agentleFS
tidycatc132tidycatc132/claude-skills/skills/week-6-go-live-email/SKILL.md

week-6-go-live-email

Skill0 starsChanged 38 days agoNo licenceView on GitHub

Drafts the Week 6 go-live confirmation email a WISE PM sends a website client when the new site is ready to launch. A script reads the Week 5 handoff, the dev handoff index, the client context and voice file, prints the header and the real page count, then checks the draft (under 200 words, page numbers match the index, only the integrations the PM named, no internal terms, no structured data claim) and writes a warning above the email when the Week 5 handoff is missing or not GO. Use when the PM asks for the go-live email, the launch confirmation email, or to tell the client the site is ready to launch or confirm the agreed launch date. Do NOT use for the Week 5 staging review email (use week-5-client-email), the go message to dev (use week-5-handoff-check), the post-launch transition email or close-out (use project-close-out), or other client emails (use week-1-client-email, week-2-client-email, welcome-email).

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.