CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/interview-question-author

Build-an-X workflow that produces a QA-role-specific interview question bank - takes a role description (manual QA / SDET / automation engineer / test lead / quality manager) plus competency model and emits a structured question bank covering technical, behavioral (STAR-format), scenario-based, and system-design dimensions, classified by ISTQB-canonical competency areas and Bloom's taxonomy difficulty levels. This produces the questions only - not the scoring rubric and not the gold-standard answer guide. Use as the first artifact a hiring manager produces when opening a QA / test role, before scheduling the first interview.

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

The body is highly actionable and well-structured: concrete templates, explicit allocation tables, a clear sequenced workflow with checkpoints, and a clean hand-off. The only weakness is conciseness — the Overview's research-narration and differentiation prose, plus repeated structured-interview citations, add tokens that do not advance the how-to.

Suggestions

Tighten the Overview: replace the four-point (a)-(d) differentiation prose and the structured-interview research narration with a one- or two-sentence positioning statement, moving the citations to the References section only.

Consolidate the repeated 'structured-interview research' Wikipedia citations (currently inlined in Overview, When-to-use, Step 3, and Anti-patterns) into the single References entry to reduce token cost.

Trim the Limitations section to the load-bearing constraints (technical-screening gap, STAR cues as heuristics, jurisdiction/legal compliance) and drop the verbose framing around each.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes competence (it leverages ISTQB, Bloom's, and STAR as classification tools rather than tutorializing them), but the Overview narrates research background and a four-point differentiation list in prose and repeats structured-interview research citations, so not every token earns its place — matching the score-2 anchor of 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the fully lean score-3 anchor.

2 / 3

Actionability

Provides copy-paste-ready guidance — a filled question-slot markdown template (Step 3), explicit role-to-slot-count and seniority-to-Bloom's-mix tables, a precise output schema (Step 5), and an anti-patterns table with fixes — matching the score-3 anchor for fully executable, specific, copy-paste-ready instruction rather than the incomplete/pseudocode score-2 anchor.

3 / 3

Workflow Clarity

A clear five-step sequence (Capture inputs, Allocate slots, Author questions, Tune difficulty, Emit bank) carries explicit checkpoints — a UNRECOGNISED_ROLE halt, a difficulty-too-far flag in Step 4, and a required hand-off block — matching the score-3 anchor; this is not a destructive/batch operation, so the lighter validation present is sufficient and does not cap at 2.

3 / 3

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent) and the body is organized into clear sections with one-level-deep, clearly signaled references (sibling skills and external URLs in a References section), so per the simple-skills scoring note well-organized sections warrant the score-3 anchor; there is no nested/deeply-referenced structure that would drop it to 2.

3 / 3

Total

11

/

12

Passed

Description

100%

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

The description is specific, complete, and distinctive: it names the concrete output (a structured QA interview question bank across four dimensions classified by ISTQB areas and Bloom's levels), gives an explicit 'use when' trigger tied to opening a QA role, and bounds its scope against sibling skills. Voice is correctly third person with no first/second-person usage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and outputs — 'produces a QA-role-specific interview question bank', 'emits a structured question bank covering technical, behavioral (STAR-format), scenario-based, and system-design dimensions, classified by ISTQB-canonical competency areas and Bloom's taxonomy difficulty levels' — matching the score-3 anchor for listing multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both 'what' ('emits a structured question bank...') and 'when' ('Use as the first artifact a hiring manager produces when opening a QA / test role, before scheduling the first interview') with an explicit Use-as clause, matching the score-3 anchor where both what AND when are clearly answered.

3 / 3

Trigger Term Quality

Natural hiring-manager vocabulary is present throughout — 'interview question bank', 'QA / test role', 'hiring manager', 'manual QA / SDET', 'competency model', 'ISTQB' — giving good coverage of terms users would actually say, matching the score-3 anchor; it is not merely partial coverage (score 2).

3 / 3

Distinctiveness Conflict Risk

Carves a precise, bounded QA-hiring niche ('This produces the questions only - not the scoring rubric and not the gold-standard answer guide') with distinct triggers unlikely to conflict with sibling skills, matching the score-3 anchor; it is not merely 'somewhat specific' (score 2).

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents