CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

common-skill-creator

Standardizes the creation and evaluation of high-density Agent Skills (Claude, Cursor, Windsurf). Ensures skills achieve high Activation (specificity/completeness) and Implementation (conciseness/actionability) scores. Use when: writing or auditing SKILL.md, improving trigger accuracy, or refactoring skills to reduce redundancy and maximize token ROI.

Quality

80%

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 ./.github/skills/common/common-skill-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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, appropriately progressive meta-skill: dense imperative rules, a sequenced workflow with validation and iteration checkpoints, and disciplined offloading to a real references/ bundle. Its weaknesses are internal redundancy (the same size/trigger thresholds stated 2–3 times), a garbled line in the workflow, and three orphaned reference files that the References section never surfaces.

Suggestions

Deduplicate the size/threshold rules: state the >10-line code-block, ≤100-line, and ≥90% trigger-rate rules once (e.g., in Content Quality) and remove their repeats in Anti-Patterns and the Quality Checklist — the Quality Checklist currently lists the ≥90% trigger requirement twice.

Fix the broken step 2 text ("what it , when it trigger, expected output format?") so the Capture-intent step reads as a complete, grammatical instruction.

Add 'load when' entries to the References section for the three orphaned files — benchmark.md, rubric.md, and tessl-best-practices.md — so all bundle content is discoverable from SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense and imperative with no AI-splaining of known concepts, but it repeats its own rules: the >10-line code-block rule appears in Content Quality, Anti-Patterns ("No Long Code Blocks"), and the Quality Checklist; the ≤100-line limit appears three times; and the ≥90% trigger-rate requirement appears twice within the same checklist ("Activation ≥ 90%" and "Trigger rate ≥90%"). Line 31 is also a broken sentence ("what it , when it trigger"), so the body clearly could be tightened — matching the 3 anchor rather than the minor-trims-only 4 anchor.

3 / 5

Actionability

For an instruction-only skill the guidance is mostly executable: a snapshot command (`cp -r <skill-dir> <workspace>/skill-snapshot/`), hard thresholds (≥90% accuracy, ≤100 lines, >10-line extraction), and per-step pointers to real reference files. It stops short of 5 because several workflow steps ("spawn parallel subagents", "run trigger eval queries") defer their exact execution to references rather than including the command or a copy-paste example inline.

4 / 5

Workflow Clarity

The 15-step workflow has a clear sequence with explicit validation checkpoints (Test with a with-skill/without-skill baseline, Evaluate on pass rate/tokens/time, Iterate on feedback, target ≥90% trigger accuracy) plus a pre-edit Snapshot safety step — near the 5 anchor. It lands at 4 because the new-skill and existing-skill tracks are merged into one continuous 1–15 numbering with awkward indentation, and validation mechanics are delegated to eval-workflow.md rather than stated as explicit validate/fix/retry steps at the point of use.

4 / 5

Progressive Disclosure

The 83-line body stays under its own 100-line budget and closes with a well-signaled References section where each of 8 linked files carries a "load when <condition>" cue; all 8 paths resolve to real files one level deep. Scoring against the actual bundle, three reference files (benchmark.md, rubric.md, tessl-best-practices.md) are never linked or mentioned from the body — orphaned content that keeps navigation from the easy 5-anchor standard.

4 / 5

Total

15

/

20

Passed

Description

87%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: third-person, explicit what-and-when structure with concrete "Use when" triggers and niche-specific terminology that minimizes conflict risk. Its only weakness is leaning on internal scoring jargon (Activation/Implementation/token ROI) where a couple of plain-language capability statements would read more naturally.

DimensionReasoningScore

Specificity

The description lists several specific actions — "Standardizes the creation and evaluation", "writing or auditing SKILL.md", "improving trigger accuracy", "refactoring skills to reduce redundancy" — in third-person imperative voice. It falls short of the 5 anchor because some capabilities are phrased through internal metric jargon ("Activation (specificity/completeness)", "Implementation (conciseness/actionability) scores", "token ROI") rather than concrete deliverables, leaving minor gaps in coverage.

4 / 5

Completeness

It explicitly answers both questions: "what" ("Standardizes the creation and evaluation of high-density Agent Skills (Claude, Cursor, Windsurf)") and "when" with a literal "Use when:" clause listing three concrete trigger conditions. This matches the 5 anchor (clear and explicit what AND when with concrete trigger phrases); the 4 anchor requires a 'when' that could be more explicit, which does not apply here.

5 / 5

Trigger Term Quality

It includes natural, user-sayable phrases ("writing or auditing SKILL.md", "improving trigger accuracy", "refactoring skills") plus the concrete file artifact "SKILL.md". A few natural terms users would plausibly say are missing (e.g., "create a skill", "skill quality", "evals"), so it matches the 4 anchor (good coverage, a few natural terms missing) rather than the comprehensive-synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche — authoring/auditing agent-skill files — anchored by distinctive artifacts ("SKILL.md", "trigger accuracy", "token ROI") that few other skills would claim. Trigger phrases are specific to this niche, giving minimal conflict risk, matching the 5 anchor.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

HoangNguyen0403/agent-skills-standard

Path

.github/skills/common/common-skill-creator/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.