CtrlK
BlogDocsLog inGet started
Tessl Logo

grill-me

Interrogate a vague or broad feature request BEFORE dispatching the harness orchestrator, to surface what the user has not anticipated. Use in the main thread when a

69

Quality

84%

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

86%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.

A tight, well-structured instruction skill that assumes Claude's competence and gives concrete probing guidance with a clear pre-dispatch workflow. Minor room to tighten actionability and add an explicit validation/feedback loop, but overall excellent for a simple skill.

DimensionReasoningScore

Conciseness

Lean and opinionated with no padding or explanation of concepts Claude already knows; every line ("One question at a time, in prose. Never a multiple-choice menu, never a batch of five at once") earns its place.

5 / 5

Actionability

Concrete, specific guidance for an instruction-only skill (one-question-at-a-time, the Cover-at-minimum list with examples like "empty / invalid input, network or backend error, two users at once", and the "I don't know" fallback) is highly actionable, just shy of fully copy-paste-ready artifacts.

4 / 5

Workflow Clarity

Clear sequence (grill one question at a time -> stop when answerable -> fold answers into dispatch prompt -> dispatch) with an explicit stop-condition checkpoint and a checklist, but lacks formal error-recovery feedback loops.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references and no bundle files present, yet well-organized into clear sections (How, Cover at minimum, After grilling), meeting the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

82%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, complete description with clear what/when guidance and an explicit negative boundary that sharpens distinctiveness. The only soft spot is specificity, since it describes one core interrogative action rather than enumerating several concrete capabilities.

DimensionReasoningScore

Specificity

Names the core action ("Interrogate a vague or broad feature request ... to surface what the user has not anticipated") but lists one main action rather than several concrete ones, matching the anchor that names the domain and 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Explicitly answers both what ("Interrogate ... to surface what the user has not anticipated") and when ("Use in the main thread when a #harness request is underspecified, when scope seems broad, or when a plan would come out too generic") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases a user would voice ("#harness request is underspecified", "scope seems broad", "a plan would come out too generic") giving good keyword coverage, though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (pre-dispatch grilling for the harness orchestrator) with distinct triggers and an explicit negative boundary ("Not for the orchestrator (headless, cannot ask)"), minimizing conflict risk.

5 / 5

Total

17

/

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
marmelab/atomic-crm
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.