Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add cnfeat/top-pm-skills --skill delegating-workgit clone --depth 1 https://github.com/cnfeat/top-pm-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/cnfeat/top-pm-skills/delegating-work)<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/delegating-work"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/delegating-work/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/delegating-work"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/delegating-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00038 | $0.00964 |
| Opus 5.5 | $0.00015 | $0.00386 |
| Sonnet 5.5 | $0.00008 | $0.00193 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
delegating-work scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegating Work
Help the user delegate effectively using frameworks from 38 product leaders who have scaled themselves and their organizations.
How to Help
When the user asks for help with delegating:
- Diagnose the blocker - Determine if they're holding on due to identity, control, or lack of trust
- Identify what to delegate - Use energy audits and the Eisenhower Matrix to find candidates
- Match delegation style to context - Help them calibrate between autonomy and involvement
- Design for success - Set up the delegation with context, parameters, and feedback loops
Core Principles
Context, not control
Ray Cao: "The number one thing is context, not control. That's the reason why we're always encouraging people to see themselves as a business owner." Provide all necessary information so employees can 'connect the dots' themselves rather than waiting for instructions.
Refuse to rule
Boz: "One of the most powerful things we do is refuse to rule. Someone will bring me a thing. I'll be like, 'Nope, but look, I think you've got it.'" Intentionally step back when the team is struggling with the 'right' problems to build their autonomy.
Give away your Legos
Cam Adams: "Finding joy in the other things of building a team, passing on your experience, helping other people do great writing or great product building is really what giving away your Lego is about." Find fulfillment in enabling others to succeed rather than holding onto tasks for personal identity.
Being in details is not micromanagement
Brian Chesky: "There's a difference between micromanagement, which is like telling people exactly what to do, and being in the details. If you don't know the details, how do you know people are doing a good job?" Deep involvement ensures quality; micromanagement prescribes every action.
Don't delegate your superpower
Brian Chesky (citing Ben Horowitz): "A lot of people tell product led founders to step away and delegate their product to other people, but suddenly they've delegated away the thing they're best at. The thing that is hardest for them to replace." Retain direct involvement in your core competency.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 71 lines · 38 tokens per session scan A 8cc6c81ae166
delegating-work is a skill published in the GitHub repository cnfeat/top-pm-skills (55 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 964 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…