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 writing-job-descriptionsgit 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/writing-job-descriptions)<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/writing-job-descriptions"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/writing-job-descriptions/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/writing-job-descriptions"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/writing-job-descriptions.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.00042 | $0.00883 |
| Opus 5 | $0.00021 | $0.00441 |
| Sonnet 5 | $0.00008 | $0.00177 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
writing-job-descriptions 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 9d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Job Descriptions
Help the user write effective job descriptions using frameworks and insights from 6 product leaders.
How to Help
When the user asks for help with job descriptions:
- Define success first - Ask what success looks like 12 months after the hire, not what tasks they'll do
- Identify the spike - Determine the one or two areas where this person needs to excel (not everything)
- Write for progress - Frame the role around the progress to be made, not a list of arbitrary tasks
- Consider the signal - Discuss whether the language attracts or repels the right candidates
Core Principles
Start with 12-month success
Jonathan Lowenhar: "Start with, it's 12 months later, you hired the person, 12 months have gone by, you're clinking champagne because of how great it's been. What's changed about the business?" Define success by business impact after one year, not a list of responsibilities.
Job descriptions are made up
Bob Moesta: "Job descriptions are made up. They're literally just made up - a list of stuff the manager wants plus stuff they don't want to do." Focus on the 'progress' the role enables rather than arbitrary feature requirements.
Identify where they should spike
Lauren Ipsen: "Trying to determine where this person should major and minor, where they should spike. Is this someone that's going to lean into design efforts or operate like a very senior PM?" Define specific competencies required rather than seeking a generalist who does everything.
Frame requirements as outcomes
Bob Moesta: "Don't tell me I need Excel, PowerPoint, and Word skills. Tell me what I'm going to do with those. Tell me you're going to need to build PowerPoints for executive alignment." Replace 'X years of experience' with specific capabilities that time is supposed to represent.
Iterate based on candidates
Jason Shah: "Taking a product mindset where I meet people and don't know exactly what role they're going to fill. A product mindset on hiring and iterating on it based on the candidates you're meeting." Treat job descriptions as iterative documents that evolve with market reality.
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.
- 9d ago First seen · 69 lines · 42 tokens per session scan A 9faefdbbb40f
writing-job-descriptions is a skill published in the GitHub repository cnfeat/top-pm-skills (48 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 883 once invoked, about $0.0002 per session on Opus 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-09-03.
Other skills, from other repositories
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.