CtrlK
BlogDocsLog inGet started
Tessl Logo

loop-me

在这个工作区中,就我想构建的工作流规格访谈我。

58

Quality

68%

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/loop-me/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 a lean, well-structured instruction-only skill that introduces novel domain vocabulary and includes an explicit definition-of-done checkpoint. It scores high on conciseness and structure, with only minor gaps in worked examples and enumerated process steps.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence; the vocabulary it introduces (Loop, Workflow, Trigger, Checkpoint, Push right, Brief) is novel domain framing rather than padding, so nearly every token earns its place.

5 / 5

Actionability

Concrete guidance is given for an instruction-only skill (one question at a time, each with a recommended answer, push-right, brief format, specs in workflows/*.md), but no example questions or sample specs are shown, leaving minor gaps versus fully copy-paste-ready material.

4 / 5

Workflow Clarity

The process has a clear implied sequence (grill, then create/edit/delete specs) with an explicit validation checkpoint in the 'definition of done' section, but the steps are not enumerated and full error-recovery feedback loops are not spelled out.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files, the content is well-organized into clear sections (loop lens, vocabulary, definition of done, workspace), qualifying for the top anchor under the simple-skill exception.

5 / 5

Total

18

/

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 clearly states what the skill does but omits any explicit trigger guidance and uses only a couple of generic keywords. It lands at the midpoint across all dimensions due to the missing "when to use" clause and limited natural trigger terms.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants to design or spec out a workflow and is willing to be interviewed for it.'

Broaden trigger-term coverage with natural user phrasings like 'design a workflow', 'spec out a workflow', or 'build a workflow' in addition to 访谈/工作流.

Restate the description in third person (e.g. 'Interviews the user about workflow specs') instead of first person ('访谈我') to align with the rubric's voice guidance.

DimensionReasoningScore

Specificity

Names the domain ("工作流规格"/workflow specs) and one concrete action ("访谈我"/interview me), matching the anchor for naming a domain plus 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

States a clear "what" (interview the user about workflow specs) but provides no "Use when..." trigger clause, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Contains some relevant keywords ("工作流"/workflow, "访谈"/interview) but misses the natural phrasings a user would say when they need this skill, such as "design a workflow" or "spec out a workflow".

3 / 5

Distinctiveness Conflict Risk

The interviewing-about-workflow-specs framing is somewhat specific but "workflow" is broad and could overlap with general workflow-design skills, matching the somewhat-specific-but-overlap anchor.

3 / 5

Total

12

/

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.

Validation15 / 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
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.