CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

grill-with-docs

Grilling session that challenges your plan against the project's documented domain language and decision records, sharpens terminology, and updates the glossary and ADRs inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

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.

A lean, highly actionable interview-style skill: the trace command and example challenge phrasings are copy-paste concrete, and the session flow is well sequenced with per-question feedback checkpoints. The main defects are a duplicated sentence about AGENTS.md, no verification step for the glossary/ADR artifacts it writes, and format sidecars referenced but missing from the bundle.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence, but states the same fact twice in a row: 'both of them pointed at from the root `AGENTS.md`' is immediately restated as 'The root `AGENTS.md` is the agent manual, and it points at both'. This matches 'efficient; minor instances of over-explanation that could be trimmed' rather than 3 (no pervasive padding) or 5 (the duplication keeps it from being fully lean).

4 / 5

Actionability

Guidance is fully executable for an instruction-only skill: a copy-paste-ready command ('sh scripts/trace.sh emit kind=grill.decision [subject=...] outcome=accepted|overridden ...'), concrete challenge phrasings ("Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"), exact doc paths, and three explicit ADR criteria. It is not below 5 because the common cases (term conflict, fuzzy term, ADR offer) each have a worked example.

5 / 5

Workflow Clarity

Sequence is clear with feedback checkpoints: 'Ask the questions one at a time, waiting for feedback on each question before continuing', 'If a question can be answered by exploring the codebase, explore the codebase instead', and 'after the decision, never in place of it' for the trace. It falls short of 5 because there is no verification step for the artifacts the skill writes (glossary edits, new ADRs), and not below 4 since the per-question feedback loop and 'if it is not obvious, ask' checkpoint are explicit.

4 / 5

Progressive Disclosure

Structure follows the good pattern — core session guidance inline with formats split out via well-signaled one-level links ('Use the format in [GLOSSARY-FORMAT.md](./GLOSSARY-FORMAT.md)', '[ADR-FORMAT.md](./ADR-FORMAT.md)'). However, neither sidecar (nor scripts/trace.sh) is present in the skill bundle as evaluated, so those references dead-end; that organization gap keeps it at 4 rather than 5, and it stays above 3 because the references are clearly signaled and only one level deep.

4 / 5

Total

17

/

20

Passed

Description

83%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 that explicitly covers both what the skill does and when to use it, with concrete actions and a genuine trigger clause in the user's own vocabulary. The only deductions are the second-person 'your plan' (voice penalty on specificity), a few missing natural synonyms, and slight overlap risk with generic plan-review or glossary-maintenance requests.

DimensionReasoningScore

Specificity

It lists multiple concrete actions — 'challenges your plan against the project's documented domain language and decision records', 'sharpens terminology', 'updates the glossary and ADRs inline as decisions crystallise' — which would be a 5 for coverage, but the second-person phrasing 'challenges your plan' incurs the guideline's 1-point voice penalty. It is not a 3 because far more than 1-2 concrete actions are named.

4 / 5

Completeness

Both halves are explicit: the what ('Grilling session that challenges... sharpens terminology, and updates the glossary and ADRs inline') and the when ('Use when user wants to stress-test a plan against their project's language and documented decisions') with a concrete trigger phrase. This matches the 5 anchor exactly; the when-clause is neither missing (3) nor merely adequate (4).

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'grilling session', 'stress-test a plan', 'glossary', 'ADRs', 'decision records', 'domain language' — phrases a user would plausibly say. It misses common synonyms such as 'pressure-test', 'interrogate', or 'challenge my plan', so it fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The documented-domain-language and decision-record angle ('challenges your plan against the project's documented domain language and decision records') carves a clear niche with distinct triggers. Minor overlap risk remains with generic plan-review requests and standalone glossary/ADR maintenance asks, fitting 'mostly distinct; minor overlap risk' rather than the minimal-conflict 5 anchor.

4 / 5

Total

17

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 2 possibly missing (./ADR-FORMAT.md, ./GLOSSARY-FORMAT.md)

Warning

referenced_paths_exist

Referenced path issues: 1 possibly missing (scripts/trace.sh)

Warning

Total

12

/

16

Passed

Repository

agranado2k/agentic-sdlc

Path

.agents/skills/grill-with-docs/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.