CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/qa-hiring-kit

End-to-end structured hiring for QA / SDET / automation / test-lead / quality-manager roles - one chain from job description through interview question bank, competency-anchored scoring rubric, interviewer calibration guide, and post-interview panel debrief, to the 30-60-90 day onboarding plan. Implements the canonical Levashina 2014 et al. structured-interview methodology with ISTQB-aligned competency vocabulary, so the JD a candidate reads, the rubric the panel scores, and the ramp plan the manager runs all describe the same role. Use when opening a QA requisition, authoring any artifact of the hiring loop (JD, questions, rubric, calibration guide, onboarding plan), or running the panel debrief to a defensible hire / no-hire decision.

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

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

92%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 a well-orchestrated overview: a dense stage table, a fully specified debrief workflow with halt conditions, thresholds, and floor rules, and clean one-level-deep disclosure into five verified reference files. The main trim opportunity is the repeated research citations and inline rationale for biases Claude already knows, which keeps conciseness at 4.

Suggestions

Cite each source once: Levashina et al. 2014 appears in the overview, debrief step 7, and the References section; anchoring and employment-interview sources are likewise cited both inline and at the end. Consolidate to a single citation point.

Trim the inline bias rationale in "Running the debrief" (the four-line anchoring explanation) to a one-line citation - the operational rule (refuse to start without independent pre-submission) stands on its own without explaining the bias.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with no filler, but research rationale is repeated: Levashina et al. 2014 is cited three times (overview, debrief step 7, References), the anchoring explanation ("the first opinion revealed in a group setting has disproportionate influence on subsequent scorers") restates a concept Claude already knows, and the closing References section re-cites every inline source. Fits the 4 anchor (efficient, minor over-explanation that could be trimmed); not 5 because of this citation redundancy, and not 3 because the core guidance is lean throughout.

4 / 5

Actionability

Concrete, executable rules throughout: "6-8 slots per interview", "5-8 competency dimensions per role", "flag any dimension with a spread greater than 1 point", floor rules ("any dimension at 1 is a no-hire regardless of totals; two or more dimensions at 2 is a no-hire"), and named halt signals (`INCOMPLETE_PANEL_SUBMISSION`, `MISSING_RUBRIC`) with required content. A panel could run the debrief directly from this file - full match to the 5 anchor for an instruction-only skill; not 4 because no step lacks the specifics needed to execute it.

5 / 5

Workflow Clarity

The debrief is a 7-step numbered sequence with explicit validation gates: refuse to start without independently pre-submitted scores, halt with a named signal on missing submissions, flag >1-point spreads, resolve disagreements via gold-standard comparison, re-score on bias flags, and escalate BORDERLINE to the hiring manager rather than re-vote. Lock timing ("Lock artifacts at the start of a hiring round") and the stage table sequence the upstream chain. All checkpoints and feedback loops are present - 5, not 4.

5 / 5

Progressive Disclosure

The 177-line body is an overview whose stage table maps each of the six stages to one of five real, verified reference files (references/jd-author.md, interview-questions.md, rubric.md, calibration.md, onboarding.md), all exactly one level deep; only the runtime debrief workflow is deliberately kept inline ("this file, 'Running the debrief'"). Cross-links inside the references are sibling navigation, not nested content. Clear split and signaling - 5.

5 / 5

Total

19

/

20

Passed

Description

92%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 enumerates the full artifact chain concretely, carves a clearly bounded QA-hiring niche, and pairs a clear "what" with an explicit multi-scenario "Use when" clause. The only weakness is a handful of missing natural synonyms for roles and artifacts, which keeps trigger-term quality at 4.

Suggestions

Add spelled-out role synonyms such as "quality assurance", "test engineer", and "tester" to the role list so users who avoid the QA/SDET abbreviations still trigger the skill.

Consider adding "interview scorecard" or "candidate evaluation" as natural trigger phrasings for the rubric artifact.

DimensionReasoningScore

Specificity

The description enumerates the full concrete artifact chain: "one chain from job description through interview question bank, competency-anchored scoring rubric, interviewer calibration guide, and post-interview panel debrief, to the 30-60-90 day onboarding plan" - six specific deliverables covering the hiring loop end to end. Matches the anchor for multiple specific concrete actions with comprehensive coverage; not 4 because no stage of the loop is left uncovered.

5 / 5

Completeness

The opening sentence answers "what" (the six-artifact hiring chain) and the explicit clause "Use when opening a QA requisition, authoring any artifact of the hiring loop (JD, questions, rubric, calibration guide, onboarding plan), or running the panel debrief to a defensible hire / no-hire decision" answers "when" with three concrete triggers. Clear match to the 5 anchor; not 4 because the when-clause is explicit and specific, not merely present.

5 / 5

Trigger Term Quality

Good natural-term coverage: "QA", "SDET", "job description", "JD", "rubric", "panel debrief", "onboarding plan", "hire / no-hire", plus five role synonyms ("QA / SDET / automation / test-lead / quality-manager"). A few common user phrasings are missing - "quality assurance" spelled out, "test engineer", "interview scorecard" - so it fits the 4 anchor (good coverage, a few natural terms missing) rather than the 5 anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Everything is anchored to a clear niche - "structured hiring for QA / SDET / automation / test-lead / quality-manager roles" - with QA-specific artifacts ("competency-anchored scoring rubric", "interviewer calibration guide") that generic hiring or engineering-interview skills would not claim. Generic words like "job description" are framed by the QA scope, so conflict risk is minimal; matches the 5 anchor.

5 / 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.

Reviewed

Table of Contents