CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cs-engineer-grill

Cross-role engineering grill — Matt Pocock 7 questions per role × 3 roles (fullstack / frontend / backend) = up to 21 forcing questions, one per turn, with canon citations and kill criteria. Default: ask which lane first; `--all` runs all 21.

Quality

77%

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 ./.gemini/skills/cs-engineer-grill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 instruction-only skill: concrete routing rules with signal keywords, 21 specific forcing questions, explicit turn discipline with a kill-criterion checkpoint, and defined output artifacts. The remaining gaps are minor — elided decision-engine arguments, a duplicated artifact-path rule, and references to files that are not part of this bundle.

Suggestions

Specify the decision-engine invocations fully (arguments, expected output) in the 'After the grill' section, or point to a usage doc, instead of eliding with '...'.

State the /tmp artifact-path rule once — either in Discipline #5 or in Output expectations — and cross-reference it from the other place.

Ship the per-lane forcing_questions.md and decision-engine scripts inside this skill's own references/ and scripts/ directories (or link resolvable paths) so the referenced files exist within the bundle.

DimensionReasoningScore

Conciseness

The body is tight — signal keyword lists, one-line questions, and rule statements with no explanations of concepts Claude already knows (LCP, RPO, tenancy are named, not explained). Minor trims remain: the /tmp artifact path is stated twice (Discipline #5 and Output expectations) and the opening sentence restates the description, so it sits at anchor 4 rather than 5.

4 / 5

Actionability

Concrete throughout: exact recommended-answer format ('Recommended: <answer>, because <one-sentence rationale from cited canon>'), 21 specific questions, a defined artifact path pattern, and named scripts to run after the grill. Minor gaps keep it below 5: the decision-engine invocations elide arguments ('fullstack_decision_engine.py ...') and the full question definitions live in external files.

4 / 5

Workflow Clarity

Phases are clearly sequenced (route lane → walk depth-first → kill-criterion STOP → run decision engine → digest) and 'If the user's answer trips it, STOP and resolve before continuing' is an explicit checkpoint. It falls short of anchor 5 because failure cases (missing reference file, script error) are unhandled and the post-grill script arguments are unspecified.

4 / 5

Progressive Disclosure

Each lane summarizes its 7 questions inline and points one level deep to the full file ('Questions live in engineering-team/skills/senior-frontend/references/forcing_questions.md') — well signaled and easy to navigate. Scored against the actual bundle structure (only SKILL.md; no references/, scripts/, or assets/ shipped, and none of the referenced paths resolve anywhere in the workspace), the external, unverifiable references are a minor organization gap that holds it at anchor 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

71%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 highly specific about mechanics (21 forcing questions, one per turn, canon citations, kill criteria, lane routing) and largely distinct from sibling skills. Its main weakness is the absence of any explicit 'Use when...' trigger guidance, which caps completeness, and its keyword set misses several natural phrasings a user might use when they need their plan challenged.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user presents an engineering plan or architecture to challenge before locking it in, or asks to be grilled on stack or design decisions.'

Include natural user phrasings as trigger terms: 'challenge my plan', 'stress-test my architecture', 'review my stack decision', 'ask me hard questions'.

Move 'architecture' (currently only in the argument-hint) into the description so the primary trigger noun appears in the searchable text.

DimensionReasoningScore

Specificity

The description names multiple concrete mechanics: '7 questions per role × 3 roles (fullstack / frontend / backend) = up to 21 forcing questions, one per turn, with canon citations and kill criteria' plus routing behavior ('Default: ask which lane first; `--all` runs all 21'). Coverage of the skill's function is comprehensive with no vague filler, matching anchor 5 rather than anchor 4's 'minor gaps in coverage'.

5 / 5

Completeness

The 'what' is explicit and detailed, but there is no 'Use when...' clause or equivalent trigger guidance; 'Default: ask which lane first; `--all` runs all 21' describes runtime behavior, not when to invoke the skill. Per the judging guideline, a missing explicit trigger clause caps completeness at 3, and it cannot be 4 because the 'when' is never stated.

3 / 5

Trigger Term Quality

Natural terms are present ('engineering', 'fullstack / frontend / backend', 'grill', 'questions'), giving good keyword coverage, but common user phrasings such as 'challenge my plan', 'stress-test', 'review', or 'architecture' are absent from the description (architecture appears only in the argument-hint). A few natural terms are missing, so anchor 4 fits better than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

'Cross-role engineering grill', 'Matt Pocock', and the three named role lanes carve a clear niche with distinct triggers, though closely related sibling commands (/cs-grill-bizops, /cs-fullstack-review and the other single-lane reviews) share trigger territory. This is 'mostly distinct; minor overlap risk' (anchor 4) rather than the minimal-conflict anchor 5.

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/cs-engineer-grill/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.