2
2 Comments

agencykit — I turned my agency's 8 most-repeated workflows into Claude skills (free, MIT)

Hey IH,

I work at a creative agency in Rome and kept running into the same problem:
every week, the team was rewriting the same 8 things from scratch.

Project briefs. Client approval emails. Monthly reports. Quotes.
Shooting day schedules. Social content calendars. Post-mortems.

Each one taking 30-90 minutes. Each one slightly different every time.
No consistency, no knowledge transfer, no way to onboard new people fast.

So I built agencykit — a pack of Claude Agent Skills that encode these workflows.
You install it once, then trigger them with plain English:

  • "new project" → full project brief with task list, phases, and risk register
  • "client approval" → approval request with 48h SLA, escalation at 72h,
    and automatic revision counter (flags revision 3+ as billable extra)
  • "monthly report" → narrative client report, not a data dump
  • "quote" → line-item quote with margin check (warns below 40%)
  • "shooting" → ODG, shot list, equipment checklist, crew WhatsApp message
  • "content calendar" → 4-week calendar with first-week captions written out
  • "post-mortem" → structured retrospective appended to LESSONS.md
  • "status update" → traffic-light per project + morning briefing message

Works with Claude Code, Codex CLI, Cursor, Gemini CLI.
All bilingual EN + IT. MIT license.

Install: npx agencykit install
GitHub: https://github.com/MarcoZorn/agencykit
Landing: https://marcozorn.github.io/agencykit/


The technically interesting part: the client-approval skill maintains
revision count state across the conversation — entirely prompt-side,
no backend. It generates a different output at revision 3+, flagging it
as a billable extra. Most agency contracts have this rule, but nobody
actually counts. Now it counts automatically.


Happy to answer questions. Especially curious if anyone's building
Claude skills for other non-developer domains — feels like the ecosystem
is 90% dev tooling and 10% everything else.

on July 4, 2026
  1. 1

    The real shift here isn’t workflow automation—it’s turning repeated agency knowledge into executable structure.

    Most agencies don’t lose time because they lack tools, but because institutional knowledge stays implicit. Encoding recurring workflows as triggerable “skills” turns tacit operational behavior into something consistent, reusable, and transferable across teams without re-explaining it every time.

  2. 1

    The revision counter on the client approval skill is clever. Most agencies I know lose real money on revision 4+ because nobody tracks it at the contract level. On your question about non-dev domains: I have seen people building Claude skills for sales outreach sequencing and customer support triage. The pattern of encode-a-workflow translates well to any domain with repeatable processes. Are you planning to add a skill for proposal writing? That is another 60-minute task most agencies rewrite from scratch every time.

Trending on Indie Hackers
The hardest part isn't building anymore User Avatar 85 comments I sold $6,773 in 2 weeks, with almost no existing community. User Avatar 60 comments Before you build another feature, use this workflow User Avatar 38 comments Ferguson is LIVE on ProductHunt today... so I audited their homepage first! User Avatar 38 comments Built a local-first Amazon profit-by-SKU + QuickBooks/Xero journal tool. Looking for founding users. User Avatar 32 comments From Fractional CTO to Micro-SaaS: How 15 Unbilled Hours Inspired an AI Shield (And What the Data Says About V2) User Avatar 26 comments