campaign-retrospective
Skill40 starsChanged 14 days agoNo licenceView on GitHub
Run a retrospective on any ABA campaign or initiative after it wraps — events, webinars, launches, cohorts, content pushes, outreach campaigns, sponsorships, partnerships. Use whenever Shaw says "let's do a retrospective", "retro", "post-mortem", "how did X go", "what did we learn from", "break down the numbers", "was it worth it", or shares a results export after a campaign. Also fires when he links a Notion retro page, drops a Luma/Kit/LinkedIn/Zoom export following a campaign, or asks why something underperformed. Pulls goal vs actual from the Notion campaign hub, reconciles actuals against each channel's source of truth, separates organic conversions from chased ones, diagnoses the binding constraint, and drafts the retro in chat for approval before writing anything to Notion. Do NOT use for pre-launch planning (business-strategy), live campaign syncs (crm / outreach), or single-channel analytics pulls (linkedin-post-analytics).
In this repository45 other files it gives its agents.
- aba-brand-systemSkill
- aba-plugin-updaterSkill
- animation-builderSkill
- business-strategySkill
- calendar-helperSkill
- call-follow-upSkill
- sync-desktop-skillsSkill
- client-docsSkill
- client-supportSkill
- conversion-copySkill
- convo-miningSkill
- cost-optimizerSkill
- crmSkill
- email-helperSkill
- engagementsSkill
- event-finderSkill
- executive-briefingSkill
- extract-chatgpt-transcriptSkill
- google-drive-helperSkill
- graphic-builderSkill
- keynoteSkill
- linkedin-audienceSkill
- linkedin-post-analyticsSkill
- linkedin-voiceSkill
- medium-helperSkill
- meeting-prepSkill
- newsletter-writerSkill
- notion-helperSkill
- outreachSkill
- reviews-referralsSkill
- sales-letter-writerSkill
- sfc-helperSkill
- skill-helperSkill
- skill-updaterSkill
- skimmable-summarySkill
- slack-helperSkill
- social-repliesSkill
- sop-helperSkill
- stripe-helperSkill
- tactical-negotiationSkill
- text-helperSkill
- upworkSkill
- video-editor-v3Skill
- workshop-use-case-researcherSkill
- youtube-strategySkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
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.