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.

65

Quality

82%

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

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 well-engineered meta-skill body: compact, imperative, self-consistent (it practices the density rules it preaches), with a clear two-track workflow, feedback loops, snapshot safety, and well-signaled one-level-deep references. The main defects are a garbled step ('what it , when it trigger'), a duplicated rule, and three orphaned reference files not indexed in the References section.

Suggestions

Fix the broken text in workflow step 2 ('Capture intent — what it , when it trigger, expected output format?') to read e.g. 'what it does, when it triggers, expected output format'.

De-duplicate the >10-line code-block rule, which appears both under 'Progressive Disclosure' in Content Quality and as 'No Long Code Blocks' in Anti-Patterns — state it once and cross-reference.

Add 'load when' entries for benchmark.md, rubric.md, and tessl-best-practices.md to the References section so all 11 bundle files are navigable from the body.

DimensionReasoningScore

Conciseness

The body is lean and imperative with no AI-splaining — e.g., 'No Redundant Knowledge: Do NOT explain concepts AI already knows... Focus strictly on project-specific rules' is enforced by the writing itself. It misses the 5 anchor due to minor trimmable redundancy: the >10-line code-block rule appears twice ('Progressive Disclosure: Move code blocks >10 lines to references/' and 'No Long Code Blocks: Blocks >10 lines must be extracted to references/'), and the Description Quality section partially repeats the workflow's description-related steps.

4 / 5

Actionability

Mostly executable guidance: concrete commands ('cp -r <skill-dir> <workspace>/skill-snapshot/'), specific thresholds ('target ≥80% accuracy', '≤100 lines'), and a defined test protocol ('spawn parallel subagents: one with-skill, one without-skill'). It sits at 4 rather than 5 because some steps are directives without inline specifics ('Evaluate — grade assertions, review benchmark' says what to grade but not how) and step 2 contains broken text ('Capture intent — what it , when it trigger, expected output format?') that impairs copy-ready precision.

4 / 5

Workflow Clarity

Clear two-path sequence (new skill steps 1–8, existing skill steps 9–15) with real feedback loops — Test → Evaluate → Iterate ('rewrite based on feedback, rerun into next iteration dir'), a pre-edit snapshot guardrail, and an explicit Quality Checklist. It does not reach 5 because checkpoints are named but not all explicit: gating criteria for pass/fail ('grade assertions, review benchmark (pass rate, tokens, time)') and the pressure-test step lack inline validation conditions, deferring them to the eval-workflow reference.

4 / 5

Progressive Disclosure

Scored against the actual bundle: the References section lists 8 real files with 'load when' load-condition hints (e.g., 'load when SKILL.md approaches 100 lines'), all one level deep, and in-text links (TEMPLATE.md, web-search-research.md, eval-workflow.md) all resolve to existing files. It falls short of 5 because 3 of the 11 bundle files (benchmark.md, rubric.md, tessl-best-practices.md) are not reachable from the body's navigation — benchmark.md is only mentioned inside eval-workflow.md — leaving discoverability gaps.

4 / 5

Total

16

/

20

Passed

Description

83%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, well under 100 words, with an explicit what+when structure and concrete, niche-specific trigger phrases. Its only weaknesses are slightly meta framing in the 'what' clause ('Standardizes', 'Ensures... scores') and a few missing natural keyword variants, which keep specificity and trigger coverage at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists several specific actions — 'creation and evaluation of high-density Agent Skills', 'writing or auditing SKILL.md', 'improving trigger accuracy', 'refactoring skills to reduce redundancy' — matching the 'several specific actions; minor gaps' anchor. It falls short of the 5 anchor because 'Standardizes' and 'Ensures skills achieve high Activation and Implementation scores' are process-level framing rather than fully concrete capabilities like the anchor-5 example's action list.

4 / 5

Completeness

Explicitly answers both questions: what — 'Standardizes the creation and evaluation of high-density Agent Skills (Claude, Cursor, Windsurf)' with named quality dimensions; when — 'Use when: writing or auditing SKILL.md, improving trigger accuracy, or refactoring skills to reduce redundancy and maximize token ROI' gives three concrete trigger conditions. It clearly matches the 5 anchor ('clearly and explicitly answers both what AND when with concrete trigger phrases'), not the 4 anchor whose 'when' is weaker or more generic.

5 / 5

Trigger Term Quality

Good natural-term coverage: 'writing or auditing SKILL.md', 'improving trigger accuracy', 'refactoring skills' are phrases a user would plausibly say, plus the distinct artifact name 'SKILL.md'. A few natural variants are missing (e.g., 'skill review', 'evals', 'skill template', 'Cursor rules'), so it sits at the 4 anchor ('good keyword coverage; a few natural terms missing') rather than 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

The skill-authoring niche is clear with distinct triggers tied to the concrete artifact 'SKILL.md', so it is above the 3 anchor ('could still overlap with similar skills'). It does not fully reach 5 because phrases like 'refactoring skills to reduce redundancy and maximize token ROI' could overlap with general code-refactoring or documentation skills, leaving minor conflict risk with closely related skills.

4 / 5

Total

17

/

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.