Agency
Claude Code skills: freelance business pack and model-routing expert team that delegates to haiku/sonnet/opus/fable specialist subagents
npx -y skills add mehtab78/skills --skill agencyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when a freelancer is turning solo work into a service agency, or running one, client onboarding, scoped proposals and rate cards, project/deadline tracking across many clients, deliverable workflows, subcontractor/team coordination, and margin protection. Trigger when the user mentions running an agency, taking on more clients than they can do alone, hiring VAs/subcontractors, productizing a service, or systematizing agency operations. For a single- client system use the clients skill; for winning the work use fiverr / upwork.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.0 KB, as published. Nobody here has run it
Running a service agency
Handle the operational load (intake, pricing, projects, deliverables, team) so the user can spend their time on clients and strategy. Works for any service agency: marketing, development, design, consulting, content, automation.
Where things live
Keep agency data under ~/agency/:
~/agency/
├── clients/ # one file per client (+ index.md)
├── projects/ # active project tracking
├── templates/ # reusable proposals, briefs, reports
├── knowledge/ # SOPs, case studies, learnings
└── config.md # rates, margins, team
The core loops
- Intake: a brief arrives (email, audio, notes) → extract scope, budget,
timeline → produce a structured brief → flag red flags → open a client folder.
See
references/onboarding.md. - Pricing: take the scope → apply the rate card and complexity multipliers →
build a proposal → sanity-check against similar past projects. See
references/pricing.md. - Projects: one board of every active project → alert on deadlines → catch
stalls → weekly status per client. See
references/projects.md. - Deliverables: turn rough input into a reviewed, on-brief deliverable, in
the right formats. See
references/deliverables.md.
Rules that keep an agency healthy
- Nothing goes to a client without the user's approval: proposals, messages, deliverables are all drafts for review.
- Track cost against estimate and speak up the moment a project starts losing money.
- Learn from corrections: fold them back into templates and the knowledge
base (
references/feedback.md). - Carry context across sessions: refer to each client's history, don't start cold.
References
| Area | File |
|---|---|
| Client intake & discovery | references/onboarding.md |
| Pricing, estimates, proposals | references/pricing.md |
| Project board & deadlines | references/projects.md |
| Client communication | references/communication.md |
| Producing deliverables | references/deliverables.md |
| Team & subcontractor coordination | references/team.md |
| Specifics per agency type | references/by-type.md |
| Learning & improvement system | references/feedback.md |
Set up ~/agency/config.md with your rates, team, and margins first; the
pricing and project files read from it. Format is in references/pricing.md.