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

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

85%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, well-structured instructional skill with a clear interview workflow, explicit feedback checkpoints, and concrete challenge phrasings — held back from excellence by its references to GLOSSARY-FORMAT.md and ADR-FORMAT.md, neither of which exists in the bundle, which breaks both navigation and the executability of the glossary/ADR update steps.

Suggestions

Ship the missing sidecars: the body links to ./GLOSSARY-FORMAT.md and ./ADR-FORMAT.md but neither file exists in the bundle — add them (e.g., under references/) or fix the paths.

If the sidecars cannot be added, inline a minimal glossary-entry and ADR template directly in the body so the "update the glossary inline" and "create an ADR" steps remain executable standalone.

Clarify the end-of-session behavior — e.g., a closing step that summarizes resolved terms and any ADRs created — so the "until we reach a shared understanding" termination has a concrete finish line.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: no explanation of concepts Claude already knows (no "what is an ADR" preamble), the docs tree only conveys kit-specific layout, and terse rules like "Create files lazily — only when you have something to write" and "Don't batch these up — capture them as they happen" earn every token. Not 4 because there is no section that could be cut without losing actionable guidance.

5 / 5

Actionability

For an instruction-only skill the guidance is largely executable: copy-paste-ready challenge phrasings ("Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"), a concrete three-part ADR test, and explicit file-creation rules. Not 5 because "Use the format in [GLOSSARY-FORMAT.md](./GLOSSARY-FORMAT.md)" and "[ADR-FORMAT.md](./ADR-FORMAT.md)" point to files that are absent from the bundle, leaving those update steps unexecutable as written.

4 / 5

Workflow Clarity

The session flow is unambiguous with explicit checkpoints: the loop is "Interview me relentlessly... until we reach a shared understanding", questions are asked one at a time with feedback waited on, codebase-answerable questions are routed to exploration, and the three-part ADR checklist plus inline glossary updates define when each write action fires. Not 4 because both the termination condition and the per-question feedback loop are explicitly stated, which are the checkpoints that matter for a conversational skill.

5 / 5

Progressive Disclosure

Body structure is good (<what-to-do> vs <supporting-info>, clear subsections) and the two references are inline and clearly signaled one level deep — but both referenced sidecars (GLOSSARY-FORMAT.md, ADR-FORMAT.md) are missing from the bundle, so navigation dead-ends. Not 4 because broken reference targets are more than a minor organization gap; not 2 because the in-body structure itself is well organized and nothing bulky is wrongly inlined.

3 / 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 clearly and explicitly states both what the skill does (three concrete capabilities) and when to use it (explicit "Use when" clause with a specific trigger phrase), in third person and without padding. Minor room to grow via broader trigger synonyms and slightly more operational phrasing of the actions.

DimensionReasoningScore

Specificity

Names several concrete actions — "challenges your plan against the project's documented domain language and decision records", "sharpens terminology", "updates the glossary and ADRs inline" — covering the skill's behavior well. Not 5 because the actions are phrased at a high level ("challenges", "sharpens") rather than as fully concrete operations like the interview format or one-question-at-a-time mechanics.

4 / 5

Completeness

Explicitly answers both questions: the "what" lists three concrete capabilities (challenge against documented language/decisions, sharpen terminology, update glossary and ADRs inline) and the "when" is an explicit "Use when user wants to stress-test a plan against their project's language and documented decisions" trigger clause. Not 4 because the when-clause is already specific and concrete rather than merely present-but-imprecise.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "stress-test a plan", "plan", "glossary", "ADRs", "decision records", "domain language", "terminology" are phrases a user would plausibly say. Not 5 because common synonyms like "grill me", "quiz me", "poke holes in my plan", "challenge my design" are absent, and "grilling session" is kit jargon rather than a term most users would spontaneously use.

4 / 5

Distinctiveness Conflict Risk

The combination of plan grilling with the project's glossary/ADR artifacts is a clear niche with distinct triggers, so it is mostly distinguishable. Not 5 because it overlaps with a plain plan-review or interview skill (and an implied sibling "grill" skill) when a user just says "grill me on my plan" without mentioning documented decisions.

4 / 5

Total

17

/

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/google-books-clojure

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.