CtrlK
BlogDocsLog inGet started
Tessl Logo

quality-loop

Use this workflow recipe when a draft, plan, proposal, or other deliverable should be independently reviewed and revised until it satisfies explicit quality criteria.

66

Quality

80%

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 ./examples/dynamicworkflow/skills/skills/quality-loop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 well-structured, actionable recipe with an explicit bounded feedback loop and strong validation checkpoints. Main improvement is de-duplicating the placeholder rule and considering whether the code shape belongs in a reference file.

Suggestions

State the placeholder-acceptance rule once (e.g. in Review Discipline) and reference it from the Process and code sections instead of repeating it three times.

Consider moving the full Python workflow shape to a references/ file and keeping a concise outline inline, so SKILL.md reads as an overview.

Tighten the Compilation Rules by merging overlapping items (e.g. the structured-output and 'read the structured object' points) to reduce token cost.

DimensionReasoningScore

Conciseness

Lean and free of basic-concept padding, but the placeholder-acceptance rule is restated in Process step 4, the code instruction, and Review Discipline, which could be consolidated.

4 / 5

Actionability

Provides a concrete, mostly-executable Python workflow shape plus explicit numbered steps, though it is explicitly a template to adapt rather than literal copy-paste code.

4 / 5

Workflow Clarity

A clearly sequenced nine-step loop with explicit validation (structured approved/feedback schema), an error-recovery feedback loop, and a hard three-review bound with stop conditions.

5 / 5

Progressive Disclosure

No bundle files exist; the single self-contained SKILL.md is well-sectioned (Process, workflow shape, Review Discipline, Compilation Rules), though it is one monolithic file rather than a pointed overview with references.

4 / 5

Total

17

/

20

Passed

Description

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

A clear, trigger-led description that answers both what and when with natural language and a specific niche. It could be sharpened by naming the bounded-loop mechanics and a few more synonyms.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ('independently reviewed and revised') but does not enumerate the bounded loop, structured output, or three-review limit, so coverage is not comprehensive.

3 / 5

Completeness

Explicit 'Use this workflow recipe when ...' trigger answers when, and 'independently reviewed and revised until it satisfies explicit quality criteria' answers what, both with concrete phrasing.

5 / 5

Trigger Term Quality

Includes natural user terms ('draft', 'plan', 'proposal', 'deliverable', 'quality criteria') but omits common synonyms like 'feedback', 'iterate', or 'polish'.

4 / 5

Distinctiveness Conflict Risk

The iterative review-revise-until-criteria niche is mostly distinct, with only minor overlap risk against generic review skills.

4 / 5

Total

16

/

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
trpc-group/trpc-agent-go
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.