CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

grill-me

Adversarial plan interview before implementation.

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 ./optional-skills/software-development/grill-me/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 an exemplary instruction-only skill: it defines one crisp mechanic (frontier rounds over a design tree), gives copy-paste formats and concrete question scripts, sequences a clear loop with an explicit stopping condition and alignment gate, and closes with a verification checklist. The only real trim candidate is the provenance line, and the distinction between facts-to-look-up-yourself versus user-decisions is unusually well drawn.

DimensionReasoningScore

Conciseness

The body is dense and imperative with no tutorials on concepts Claude already knows, but a few tokens could still be trimmed: the provenance line "Combines the phase discipline of the original with the frontier-rounds mechanic from mattpocock/skills' `grilling`" adds context rather than instruction, and flourishes like "a guess wearing a question mark" are stylistic. Matches anchor 4 (efficient, minor trimmable instances), not anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Fully concrete instruction-only guidance: a copy-paste round format template ("❓ Q1 — <question title>... ➡️ Recommendation: ..."), specific question scripts ("Why this approach and not X?", "What if volume is 100x expected?"), an exact synthesis prompt ("Aligned? Should I start implementing, or adjust anything?"), and named tools (search_files / read_file / terminal / delegate_task). Per the scoring notes, absence of code is not penalized when guidance is this actionable — anchor 5.

5 / 5

Workflow Clarity

The process is a clearly sequenced loop — map the design tree, ask the current frontier in one message, wait, reshape the tree from answers, recompute the frontier, repeat until empty, then synthesize with an explicit alignment gate ("Do not act on the plan until the user confirms"). A dedicated Verification checklist closes it, matching anchor 5's feedback loops plus checklists; the skill is not destructive/batch, so no cap applies.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed: every section (When to Use, Core Mechanic, Question Coverage, Synthesis, Pitfalls, Verification) is short and load-bearing, so nothing clearly belongs in a separate reference file. Sections are well-organized with clear headers and easy navigation, satisfying the well-organized-structure condition for a self-contained skill.

5 / 5

Total

19

/

20

Passed

Description

53%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 short, third-person, and unambiguous about what the skill does, but it is under-powered as a trigger document: it lacks any explicit "Use when..." invocation guidance and misses the natural phrases ("grill me", "stress test") that users actually say for this need. The body's excellent "When to Use" section contains exactly the trigger material the description is missing.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user says 'grill me', asks to stress-test or interview a plan, or before starting complex work with unresolved decisions."

Fold in the natural synonyms from the body ("grill", "stress test", "interview my plan") so the description matches how users actually phrase the request.

Optionally add one more concrete capability phrase (e.g. "models the plan as a decision tree and asks round-by-round questions") to lift specificity from one action to several.

DimensionReasoningScore

Specificity

"Adversarial plan interview" names the domain and one concrete action with a manner qualifier, and "before implementation" adds timing — but only 1-2 actions are stated, not the several specific actions anchor 4 requires. It is well above anchor 2's generic, minimal-action phrasing (e.g. "Processes PDF files").

3 / 5

Completeness

The "what" is clear (adversarial plan interview), but there is no explicit "Use when..." trigger clause — "before implementation" only weakly implies when via lifecycle timing. Per the guideline, a missing 'Use when' clause caps completeness at 3, and anchor 3 fits exactly: clear what, weakly implied when.

3 / 5

Trigger Term Quality

"plan" and "interview" are natural terms a user would plausibly say, but the description omits common synonyms users actually use for this need — "grill me", "stress test", "critique my plan", "review my plan". This matches anchor 3: some relevant keywords, missing common variations.

3 / 5

Distinctiveness Conflict Risk

"Adversarial plan interview before implementation" carves a fairly distinct niche (pre-implementation stress-testing), but the broad word "plan" leaves minor overlap risk with general planning and plan-review skills, matching anchor 4 rather than anchor 5's clear-niche-with-distinct-triggers.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/software-development/grill-me/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.