CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

loop-me

Grill me about specs for the workflows I want to build, within this workspace.

Quality

73%

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 ./.agents/skills/loop-me/SKILL.md

The canonical home for this skill is loop-me in mattpocock/skills

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-organized instruction-only skill that defines its own vocabulary, gives a testable definition of done, and specifies the workspace layout concretely. Its only soft spots are reliance on an only-parenthetically-defined /grilling discipline and a process the reader must assemble from sections rather than follow as steps.

DimensionReasoningScore

Conciseness

The ~26-line body is lean and teaches only its own invented vocabulary ("Push right: defer the checkpoint as far as it will go", "The user reads a brief, not a draft"); it explains nothing Claude already knows and every sentence carries instruction.

5 / 5

Actionability

Concrete, specific guidance throughout — "a round of questions at a time, a recommended answer attached to each", "Create, edit, and delete specs as the grilling resolves things", "interview them about their world" when NOTES.md is thin — with one minor gap: the "/grilling" discipline it depends on is only characterized parenthetically rather than spelled out.

4 / 5

Workflow Clarity

The iterative process is legible (grill in rounds, resolve, create/edit/delete specs) with an explicit validation checkpoint — "done when an implementer agent could build it without asking a single question. Grill until then; nothing is done while a question remains" — but the sequence must be assembled across sections rather than laid out as steps.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external reference files; content is split into well-organized sections (The loop lens, Vocabulary, Definition of done, The workspace) and the only cross-skill reference ("/grilling") is clearly signaled one level deep, satisfying the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

48%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 distinctive niche but is written in first/second-person voice, names only one action, and entirely lacks a "Use when..." trigger clause. It reads like an argument hint rather than a self-contained third-person description with explicit trigger guidance.

Suggestions

Rewrite in third person with what+when form, e.g.: "Runs a stateful grilling session that interrogates the user round by round until each workflow spec in workflows/*.md could be implemented without a single question. Use when the user wants to design or refine a workflow, or when workflows/ or NOTES.md need new or sharpened specs."

Add natural trigger terms and synonyms users would actually say — "design a workflow", "plan a recurring task", "spec out an automation" — alongside the existing "specs" and "workflows".

State the concrete actions and outputs explicitly (ask rounds of questions each with a recommended answer; create, edit, and delete specs in workflows/*.md; record canonical terms in NOTES.md) so the "what" is comprehensive rather than implied.

DimensionReasoningScore

Specificity

"Grill me about specs for the workflows I want to build" names the domain (workflow specs) and one concrete action (grilling the user), fitting the 1-2-concrete-actions anchor (3); however it is written in first/second person ("Grill me", "I want to build") rather than third person, so the voice guideline reduces specificity by 1.

2 / 5

Completeness

The "what" is clear (grill the user to produce workflow specs), but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

"specs" and "workflows" are relevant natural keywords, but common variations users would actually say ("design", "plan", "automate", "interview me") are absent, matching the "some relevant keywords but missing common variations or synonyms" anchor.

3 / 5

Distinctiveness Conflict Risk

The niche — interrogating the user to specify recurring workflows "within this workspace" — is fairly distinct with domain-specific trigger words ("specs", "workflows"), carrying only minor overlap risk against general planning or init-style skills.

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

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

koenighotze/wheel-of-meeting

Path

.agents/skills/loop-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.