Launch week

Security, performance and a rollback plan before real users arrive.

4 of 4 available · 0 paused

A pre-launch checklist for an AI-built app

Fieldbook’s Launch week kit helps you choose agent skills for a security review, performance investigation or release check. Start with the gap in your evidence. Installing every skill does not make an app production-ready, and a passing local check does not authorize deployment.

Choose the check you need

The listings below describe each member’s scope and requested access. Read its review and source before installing one. Paused members remain visible for context but are excluded from install commands. A retained scan is not a check of today’s upstream instructions.

Write a bounded launch brief

Replace the bracketed details before handing this to your agent. This is an illustrative brief, not evidence of a completed audit or a claim that a particular skill will cover every risk.

Review [repository and revision] for [critical user journey] before launch. Begin read-only. Identify the project’s build and test commands and propose the checks needed for this journey. Permitted test targets: [local or staging URL and synthetic accounts]. Out of scope: [systems and data]. Ask before running commands that send data or change state. Separate confirmed defects from risks you could not test. For each finding, give the relevant path, evidence, impact and smallest proposed fix. Do not deploy, run migrations, change production settings, or contact third-party systems.

For example, an app that saves private notes needs evidence that account B cannot read account A’s notes. A successful login test only checks login. Use synthetic notes and test accounts in an authorized environment, and test the server’s permission check rather than only hiding a button.

Collect evidence before deciding to ship

When to stop the launch

Stop when a required check fails, a private-data boundary is untested, a secret appears in output or the recovery plan cannot account for a destructive change. Investigate and rerun the affected checks after a fix. A scanner result, an install count or a skill’s review label cannot decide these questions for your project.

Fieldbook’s automated scan covers SKILL.md, not every referenced file or runtime behavior. Read what the review does and does not establish.

Install the available skills

Read each skill’s review and access labels below before installing.

Commands target the repository commits recorded with the automated scans. Scans cover only SKILL.md, not referenced files or runtime behavior. What the review covers.

4 available install commands
npx skills@latest add https://github.com/AaravKashyap12/secure-launch/tree/389610e3efc6be85a34555110c3ce69e9195a699 --skill secure-launch
npx skills@latest add https://github.com/addyosmani/agent-skills/tree/39b723ceebf81474d0557c1fecd01eddab585563 --skill shipping-and-launch
npx skills@latest add https://github.com/cloudflare/skills/tree/cbf893b954222276bf1af57e5f23379231e0efb9 --skill web-perf
npx skills@latest add https://github.com/addyosmani/agent-skills/tree/39b723ceebf81474d0557c1fecd01eddab585563 --skill ci-cd-and-automation

Each command asks which agents to install for; add -g to install globally. Confirm installation in your chosen agent.

In this kit