jd-decoder
Decode a job description to find what they actually want beneath the buzzwords. Use when asked to analyse a job description, decode a JD, assess fit for a role, or figure out what a posting really means before applying. Produces a decode — the real must-haves vs. nice-to-haves, hidden priorities & culture signals, red flags, an honest fit assessment, and the exact phrases to mirror in your application.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill jd-decoder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# JD Decoder Skill A job description is a wishlist written by committee — the real signal is buried under boilerplate. This skill reads between the lines: what they *must* have vs. what's aspirational, the priorities the wording reveals, the red flags, and an honest read on your fit — plus the specific language to mirror so your application (and the ATS) sees a match. ## Required Inputs Ask for these only if they aren't already provided: - **The job description** (paste it in full — the more complete, the better the decode). - **Your background** — a short summary or CV, so the fit assessment is real, not generic. - **The company / role level**, if not obvious from the JD. ## Output Format ### JD Decode: [role] at [company] **1. What they actually want** — translate the posting into the 3–5 things that will truly decide the hire (often *not* the long requirements list). Quote the lines that reveal each. **2. Must-haves vs. nice-to-haves** — split the requirements honestly. Most "requirements" are negotiable; name the few that aren't. | Requirement | Real weight | Your match | |---|---|---| | e.g. "5+ yrs B2B PM" | must-have | ✅ strong | | e.g. "fintech experience" | nice-to-have |
- Required Inputs
- Output Format
- JD Decode: [role] at [company]
- Quality Checks
- Anti-Patterns
- Based On
What does the jd-decoder skill do?
Decode a job description to find what they actually want beneath the buzzwords. Use when asked to analyse a job description, decode a JD, assess fit for a role, or figure out what a posting really means before applying. Produces a decode — the real must-haves vs. nice-to-haves, hidden priorities & culture signals, red flags, an honest fit assessment, and the exact phrases to mirror in your application.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill jd-decoder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.