CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hire

Builds a role scorecard, interview loop, sourcing plan, reference-check guide and close plan for a hire, and grades an existing job description or loop. Use when you say 'I need to hire a PM', 'write a job description', 'interview questions', 'how do I run references', 'first sales hire', 'first marketer', 'head of product search', 'scorecard' or 'how do I close a candidate'. Draws on 210 Lenny's Podcast guests including Adam Ward, Keith Rabois and Lauren Ipsen.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an unusually actionable playbook: verbatim questions, routing tables, a fill-in deliverable template, and explicit decision gates with a post-hire feedback loop, all dense with attributed, non-generic guidance. Its only issues are minor redundancy — the header repeats the description and the Receipts section duplicates quotes.md — and a slightly heavy body for an overview file.

Suggestions

Drop or shrink the 'Receipts' section to one or two anchor quotes and point to references/quotes.md for the rest, removing the duplication flagged in both conciseness and progressive_disclosure.

Trim the opening paragraph's restatement of frontmatter facts (guest count, lead-team roster) or compress it to a single line, since the description already carries that information.

Consider moving the 8-row 'Grade existing work' rubric table into references/frameworks.md (linked from a short 'Grade existing work' stub) to slim the always-loaded body.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — it never explains generic hiring concepts, instead packing each line with named, non-derivable guidance ('Never test: structure-sounding answers whose ideas are weak (Jackie Bavaro)'). However, the opening paragraph restates frontmatter facts (guest count, lead team) and the six 'Receipts' quotes duplicate references/quotes.md, giving minor instances that could be trimmed — the 4 anchor rather than the every-token-earns-its-place 5.

4 / 5

Actionability

Guidance is directly executable: a question bank with verbatim questions and follow-ups ('Tell me about something that would not exist without your initiative. Then dig six levels: how exactly?'), a complete copy-paste deliverable template, and a 1/3/5 grading rubric with a totalling rule out of 40. For an instruction-only skill this is copy-paste-ready coverage of the common cases, matching the 5 anchor rather than the minor-gaps 4.

5 / 5

Workflow Clarity

The process is clearly sequenced (Diagnose with a max-4-question cap → routing table for picking the play → run A–F → deliverable → 30-day follow-up) with explicit decision gates ('If you cannot name the specific problem, delay the search') and a genuine feedback loop (the 30-day would-you-rehire check that 'fixes the loop, not just the person'). Checkpoints are explicit, matching the 5 anchor; this is not a destructive or batch operation, so no cap applies.

5 / 5

Progressive Disclosure

The bundle structure is good: references/frameworks.md and references/quotes.md both exist, are exactly one level deep, and are clearly signaled in 'Go deeper' with a description of what each contains. The gap is that the inline 'Receipts' quotes overlap references/quotes.md — content that could live solely in the reference — placing it at the 'minor organization gaps' 4 anchor rather than the cleanly-split 5.

4 / 5

Total

18

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it names concrete deliverables on both the build and grade paths and pairs them with an explicit, naturally-phrased trigger list. The only weakness is that a couple of trigger phrases (e.g. 'interview questions') are ambiguous about which side of the table the user is on, creating minor overlap risk with a candidate-preparation skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete deliverables — 'role scorecard, interview loop, sourcing plan, reference-check guide and close plan' — plus a second capability ('grades an existing job description or loop'), giving comprehensive, non-generic coverage of the domain. This matches the anchor for multiple specific concrete actions with comprehensive coverage, and the minor-gaps anchor at 4 does not fit since no meaningful capability is missing.

5 / 5

Completeness

It explicitly answers both 'what' (five named deliverables plus grading existing work) and 'when' via a 'Use when you say...' clause with concrete trigger phrases, exactly matching the 5 anchor pattern. The 4 anchor ('when' could be more explicit) does not apply because the when-clause enumerates specific phrases.

5 / 5

Trigger Term Quality

Trigger phrases are natural user utterances with synonyms and stage variants: 'I need to hire a PM', 'write a job description', 'interview questions', 'how do I run references', 'first sales hire', 'first marketer', 'head of product search', 'scorecard', 'how do I close a candidate'. Coverage is comprehensive in the style of the 5 anchor; at most a term like 'recruiting' is absent, which is too marginal to drop to 4.

5 / 5

Distinctiveness Conflict Risk

The niche (employer-side hiring) is clear and most triggers are hire-specific, but phrases like 'interview questions' would also be said by a candidate preparing for interviews — a closely related skill could be triggered in that case (the skill body itself notes a separate 'career' skill for the candidate side). This is the 'mostly distinct; minor overlap risk' anchor rather than the minimal-conflict anchor at 5.

4 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

menkesu/awesome-pm-skills

Path

skills/hire/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.