CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-builder

Reviews and improves SKILL.md packages by fixing audit findings, triggers, examples, evals, token budget, release proof, safety verdicts, comparator/baseline choices, and bounded code-lens hardening. Use when the user says improve a skill, fix a skill file, review SKILL.md, raise Tessl score, reduce context cost, add skill evals, or prepare a plugin skill for release.

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 ./Plugins/skill-factory/skills/code_quality_review/skill-builder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 content is dense and command-driven with a genuinely well-instrumented repair loop (baseline, single-change-per-iteration, rerun, flat-loop termination), and it avoids teaching known concepts. Its weaknesses are structural: significant duplication across the Validation/Execution Boundaries/Gotchas sections, two broken out-of-bundle reference paths, unnamed scripts, and inlined detail that its own guidance says belongs in references.

Suggestions

Deduplicate the release-evidence constraints repeated across Validation, Execution Boundaries, and Gotchas (the 20-scenario minimum, 300-run/20-run budget, and handoff receipt requirements each appear two to three times) by consolidating them into one reference file cited from each section.

Fix or remove the two reference paths that are absent from the bundle (Infrastructure/references/first-principles-factory-gate.md and Plugins/skill-factory/references/tessl-knowledgeos-capsule.md), and name the specific scripts/ files for each task instead of referencing scripts/ generically.

Move the long package-specific validation bullet lists out of the entrypoint into references (e.g., eval-enforcement-contract.md) and keep SKILL.md to the mode-selection and repair workflow, per the skill's own gotcha about not crowding the entrypoint.

DimensionReasoningScore

Conciseness

The body is lean and free of concept over-explanation, but the Validation, Execution Boundaries, and Gotchas sections restate the same constraints multiple times (the 20 gold-standard scenario minimum, the 300-run/20-run budget, and handoff receipt requirements each appear in two or three sections), which is more than minor trimming — fitting the mostly-efficient-but-could-be-tightened anchor.

3 / 5

Actionability

Concrete executable commands are given for the main gates ("./bin/ask skills external-review <target> --audit-level compat --json --robot", "./bin/ask sdk start <skill-path> --json --robot", "./bin/ask skills package verify <skill-path> --json --robot"), but several validation bullets name checks without supplying the command ("run scenario-quality, scorer-quality, and scorer-calibration through the SDK eval commands"), leaving minor gaps that keep it below fully copy-paste-ready.

4 / 5

Workflow Clarity

The numbered 7-step workflow has explicit validation checkpoints (record baseline, rerun the exact failed gate, three-flat-loops stop condition, final gates) and error-recovery feedback loops, but steps 2–3 cram multiple mode branches into single steps and "the focused gate" is undefined until the mode is known — clear sequence with most checkpoints rather than the fully explicit top anchor.

4 / 5

Progressive Disclosure

References are one level deep and listed in a dedicated section, but two referenced paths do not exist in the bundle ("Infrastructure/references/first-principles-factory-gate.md", "Plugins/skill-factory/references/tessl-knowledgeos-capsule.md"), scripts/ is referenced only generically without naming which script serves which task, and package-specific validation detail is inlined in the entrypoint — which the skill's own Gotcha ("Do not let package-specific repair details crowd the entrypoint") says to avoid — fitting the some-structure-but-could-be-better-organized anchor.

3 / 5

Total

14

/

20

Passed

Description

88%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 strong description: concrete action list, explicit third-person what-statement, and a rich natural-language trigger clause covering the main use cases. The only weaknesses are a couple of missing natural trigger variations and one overly broad trigger phrase with mild overlap risk.

DimensionReasoningScore

Specificity

"Reviews and improves SKILL.md packages by fixing audit findings, triggers, examples, evals, token budget, release proof, safety verdicts, comparator/baseline choices, and bounded code-lens hardening" enumerates nine concrete repair actions with comprehensive coverage of the skill-repair domain, matching the anchor for multiple specific concrete actions; it is not score 4 because coverage is comprehensive rather than having minor gaps.

5 / 5

Completeness

The description explicitly answers what ("Reviews and improves SKILL.md packages by fixing audit findings, triggers, examples, evals...") and when ("Use when the user says improve a skill, fix a skill file...") with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

"Use when the user says improve a skill, fix a skill file, review SKILL.md, raise Tessl score, reduce context cost, add skill evals, or prepare a plugin skill for release" provides seven natural trigger phrases with synonyms (improve/fix/review) and the SKILL.md filename, but common variations like "audit a skill" or "validate a skill" are missing, fitting the good-coverage-with-a-few-missing anchor rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Triggers like "fix a skill file", "raise Tessl score", and "prepare a plugin skill for release" carve a distinct skill-repair niche, but "reduce context cost" is broad enough to overlap with general token/context-optimization requests, making it mostly distinct with minor overlap risk rather than minimal conflict risk.

4 / 5

Total

18

/

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

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Plugins/skill-factory/skills/code_quality_review/skill-builder/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.