kickoff-call-processing
Skill0 starsChanged 34 days agoNo licenceView on GitHub
Turns a new-build client's Kickoff Call (orientation call) transcript into the Blueprint inputs. Use when a Kickoff Call transcript needs processing after the call, for example "process the kickoff call transcript for [client]", "write the Blueprint Input Package", "pull the quote bank from the call" or "did the AM promise more than the SOW on the call". Writes the call-updates file for client-context-update, the Blueprint Input Package SEO starts the Growth Blueprint from (services priority, audiences, area tiers, voice, competitors, topics, scope) and a verbatim client quote bank, and flags any page count or deliverable said on the call that differs from the scope source as a CONFLICT while the scope source still wins. Do NOT use for merging a finished call-updates file or intake form into the context (use client-context-update), the Day 1 kickoff files (use new-build-kickoff), brand, voice or audience files (use client-reference-kit), or the AM's brief before the call (use kickoff-call-brief).
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
- new-build-kickoffSkill
- offsite-signal-analyzerSkill
- page-type-design-briefsSkill
- project-close-outSkill
- 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
3 rules. About 0 are common, 1 is distinctive, and 2 are 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.
2
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.