agentleFS
Sign inStart free
ZoolCoderZoolCoder/findable/skills/launch/SKILL.md

launch

Skill0 starsChanged 30 days agoMITView on GitHub

Check a site before it goes live, moves domain or changes URLs: findable audit with no errors, canonical host, preview hosts kept out of search, redirects from old URLs, sitemap submitted, and a CI gate. Use when the user says "launch", "go live", "migrate", "new domain", "redesign is ready", or "add SEO checks to CI".

66 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-policy, tool-rename-deprecation and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • OpenCortexIDESkill

    add-policy

    Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.

    Also in 4 projects that use this

  • gitpod-ioSkill

    tool-rename-deprecation

    Ensure renamed built-in tool references preserve backward compatibility. Use when renaming a toolReferenceName, tool set referenceName, or any tool identifier. Run on ANY change to tool registration code. Covers legacyToolReferenceFullNames for tools and legacyFullNames for tool sets.

    Also in 4 projects that use this

  • CesarjoquinSkill

    competitors

    When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.

    Also in 12 projects that use this

  • CesarjoquinSkill

    paywalls

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

    Also in 9 projects that use this

  • riggyzSkill

    attribution

    Attribution rules for issues, pull requests, work items, reviews, and comments created or edited by the agent in GitHub, Linear, Azure DevOps, or similar collaboration systems. Use when creating, commenting on, reviewing, or modifying external tracker content.

    Also in 6 projects that use this

  • coreyhaines31Skill

    conversion-tracking

    Set up, audit, verify, or fix website conversion tracking. Use when the conversion is a form submission, booked meeting, chat, phone call, signup, or purchase; when conversions must reach Google Ads, Meta, GA4, LinkedIn, TikTok, or Microsoft Ads; when the work involves GTM tags and dataLayer events, pixels, the Conversions API (CAPI), Enhanced Conversions, server-side tagging, or gclid and fbclid capture; or when the user reports conversion problems like "conversions stopped", "double counting", "spend but no conversions", "GA4 and Google Ads don't match", or an Unverified or Inactive status. Covers lead gen and ecommerce. Always fire on confirmed success, never the submit click; verify a test conversion arrives; diagnose before changing anything; offer free and native paths alongside paid ones and disclose partner tools. For tracking plans and UTMs, see analytics. For attribution models, see attribution. For campaigns and bidding, see ads. For CRM lead-stage design, see revops.

    Also in 3 projects that use this

  • +4 more from Cesarjoquin

The file

Create a free account to mount
Files
SKILL.md

Launch

Before

  1. Build with the production base URL, then findable audit -exit-code. No errors. Read every warning with the owner.
  2. Canonicals and the sitemap name the production host only (meta.canonical.host, sitemap.url.host).
  3. Preview and staging hosts send X-Robots-Tag: noindex or sit behind auth. Never let a preview be indexed, and never ship the production build with a site-wide noindex left on.
  4. Moving URLs or domains: a 301 from every old URL to its new one (not all to the home page). Keep the redirects for at least a year. Check them by crawling the old sitemap.
  5. robots.txt allows the site and names the sitemap. AI crawler policy decided (the ai-search skill).
  6. Structured data passes the Rich Results Test on one page of each type.
  7. Lighthouse mobile on the key pages; fix anything far off.

Deploy

Deploying is the owner's decision and action. Agents prepare and report; they do not deploy production without an explicit yes in this conversation.

After

  1. Submit the sitemap in Search Console and Bing Webmaster Tools; for a domain move, use the Change of Address tool too.
  2. findable audit against the live url: once, to catch what only the server does (redirects, headers, X-Robots-Tag).
  3. Watch index coverage and 404s for four weeks (the measure skill).

CI gate

- run: npm run build
- run: findable audit -exit-code -target site

-exit-code exits 2 on any error finding. Pin the findable version.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free