Every week at the agency, I watched the same thing happen.
Someone would spend 45 minutes writing a project brief from scratch.
A client approval email would go out without a deadline or escalation plan.
The monthly report would take two hours to format because there was no template.
A shooting day would start without a proper shot list.
Eight workflows. Repeated every week. Each one rebuilt from memory.
After the tenth time watching this happen, I decided to encode these workflows
as Claude Agent Skills and open-source them.
What is agencykit
agencykit is a pack of 8 Claude Agent Skills that handle the workflows
creative agencies and freelancers repeat most often.
Install with:
\bash
npx agencykit install
\\
Then trigger from plain English inside Claude Code, Codex CLI, Cursor,
or Gemini CLI — any agent that follows the agentskills.io spec.
The 8 skills
project-brief
Trigger: "new project", "nuovo progetto"
Asks 5 clarifying questions, then produces a complete project brief:
RECAP (client, service, objective, deadline, owner, teams, status, priority),
phased task list with owners and deadlines, and a risk register.
Output is formatted to paste directly into Asana, Notion, or ClickUp.
client-approval
Trigger: "approval", "approvazione", "revision"
Generates the client-facing approval request with a 48h SLA baked in.
Escalates automatically at 72h. Tracks revision count across the conversation
and flags revision 3+ as billable extra — because most agency contracts
have this rule but nobody actually enforces it.
client-report
Trigger: "monthly report", "report mensile"
Takes raw KPI data and produces a narrative report: executive summary
(3 sentences), what worked, what didn't, next month plan, data table.
Not a data dump. A story.
quote-builder
Trigger: "quote", "preventivo"
Line-item quote with payment terms (50% upfront, 50% delivery).
Asks for internal cost estimate and shows gross margin.
Warns if margin is below 40%.
shooting-day
Trigger: "shooting", "riprese"
Produces the full shooting day pack: ODG with times, shot list
(Hook / Body / CTA / B-roll / Audio), equipment checklist,
and a WhatsApp-ready crew briefing message.
social-calendar
Trigger: "content calendar", "piano editoriale"
4-week content calendar with date, channel, format, topic/angle,
hook first line, and posting time recommendation.
First week captions written in full.
post-mortem
Trigger: "post-mortem", "retrospective"
Structured retrospective: what worked, what didn't, root causes,
3 concrete actions for next similar project.
Appends a formatted entry to LESSONS.md in the project root.
agency-status
Trigger: "status update", "stato agenzia"
Traffic-light status per active project (green/yellow/red),
top 3 priorities for the week, blocked items with owner and next action,
and a Slack/WhatsApp-ready morning briefing message.
The technically interesting part
The client-approval skill maintains revision count state across
the conversation — entirely prompt-side, no backend, no database.
The skill instructions tell the model to:
- Start a revision counter at 0 in the first response
- Increment it each time a revision is requested
- At revision 3+, generate a different output block that flags the revision as billable extra and includes the contract clause language
This is a useful pattern for any skill that needs to track
conversational state without external storage.
How it works technically
Each skill is a SKILL.md file with YAML frontmatter and bilingual
(EN + IT) instructions. The CLI installer drops them into:
-
.claude/skills/for project-level installation -
~/.claude/skills/for global installation
The skills follow the agentskills.io spec, so they work with any
compatible agent — not just Claude Code.
Install
\`bash
via npx
npx agencykit install
via curl
curl -fsSL https://raw.githubusercontent.com/MarcoZorn/agencykit/main/install.sh | bash
list installed skills
npx agencykit list
`\
GitHub: https://github.com/MarcoZorn/agencykit
Landing: https://marcozorn.github.io/agencykit/
License: MIT
Curious what domains people think are underserved in the Claude skills
ecosystem. Currently it's ~90% developer/DevOps tooling. Feels like
there's a lot of space for non-developer workflows.
Top comments (0)