Agent prompt

The handoff packet.

This is the thing AppFleet gives the agent. It installs the CLI, uploads the project, and syncs encrypted env envelopes without putting secret values in chat.

Copy prompt Install skill

Recommended path

Browser for the dashboard. Agent for the repo.

The prompt runs inside the target repository, where the CLI can discover safe project facts, run a doctor check, and import approved env files into the encrypted vault.

CLI: Install
Project: Upload
Env Vault: Encrypt
Dashboard: Verify

Universal prompt

Paste into any coding agent

Use this inside the target repository. It tells the agent to install the CLI, create the project, upload health evidence, import approved env files, and sync encrypted envelopes without printing values.

You are setting up AppFleet for the repository currently open in this coding-agent workspace.

Goal:
- Install or update the public AppFleet CLI.
- Sign in to AppFleet production.
- Initialize this repository with its canonical deployed URL.
- Upload a safe doctor report so the project appears in the AppFleet workspace.
- Import approved env files into the encrypted AppFleet vault.
- Sync encrypted credential envelopes to the active AppFleet workspace.
- Do this without printing env values, master passwords, tokens, ciphertext, or key material.

If your environment supports reusable skills:
- Install the AppFleet skill with: `npx skills add archietechnophile/appfleet-skills --skill appfleet-project`.
- If the skills CLI is unavailable, use the hosted fallback: `mkdir -p ~/.codex/skills/appfleet-project && curl -fsSL https://appfleet.xyz/agents/appfleet-project -o ~/.codex/skills/appfleet-project/SKILL.md`.
- If a skill is already available, use it for this task.
- If skills are not supported, follow this prompt directly.

Safety rules:
- You may locate env files by path and pass approved files to appfleet secrets import-env.
- Do not ask the human to paste secrets into chat.
- Do not print env values, auth tokens, session cookies, master passwords, encrypted blob ids, key wrapper ids, ciphertext, key material, or command output that may contain secrets.
- Ask the human to provide APPFLEET_MASTER_PASSWORD in the terminal environment or another out-of-chat channel before vault commands.
- Ask for explicit human confirmation before production credential use, reveal, rotation, deletion, provider mutation, or deleting local files.
- Use appfleet secrets inject when a command needs environment values.

Workflow:
1. Confirm you are in the target repository with `pwd` and, if available, `git remote -v`.
2. Infer the canonical deployed URL from safe public metadata only: package.json homepage, README links, framework config, Vercel/Netlify config, or existing AppFleet metadata.
3. If no deployed URL is obvious, ask me for it. Do not use localhost.
4. Check whether `appfleet` exists. If it is missing, run `npm install -g @appfleet-cli/cli@latest`.
5. Run `appfleet login`. If the browser opens, pause for me to complete sign-in.
6. Run `appfleet init --url <deployed-url>` using the real deployed URL.
7. Capture the project id and active workspace id from the safe CLI output. If unclear, run `appfleet workspace current` and `appfleet projects status <project-id>`.
8. Run `appfleet doctor <project-id> --upload`.
9. Ask me to choose or reuse the workspace master password outside chat, then run `APPFLEET_MASTER_PASSWORD='<workspace-master-password>' appfleet vault init --workspace <workspace-id>` with the real workspace id.
10. Locate likely env files by path only: `.env`, `.env.local`, `.env.production`, `.env.preview`, framework-specific env files, and package app env files. Do not print their contents.
11. Tell me the env file paths you found and ask which ones to import, including the environment name for each file.
12. For each approved file, run `APPFLEET_MASTER_PASSWORD='<workspace-master-password>' appfleet secrets import-env <env-file> --project <project-id> --env <environment>`.
13. Run `appfleet secrets sync --production-cloud --workspace <workspace-id> --api-base-url https://appfleet.xyz` with the real workspace id.
14. Ask me to verify the project and Env Vault at https://appfleet.xyz.

Final response format:
AppFleet setup result:
- Workspace: <workspace or unknown>
- Project: <project id or unknown>
- URL: <canonical URL>
- Doctor upload: <uploaded | skipped | failed>
- Env import: <imported aliases count | skipped | failed>
- Encrypted sync: <uploaded | skipped | failed>
- Workspace: https://appfleet.xyz
- Next: <one concrete next action>

Safety:
- Did not print env values, master password, tokens, ciphertext, or key material.
- Did not mutate providers or credentials.

Reusable skill

appfleet-project

Source: https://github.com/archietechnophile/appfleet-skills. Install target: ~/.codex/skills/appfleet-project.

1
Install with skillsUse this standardized install path for Codex-style and compatible agents. npx skills add archietechnophile/appfleet-skills --skill appfleet-project
2
Fallback installUse this when the skills CLI is unavailable but the agent supports local skills. mkdir -p ~/.codex/skills/appfleet-project && curl -fsSL https://appfleet.xyz/agents/appfleet-project -o ~/.codex/skills/appfleet-project/SKILL.md
3
Invoke the skillPaste this as the first message after installing the skill. Use $appfleet-project to initialize this repository in AppFleet, upload a doctor check, and sync encrypted env files.
4
FallbackIf the agent does not support skills, paste the full bootstrap prompt instead.

What the agent may run

Project and Env Vault commands

npm install -g @appfleet-cli/cli@latest
appfleet login
appfleet init --url <deployed-url>
appfleet doctor <project-id> --upload
APPFLEET_MASTER_PASSWORD='<workspace-master-password>' appfleet vault init --workspace <workspace-id>
APPFLEET_MASTER_PASSWORD='<workspace-master-password>' appfleet secrets import-env <env-file> --project <project-id> --env <environment>
appfleet secrets sync --production-cloud --workspace <workspace-id> --api-base-url https://appfleet.xyz

Trust boundary

No secrets in chat

You may locate env files by path and pass approved files to appfleet secrets import-env.
Do not ask the human to paste secrets into chat.
Do not print env values, auth tokens, session cookies, master passwords, encrypted blob ids, key wrapper ids, ciphertext, key material, or command output that may contain secrets.
Ask the human to provide APPFLEET_MASTER_PASSWORD in the terminal environment or another out-of-chat channel before vault commands.
Ask for explicit human confirmation before production credential use, reveal, rotation, deletion, provider mutation, or deleting local files.
Use appfleet secrets inject when a command needs environment values.