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

81%

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

71%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, actionable interviewing skill with concrete challenge scripts and a disciplined ADR gate, held back by a broken disclosure structure: the two referenced format sidecars are missing from the bundle entirely. Shipping GLOSSARY-FORMAT.md and ADR-FORMAT.md alongside the body would resolve its main defect.

Suggestions

Add the referenced ./GLOSSARY-FORMAT.md and ./ADR-FORMAT.md to the skill bundle (e.g., under references/) — both links in the body currently dangle, leaving the glossary and ADR entry formats unspecified.

Include the attribution-referenced .agents/skills/LICENSE-mattpocock-skills.md or trim the footer to a plain source note, so the third reference is also not a dead path.

Trim the glossary-purity passage to a single sentence (e.g., 'The glossary contains only agreed domain terms — no implementation details') and drop the duplicated AGENTS.md-authority explanation to tighten conciseness.

DimensionReasoningScore

Conciseness

Efficient, prescriptive instruction with no explanations of concepts Claude already knows — the docs-layout tree and verbatim challenge phrases earn their tokens. Minor trimmable padding: 'The glossary should be totally devoid of implementation details. Do not treat it as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else' says one thing three ways, and the AGENTS.md-as-authority point is made twice. Not 5 for these small redundancies; well above 3.

4 / 5

Actionability

Concrete, executable guidance throughout for an instruction-only skill: verbatim challenge scripts ('Your glossary defines "cancellation" as X, but you seem to mean Y — which is it?'), a hard three-part ADR test, lazy file-creation rules, and an explicit AGENTS.md fallback for foreign layouts. Not 5 because 'Use the format in [GLOSSARY-FORMAT.md]' and '[ADR-FORMAT.md]' point at files that do not exist in the bundle, so the entry/record formats — a key detail for the update actions — are left to improvisation.

4 / 5

Workflow Clarity

The session flow is clear — explore docs first, interview one question at a time with a recommended answer per question, then condition→action pairs (conflict → call out; resolved → update inline; all three ADR criteria met → offer ADR; ambiguous context → ask, since ambiguity is itself a finding). The three-criteria gate is an explicit checkpoint. Not 5 because there is no verification step after glossary/ADR writes (e.g., re-reading the updated entry against the glossary's purity rule), a minor validation gap; the destructive/batch cap does not apply since edits are incremental single-file updates.

4 / 5

Progressive Disclosure

The structure is well designed — concise session guidance inline with formats delegated to one-level-deep, clearly signaled links at the point of use — but scored against the actual bundle, both referenced sidecars (GLOSSARY-FORMAT.md, ADR-FORMAT.md) and the footer's LICENSE file are absent, so every reference dangles and the split is broken in practice. Not 4 because missing referenced files are more than a 'minor organization gap'; not 2 because the inline content is well sectioned and nothing that belongs in a sidecar is inlined.

3 / 5

Total

15

/

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 states both capability and trigger with concrete, natural language. Its only weaknesses are a few missing user-side synonyms and mild overlap risk with generic plan-stress-testing skills.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'challenges your plan against the project's documented domain language and decision records', 'sharpens terminology', 'updates the glossary and ADRs inline' — with only minor coverage gaps (e.g., the one-question-at-a-time interview format is not surfaced). Not 5 because the actions stop short of the fully concrete operation level of the anchor example, and not 3 since well more than 1–2 actions are named.

4 / 5

Completeness

Explicitly answers both: what ('Grilling session that 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. Anti-drift check: anchor 4 requires that 'when' could be more explicit — here the when-clause is already explicit and specific, so 5 is the better fit.

5 / 5

Trigger Term Quality

Good natural-keyword coverage: 'grilling session', 'stress-test a plan', 'glossary', 'ADRs', 'decision records', 'domain language', 'sharpens terminology'. Not 5 because common user synonyms like 'poke holes in my plan', 'interrogate my design', 'design review', or 'ubiquitous language' are absent, leaving a few natural entry phrases uncovered.

4 / 5

Distinctiveness Conflict Risk

The documented-domain-language/ADR niche is distinct and the qualifier 'against their project's language and documented decisions' narrows triggering well. Not 5 because 'grilling session' and 'stress-test a plan' are generic enough to overlap with closely related plan-review or generic grill skills (the footer notes it was adapted from just such a sibling).

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/tic-tac-toe-haskell

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.