write-role-scorecard

write-role-scorecard is a skill for Claude Code from jeffreytse/grimoire-core. It costs 55 tokens per session (2,000 once invoked), scanned A, original, MIT.

A hiring document that defines the results a role must deliver, the skills needed, and the expected working behaviors.

In plain words
What is it for?
Use it to define a role before hiring and create interview questions and evaluation criteria.
Why use it?
It helps interviewers judge candidates against the work itself instead of relying mainly on credentials or years of experience.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the grimoire-business plugin — 145 skills shipped together

Good fit Use it to define a role before hiring and create interview questions and evaluation criteria.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/write-role-scorecard
Install

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.

Any agent
npx skills add jeffreytse/grimoire-core --skill write-role-scorecard
Clone the repo
git clone --depth 1 https://github.com/jeffreytse/grimoire-core

Made for: Claude Code.

Or install grimoire-business, the plugin that ships this one along with the rest of its 145 skills.

Wrote 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.

agentmods badge for write-role-scorecard

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/write-role-scorecard/github.svg)](https://agentmods.dev/skills/jeffreytse/grimoire-core/write-role-scorecard)
Your own site
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/write-role-scorecard"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/write-role-scorecard/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.

agentmods 80×15 button for write-role-scorecard

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/write-role-scorecard"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/write-role-scorecard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,000 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.02000
Opus 5 $0.00028 $0.01000
Sonnet 5 $0.00011 $0.00400
Haiku 4.5 $0.00006 $0.00200

Measured 5d ago against content hash 3df6b90bd097, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

write-role-scorecard 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 5d 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.

skills/business/leadership/skills/write-role-scorecard/SKILL.md · 130 lines

How it starts

The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Write Role Scorecard

Define a hiring role by its required outcomes, competencies, and cultural fit criteria — so the hiring team evaluates candidates against actual job performance standards rather than resume signals.

Why This Is Best Practice

Adopted by: Smart & Street's "Who: The A Method" is the most widely cited CEO-level hiring methodology, with documented adoption at the Blackstone Group, General Atlantic, and hundreds of private equity portfolio companies; ghSMART's Topgrading methodology — which the scorecard is derived from — has been applied at over 5,000 organizations; the US Navy SEALs use a performance-standard scorecard equivalent in their selection process (Basic Underwater Demolition/SEAL training); SHRM's competency-based hiring framework incorporates scorecard principles as the foundation of structured hiring Impact: Smart & Street's research (313 hiring decisions analyzed) found that managers using scorecards to define and evaluate against role outcomes hired "A players" (performers in the top 10% for the role) 90% of the time, compared to 26% using traditional credential-and-interview methods; McKinsey's 2021 talent research found that organizations with clearly defined role outcomes rather than vague job descriptions reduced time-to-productivity for new hires by 35%; Geoff Smart's follow-on research (500+ executive hires) found that 90% of hiring failures trace to misaligned expectations of what success in the role looks like — a gap the scorecard closes before the hire Why best: Job descriptions are marketing documents — they attract candidates; scorecards are performance standards — they define what success requires; traditional interviews evaluate whether a candidate is likable, impressive, and experienced; scorecard-based interviews evaluate whether a candidate has the track record of accomplishing the specific outcomes the role requires; the scorecard replaces subjective "gut feel" hiring with evidence of past performance on the dimensions that matter

Read the full file on GitHub · 130 lines

Changes

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.

  1. 5d ago First seen · 130 lines · 55 tokens per session scan A 3df6b90bd097

Subscribe to this mod's changes

write-role-scorecard is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 20d ago), licensed MIT. It adds 55 tokens to every session and 2,000 once invoked, about $0.0003 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.