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

83%

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

The canonical home for this skill is common-skill-creator in HoangNguyen0403/agent-skills-standard

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 dense, well-budgeted instruction skill: no filler, concrete thresholds and commands, an explicit iterate/evaluate loop, and an exemplary condition-annotated references table. Its weaknesses are execution-level — a broken sentence in the workflow, an undefined 'iteration dir' convention, merged two-track step numbering, and three orphaned bundle files that SKILL.md never surfaces.

Suggestions

Fix step 2's broken sentence ('what it , when it trigger, expected output format?') and define the iteration-directory convention referenced by 'rerun into next iteration dir', ideally with the exact path pattern used in eval-workflow.md.

Restructure the Workflow section so the new-skill and existing-skill tracks are two separate numbered lists (or headed subsections) instead of one 15-step sequence, so readers cannot misattribute steps 9–15.

Add load-when links for the three orphaned bundle files — benchmark.md, rubric.md, and tessl-best-practices.md (the 'Tessl-Aligned' checklist header is a natural anchor for the last) — so every file in references/ is discoverable from SKILL.md.

DimensionReasoningScore

Conciseness

The body is lean and imperative with no explanations of concepts Claude already knows — every section is rules, thresholds, or workflow steps. Minor token spend is questionable: the 'Evidence Tiers & Guardrails' section leans on unexplained project jargon ('per readiness.ts', 'Bind scorer, evals, and generated metadata digests to candidate checkout') that could be trimmed or moved to a reference, keeping it below the 'every token earns its place' anchor.

4 / 5

Actionability

Mostly actionable: a copy-paste command ('cp -r <skill-dir> <workspace>/skill-snapshot/'), numeric gates ('target ≥90% accuracy', '≤100 lines', '>10 lines'), and concrete procedures (spawn parallel subagents with/without skill). Minor gaps remain — step 2 is broken text ('what it , when it trigger, expected output format?') and 'rerun into next iteration dir' references an undefined convention — so it does not reach fully-executable coverage of common cases.

4 / 5

Workflow Clarity

Clear ordered sequence with explicit validation checkpoints (Test, Evaluate against 'pass rate, tokens, time', '≥90%' trigger accuracy), a feedback loop ('Iterate — rewrite based on feedback, rerun... repeat'), and a Quality Checklist. It falls short of the top anchor because the new-skill (steps 1–8) and existing-skill (steps 9–15) tracks are merged into a single numbered list with an awkwardly indented '**Existing skill:**' marker, making the two sequences easy to misread.

4 / 5

Progressive Disclosure

Good structure: an 84-line body with no oversized code blocks, in-text links to real files (TEMPLATE.md, eval-workflow.md, web-search-research.md), and a References section where every entry carries a 'load when' condition; all linked files exist and are one level deep. The gap versus the top anchor is that 3 of the 11 bundle files (benchmark.md, rubric.md, tessl-best-practices.md) are not referenced anywhere in SKILL.md, and 'Quality Checklist (Tessl-Aligned)' names Tessl without linking the tessl-best-practices.md mapping.

4 / 5

Total

16

/

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 with explicit what/when structure, third-person voice, and a distinct niche with low conflict risk. Its main weakness is reliance on internal scoring vocabulary (Activation/Implementation, Token ROI, high-density) instead of plainer capability language, and it omits a few natural trigger synonyms like 'create skill'.

DimensionReasoningScore

Specificity

Lists several specific actions — 'Standardizes the creation and evaluation', 'improving trigger accuracy', 'refactoring skills to reduce redundancy and maximize token ROI' — but relies on internal jargon ('high Activation (specificity/completeness) and Implementation (conciseness/actionability) scores', 'high-density') rather than fully concrete operations. Matches the 'several specific actions; minor gaps' anchor, not the comprehensive anchor whose actions are tangible like 'fill forms, merge documents'.

4 / 5

Completeness

Explicitly answers both: what ('Standardizes the creation and evaluation of high-density Agent Skills... Ensures skills achieve high Activation... and Implementation... scores') and when ('Use when: writing or auditing SKILL.md, improving trigger accuracy, or refactoring skills to reduce redundancy'). The when-clause is fully explicit with concrete trigger phrases, matching the top anchor rather than the 'could be more explicit' anchor below it.

5 / 5

Trigger Term Quality

'writing or auditing SKILL.md', 'improving trigger accuracy', and 'refactoring skills' are phrases a user would naturally say, giving good keyword coverage. A few natural terms are missing — 'create skill', 'skill template', 'optimize description' — so it falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — Agent Skills (Claude, Cursor, Windsurf) authoring/auditing — with surgical triggers like 'SKILL.md', 'trigger accuracy', and 'token ROI' that other skills would not claim. 'refactoring skills' is contextualized ('to reduce redundancy and maximize token ROI'), so overlap with code-refactoring skills is minimal.

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

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