CtrlK
BlogDocsLog inGet started
Tessl Logo

grilling

Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.

67

Quality

80%

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

82%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 lean, well-structured instruction set for a simple single-purpose skill, with concrete guidance and an explicit feedback loop. It scores slightly below perfect on actionability, workflow clarity, and progressive disclosure due to the absence of example questions, concrete sequencing, and section headers.

Suggestions

Add 1-2 example interview questions to make the actionability fully concrete and model the expected depth.

Make the design-tree traversal sequence explicit (e.g., a short numbered outline of how to pick the next branch) to lift workflow clarity.

Add lightweight section headers (e.g., '## Approach', '## Rules') to give the short body clear structural markers for progressive disclosure.

DimensionReasoningScore

Conciseness

Seven lean lines with no padding and no over-explanation of concepts Claude already knows; every token earns its place, matching the score-5 anchor.

5 / 5

Actionability

Concrete, executable instruction ('ask one at a time, waiting for feedback', 'provide your recommended answer', 'explore the codebase instead'), but it stops short of giving example questions, keeping it below the score-5 anchor.

4 / 5

Workflow Clarity

A clear iterative sequence is present with an explicit feedback checkpoint ('waiting for feedback on each question before continuing'), but 'walk down each branch of the design tree' is somewhat abstract without an explicit ordering, so it does not reach 5.

4 / 5

Progressive Disclosure

The body is short and logically organized into three focused paragraphs with no external references needed, but it is flat with no section headers or structural markers, placing it just below the score-5 anchor.

4 / 5

Total

17

/

20

Passed

Description

78%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 strong: it explicitly covers what the skill does and when to use it, with natural trigger terms and a distinct niche. Its only weak spot is specificity, where it names the domain and a couple of actions rather than enumerating several concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain ('interview relentlessly about a plan or design', 'stress-test a plan') with 1-2 concrete actions, but does not enumerate several specific actions, so it matches the score-3 anchor rather than 4.

3 / 5

Completeness

Explicitly answers both what ('Interview the user relentlessly about a plan or design') and when ('Use when the user wants to stress-test a plan before building, or uses any grill trigger phrases') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms a user would say ('stress-test a plan', 'grill') with good coverage, though a few common synonyms ('poke holes in', 'pressure-test') are missing, placing it above the score-3 anchor.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche (relentless interviewing/grilling about a plan) with distinct triggers, but carries minor overlap risk with general planning or design-review skills, so it sits just below the score-5 anchor.

4 / 5

Total

16

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
coder/agent-tty
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.