CtrlK
BlogDocsLog inGet started
Tessl Logo

grill-with-docs

一个用来打磨计划或设计的持续追问式访谈,并在过程中创建文档(ADRs 和词汇表)。

48

Quality

50%

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 ./skills/engineering/grill-with-docs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

51%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 exceptionally concise but reduces to a bare delegation to two other skills with no concrete steps, sequencing, or guidance on how they combine, making it minimally actionable.

Suggestions

Spell out how /grilling and /domain-modeling relate: the order to run them, what to feed from one into the other, and where the ADRs/glossary are written.

Add a short concrete checklist of the expected outputs (ADR entries, glossary terms) so the delegation has a verifiable end state.

If the two referenced skills fully define the workflow, state that explicitly so the single line reads as deliberate delegation rather than an underspecified instruction.

DimensionReasoningScore

Conciseness

The single-line body ('运行一次 /grilling session,并使用 /domain-modeling skill。') is maximally lean with zero padding and assumes Claude's competence; every token earns its place.

5 / 5

Actionability

It only offers a high-level hint (invoke /grilling and /domain-modeling) with no concrete steps, specifics on how to combine them, or what to produce, missing the specific steps to execute.

2 / 5

Workflow Clarity

A rough sequence is implied (run /grilling, then use /domain-modeling) but the relationship and ordering between the two skills is poorly defined and there are no checkpoints, leaving many gaps.

2 / 5

Progressive Disclosure

No bundle files exist and there is nothing to offload, but the body has no section structure or navigation at all; it is acceptable yet unorganized for such a minimal skill.

3 / 5

Total

12

/

20

Passed

Description

50%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 conveys a clear purpose and concrete artifacts (ADRs, glossary) but provides no explicit usage triggers and only modest keyword coverage, leaving it indistinct from related planning skills.

Suggestions

Add an explicit 'Use when...' trigger clause naming the situations a user would describe (e.g., refining a design, deciding between options, needing to capture decisions as ADRs).

Include natural synonyms and variations users actually say (e.g., '设计评审', '决策记录', 'ADR', 'glossary/词汇表') to improve trigger term coverage.

Sharpen the action list beyond a single verb to distinguish it from general planning/domain-modeling skills.

DimensionReasoningScore

Specificity

Names the domain ('打磨计划或设计' / refine plans or designs via '持续追问式访谈') and concrete outputs ('创建文档(ADRs 和词汇表)'), giving 1-2 concrete actions but not comprehensive coverage.

3 / 5

Completeness

There is a clear 'what' (a questioning-style interview that refines plans and produces ADRs/glossary), but 'when' is entirely missing with no 'Use when...' guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Relevant keywords exist (打磨计划/设计, ADRs, 词汇表, 追问式访谈) but common natural variations or synonyms a user would say are missing, and there is no explicit trigger clause.

3 / 5

Distinctiveness Conflict Risk

The grilling-interview-for-plans-with-ADRs niche is somewhat specific, but without trigger phrases it could still overlap with general planning or domain-modeling skills.

3 / 5

Total

12

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
vinvcn/mattpocock-skills-zh-CN
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.