CtrlK
BlogDocsLog inGet started
Tessl Logo

panel-review-loop

Iteratively review and improve a Fallow user-facing surface across representative real-world projects until the panel has no blocking concerns.

61

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/panel-review-loop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 tight, well-structured iterative review loop with explicit validation and feedback checkpoints and a single clearly-signaled external reference; the only minor gap is unspecified mechanics for the 'define' and 'capture' steps.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: a one-line setup note plus a terse numbered loop and two guardrail sentences, with no padding or explanation of concepts Claude already knows, matching the score-5 anchor.

5 / 5

Actionability

Provides concrete, executable guidance with real commands and paths ('npm --prefix benchmarks run download-fixtures', 'benchmarks/fixtures/real-world/', 'panel-review'), but steps 1 and 3 ('Define the user-visible surface', 'Capture actual output') leave minor gaps in how to execute, fitting score 4 rather than the fully copy-paste-ready 5.

4 / 5

Workflow Clarity

A clearly sequenced 7-step loop with an explicit validation gate (panel-review on evidence) and feedback loop (re-run the same corpus, compare, stop when no blocks), plus guardrails ('Keep the corpus stable', 'Preserve output contracts'), matching the score-5 anchor.

5 / 5

Progressive Disclosure

Under 50 lines, well-organized into a numbered process with one clearly-signaled one-level-deep reference ([benchmark setup](../../../BENCHMARKS.md#comparative-benchmarks)); the simple-skill exception applies, so well-organized sections alone justify a 5.

5 / 5

Total

19

/

20

Passed

Description

53%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 states a clear purpose and niche but omits any 'when to use' trigger guidance, capping completeness, and offers only a thin set of concrete actions and natural trigger terms.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when polishing a Fallow UI surface, running a panel review, or deciding whether a surface change is ready to ship').

Enumerate more concrete actions to raise specificity (e.g., 'define success criteria, capture output, run panel-review, implement consensus fixes, re-run until no blocks').

Include common natural synonyms users would actually say (e.g., 'UI review', 'panel review', 'surface polish', 'blocking concerns') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Fallow user-facing surface') and 1-2 concrete actions ('review', 'improve') but does not enumerate a comprehensive set of actions, matching the score-3 anchor rather than 4 which requires several specific actions.

3 / 5

Completeness

The 'what' is clear (iteratively review and improve a surface until the panel has no blocks) 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

Includes relevant keywords ('review', 'improve', 'panel', 'blocking concerns') but lacks common natural variations or the phrases a user would naturally say, fitting 'some relevant keywords but missing common variations' rather than the fuller coverage of 4.

3 / 5

Distinctiveness Conflict Risk

The 'Fallow user-facing surface' and 'panel' framing carves a mostly distinct niche with only minor overlap risk against generic review skills, matching the score-4 anchor rather than the fully distinct triggers of 5.

4 / 5

Total

13

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
fallow-rs/fallow
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.