project-close-out
Skill0 starsChanged 36 days agoNo licenceView on GitHub
Writes a launched website build's close-out package from the build's own files - the internal project summary with a Build complete table and outstanding items, the client transition email that moves them to the monthly retainer, and the retainer handoff brief for SEO and the AM. A script reads the go-live email, dev handoff index, articles, launch check, staging QA, Week 5 feedback, roadmap and case study, fills every table, and checks the email (under 300 words, real numbers only, no internal terms, no structured data claim). Use when the PM or AM asks to close out the project, for the close-out package, the post-launch transition email, or the retainer handoff brief. Do NOT use for the go-live email (use week-6-go-live-email), the SEO roadmap, the Month 1 task plan or the ClickUp retainer tasks (use retainer-roadmap), the case study (use case-study), the live site check (use staging-site-qa), or the Week 5 go/no-go (use week-5-handoff-check).
In this repository40 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- blueprint-deckSkill
- case-studySkill
- clickup-progress-syncSkill
- client-context-updateSkill
- client-feedbackSkill
- client-reference-kitSkill
- competitor-analysisSkill
- content-briefSkill
- content-gap-analysisSkill
- content-quality-auditorSkill
- design-qa-dev-prepSkill
- dev-handoff-indexSkill
- google-ads-analysisSkill
- google-ads-auditSkill
- growth-blueprintSkill
- homepage-design-briefSkill
- keyword-researchSkill
- kickoff-call-briefSkill
- kickoff-call-processingSkill
- new-build-kickoffSkill
- offsite-signal-analyzerSkill
- page-type-design-briefsSkill
- prospect-digital-auditSkill
- retainer-roadmapSkill
- seo-content-writerSkill
- seo-drift-monitorSkill
- serp-analysisSkill
- site-structure-optimizerSkill
- staging-site-qaSkill
- subagent-performance-reviewSkill
- technical-seo-checkerSkill
- week-1-client-emailSkill
- week-1-handoff-checkSkill
- week-2-client-emailSkill
- week-2-handoff-checkSkill
- week-5-client-emailSkill
- week-5-handoff-checkSkill
- week-6-go-live-emailSkill
- welcome-emailSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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 350,495 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
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.