CtrlK
BlogDocsLog inGet started
Tessl Logo

batch-grill-me

持续追问式访谈,每一轮同时提出当前 frontier 上的所有问题。

51

Quality

56%

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/in-progress/batch-grill-me/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers a clear, well-sequenced iterative workflow with a strong validation gate, but it is presented as an unsectioned prose wall and lacks a concrete worked example of a round. Adding headers and one sample round would improve both organization and actionability.

Suggestions

Break the prose into labeled sections (e.g., 'Design tree', 'Rounds & frontier', 'Facts vs. decisions', 'Termination') so the structure is scannable.

Add a short worked example showing one round (numbered questions with recommended answers and the resulting frontier recompute) to make the procedure concrete.

Tighten the repeated frontier-recompute explanation across paragraphs two and three into a single statement to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is lean and defines only its own skill-specific terms (design tree, frontier), but the frontier-recompute logic is restated across the second and third paragraphs, so it is 'mostly efficient but could be tightened' rather than fully lean.

2 / 3

Actionability

It gives concrete procedural guidance ('给每个问题编号并提供推荐答案,然后等待用户回答', dispatch sub-agents for facts, defer dependent questions), but offers no worked example of a single round, leaving the guidance specific yet not fully copy-paste concrete.

2 / 3

Workflow Clarity

The round-based process is clearly sequenced with a feedback loop (user answers reshape the tree and recompute the frontier) and an explicit validation gate ('Frontier 为空时 session 才结束' and '在用户确认已经达成共同理解前,不要采取行动'), matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

No bundle files exist and the body is a single undifferentiated block of prose with no section headers; for a sub-50-line skill with no external references, a 3 requires well-organized sections, which are absent here.

2 / 3

Total

9

/

12

Passed

Description

50%

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 the skill's core mechanism but is generic and trigger-less: it states what happens without saying when to use it or which natural user phrases should invoke it. Adding an explicit 'Use when...' clause with plain-language triggers would move it up a level.

Suggestions

Add an explicit 'Use when...' trigger clause with natural user phrasing (e.g., when the user has a complex decision or design to work through and needs structured questioning to reach shared understanding).

Replace or gloss the jargon term 'frontier' with plain language so the description reads as something a user would actually say.

List a few concrete actions the skill performs (e.g., 'numbers each open question, proposes a recommended answer, and waits per round') to raise specificity.

DimensionReasoningScore

Specificity

The description names the domain ('持续追问式访谈') and one concrete behavior ('每一轮同时提出当前 frontier 上的所有问题'), but lists only a single conceptual action rather than multiple specific concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor.

2 / 3

Completeness

It clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

It carries relevant concepts ('访谈', '追问') but leans on the technical term 'frontier' and includes no natural phrasing a user would spontaneously say; this fits 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The frontier/design-tree framing gives it a niche, but the description is abstract and lacks explicit triggers, so it could still overlap with general clarification/interviewing skills.

2 / 3

Total

8

/

12

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.