CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

interview

Phase 1 of building a Claude Managed Agent — interview the founder about the one job the agent should do, then produce a build sheet (CMA primitives table + v1/v2 deferrals + eval plan) WITHOUT needing their API key yet. Use when the user says "help me scope an agent", "I have an idea for an agent", "what should this agent be", or when the orchestrator routes phase=interview. Drives the six intake slots (job, trigger, inputs, actions, definition-of-done, recurrence) via AskUserQuestion, maps them to primitives with interview_planner.py, assembles build-sheet.json with build_sheet_builder.py, and validates limits with primitives_validator.py. Connectors are mockable in v0 (schema-true custom tools); real MCP servers become v1 deferrals. Distinct from stage-launch (which turns the sheet into payloads).

68

Quality

86%

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

77%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 tightly written, highly actionable phase guide with a clear sequenced workflow and an explicit validate-and-fix checkpoint, and its commands match the real bundled scripts. Its weaknesses are redundancy (the Tools section and forcing questions restate the workflow) and progressive disclosure that does not hold up against the bundle: three of four cited reference docs are missing or pathless, and the final workflow step calls a script that is not in the bundle.

Suggestions

Make the cited reference docs resolvable: bundle them under the skill (e.g. references/) or link them with paths that exist relative to SKILL.md, and give 'cma-primitives.md' and 'loops-and-workflows.md' full paths in the forcing-question library.

Drop the '## Tools' section — its one-line summaries of interview_planner.py, build_sheet_builder.py, and primitives_validator.py duplicate the workflow steps that already invoke them with full commands.

Give 'goal_state.py' an explicit path (or note it lives outside this skill) so step 5 of the workflow is as copy-paste runnable as steps 2–4.

DimensionReasoningScore

Conciseness

Lean body with no explanations of concepts Claude already knows; every section (intake table, workflow, hard rules, forcing questions) earns its place. Not a 5: the '## Tools' section re-describes the three scripts already shown with full commands in the workflow, and the forcing-question library partially repeats the intake-slot table.

4 / 5

Actionability

The three core commands are concrete and executable with realistic example arguments, and the scripts in ./scripts/ expose exactly those flags (--job/--trigger/--inputs/--actions/--dod/--recurrence/--out, --plan/--out-dir, --sheet). Not a 5: step 5 invokes 'goal_state.py set ...' with no path and the script is absent from the bundle, leaving the final step not copy-paste runnable.

4 / 5

Workflow Clarity

The five-step sequence (Interview → Map → Assemble → Validate → Record) is clearly ordered and includes an explicit validation gate with a feedback loop: 'FAIL blocks progress; fix and re-run. WARN is advisory (surface it)' — matching the anchor for explicit validation steps with error recovery.

5 / 5

Progressive Disclosure

The body is a well-organized overview that correctly defers detail to reference docs and scripts, but scored against the actual bundle the navigation fails: the links point to '../../references/examples-bank.md' and '../../references/interview-to-config.md' which do not exist in the bundle (no references/ directory), and the forcing-question library cites 'cma-primitives.md' and 'loops-and-workflows.md' as bare filenames with no path at all. Not a 4: references are not resolvable within the skill, so the 'references mostly clear' anchor is not met.

3 / 5

Total

16

/

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.

The description is a strong example: concrete, tool-named actions in third person, an explicit 'Use when...' clause with natural quoted trigger phrases, and an explicit boundary against the sibling stage-launch skill. Its only soft spot is trigger coverage that misses a few plausible phrasings ('design an agent', 'plan an agent'), and it runs slightly long with implementation details (mocking strategy) that do not help triggering.

DimensionReasoningScore

Specificity

Multiple concrete actions are named with their exact tools: 'Drives the six intake slots (job, trigger, inputs, actions, definition-of-done, recurrence) via AskUserQuestion, maps them to primitives with interview_planner.py, assembles build-sheet.json with build_sheet_builder.py, and validates limits with primitives_validator.py' — comprehensive coverage from intake to validated output in third-person voice.

5 / 5

Completeness

Explicitly answers both parts: what ('interview the founder about the one job the agent should do, then produce a build sheet (CMA primitives table + v1/v2 deferrals + eval plan)') and when ('Use when the user says... or when the orchestrator routes phase=interview') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural quoted phrases users would actually say — 'help me scope an agent', 'I have an idea for an agent', 'what should this agent be' — plus the orchestrator route 'phase=interview'. Not a 5: common variations like 'design/plan an agent' or 'agent requirements' are missing, though coverage for the niche is good.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Phase 1 interview/planning of a Claude Managed Agent) and explicitly fences off the sibling skill: 'Distinct from stage-launch (which turns the sheet into payloads)' — minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

14

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

agent-launcher/skills/interview/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.