CtrlK
BlogDocsLog inGet started
Tessl Logo

panel-review

Review a Fallow design, plan, workflow, CLI surface, documentation architecture, or user experience with representative end-user and domain-expert perspectives before implementation.

62

Quality

72%

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/panel-review/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 tight, well-sequenced review playbook with concrete steps, a verification checkpoint, and clear synthesis categories; it stays lean and needs no external references, with only minor actionability and feedback-loop gaps.

Suggestions

Add an explicit feedback loop for step 5, e.g. "If a load-bearing claim fails verification, demote it to a follow-up and re-synthesize before recording decisions."

Give one concrete line on how to choose the "representative users plus specialists" in step 3 so reviewer selection is repeatable rather than left to judgment.

DimensionReasoningScore

Conciseness

The body is a lean seven-step list plus two short guardrail lines with no padding and no explanation of concepts Claude already knows; every line earns its place.

5 / 5

Actionability

Steps are concrete and directive ("Build one evidence package from current source, live behavior, and relevant public contracts", "Synthesize consensus under: Fix before change / Fix now / Follow-up / No action", "Record approved decisions in the active `.plans/<task>.md`"), with only minor gaps such as how to actually select or recruit reviewers.

4 / 5

Workflow Clarity

A clear numbered seven-step sequence includes an explicit verification checkpoint ("Verify load-bearing claims against source before accepting them") and a synthesis framework, but there is no explicit error-recovery feedback loop after verification fails.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is well organized as a numbered process with closing guardrails, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

18

/

20

Passed

Description

58%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 is specific about what kinds of Fallow artifacts get reviewed and from whose perspectives, but it relies on one action verb and lacks an explicit Use-when trigger clause, leaving completeness and specificity in the mid-range.

Suggestions

Add an explicit trigger clause such as "Use when reviewing a Fallow design, plan, workflow, CLI surface, docs architecture, or UX before implementation, or when the user asks for a panel/end-user review."

Vary the action verbs to show distinct capabilities (e.g., "Recruit representative reviewers, gather blockers and follow-ups, verify load-bearing claims, and synthesize consensus decisions") rather than a single "Review" action.

DimensionReasoningScore

Specificity

The description names many concrete review surfaces ("design, plan, workflow, CLI surface, documentation architecture, or user experience") but bundles them under a single action ("Review ... with representative end-user and domain-expert perspectives"), so it names the domain well without listing several distinct actions.

3 / 5

Completeness

It gives a clear "what" (review Fallow artifacts via end-user and domain-expert perspectives) but only weakly implies "when" via "before implementation" and lacks an explicit "Use when..." clause, which caps completeness at 3 per the guideline.

3 / 5

Trigger Term Quality

Natural terms like "design", "plan", "workflow", "CLI surface", "documentation", "user experience", and "review" appear, and "before implementation" is a recognizable trigger phrase; a few common synonyms are missing but coverage is good.

4 / 5

Distinctiveness Conflict Risk

Tying the skill to "Fallow" and enumerating specific artifact types gives it a clear niche with minimal conflict risk, though "review this design/plan" phrasing could loosely overlap with generic review skills.

4 / 5

Total

14

/

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