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

76%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/grill-with-docs/SKILL.md

The canonical home for this skill is grill-with-docs in agranado2k/google-books-clojure

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-organized, mostly lean instruction skill with concrete example dialogues and clear condition-triggered tactics. Its main defects are the two dangling sidecar references — the glossary and ADR format files it instructs Claude to use do not exist — and minor redundant moralizing about the glossary's purity.

Suggestions

Ship the referenced GLOSSARY-FORMAT.md and ADR-FORMAT.md alongside SKILL.md, or inline minimal entry/record templates, since the skill's core outputs currently have no defined format.

Trim redundant emphasis sentences (e.g., "It is a glossary and nothing else") to tighten token efficiency.

Clarify the ordering between the what-to-do interview loop and the during-session tactics (e.g., note that the tactics apply while walking the design tree) to make the workflow fully explicit.

DimensionReasoningScore

Conciseness

The body is mostly lean directive prose with quoted example dialogues and a compact directory sketch; only minor preachy redundancy could be trimmed ("It is a glossary and nothing else" and "it is the authority here, not this file"), matching the 4 anchor rather than 5's every-token-earns-its-place.

4 / 5

Actionability

The interview guidance is concrete (example callouts like "Your glossary defines 'cancellation' as X…" and a crisp three-part ADR test), but the formats for the skill's two output artifacts are delegated to GLOSSARY-FORMAT.md and ADR-FORMAT.md, which do not exist in the bundle — a missing key detail that fits the 3 anchor ('concrete guidance but incomplete') rather than 4.

3 / 5

Workflow Clarity

The interaction loop is explicit (ask one question at a time, explore the codebase when a question is answerable there, update the glossary inline) and the tactics are clearly condition-triggered; no destructive or batch operations are involved, so the missing-validation cap does not apply — matching the 4 anchor, with the 5 anchor's explicit validation/feedback loops not applicable to this conversational skill.

4 / 5

Progressive Disclosure

In-body structure is good with clearly signaled, one-level-deep references ([GLOSSARY-FORMAT.md](./GLOSSARY-FORMAT.md), [ADR-FORMAT.md](./ADR-FORMAT.md)), but both referenced files are absent from the actual bundle, so navigation leads nowhere — worse than the 4 anchor's 'minor organization gaps' but better than the 2 anchor's inlined-wall-of-text, landing at 3.

3 / 5

Total

14

/

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.

A strong description that clearly states capabilities and an explicit, specific 'Use when' trigger with natural keywords. Its main flaws are second-person phrasing and a when-clause that largely echoes the what-clause instead of broadening trigger coverage with synonyms.

Suggestions

Rewrite in third person (e.g., "Challenges the user's plan against…") to match the required voice and avoid the specificity penalty.

Broaden the trigger clause with synonyms users actually say, such as 'pressure-test', 'interrogate', 'challenge my plan', or 'review my plan critically', rather than repeating the capability sentence.

Consider naming the artifacts users might mention verbatim ('ubiquitous language', 'decision records', 'ADR review') to improve trigger matching.

DimensionReasoningScore

Specificity

Names the domain and three concrete actions ("challenges your plan", "sharpens terminology", "updates the glossary and ADRs inline"), matching the 4 anchor, but it is written in second person ("challenges your plan", "Use when user wants") rather than third person, which the guidelines penalize by one point.

3 / 5

Completeness

Explicitly answers both what ("challenges your plan… sharpens terminology, and updates the glossary and ADRs inline") and when ("Use when user wants to stress-test a plan against their project's language and documented decisions") with a concrete trigger phrase, matching the 5 anchor; the 4 anchor's 'when could be more specific' does not apply.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — "stress-test a plan", "grilling", "glossary", "ADRs", "decision records" — giving good coverage, though common synonyms like "pressure-test", "interrogate", or "challenge my plan" are missing, keeping it below the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The docs-anchored framing ("documented domain language and decision records") carves a distinct niche versus generic plan-review or code-review skills, with only minor overlap risk against a plain 'grill me about my plan' skill — matching the 4 anchor rather than 5's fully minimal conflict risk.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

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

Warning

Total

15

/

16

Passed

Repository

agranado2k/tic-tac-toe-with-agentic-sdlc

Path

.claude/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.