CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ai-md

Convert human-written CLAUDE.md into AI-native structured-label format. Battle-tested across 4 models. Same rules, fewer tokens, higher compliance.

Quality

62%

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 ./skills/ai-md/SKILL.md

The canonical home for this skill is ai-md in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

56%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 core conversion methodology is genuinely actionable — a concrete six-phase process, a standard label vocabulary, and a validation protocol with a safety net. However, the skill buries it under verbose theory and battle-test narrative, and keeps everything in one monolithic file instead of splitting reference material out.

Suggestions

Cut the marketing/backstory prose (three mechanism theory sections, "Real-World Results" table, testimonials, "The uncomfortable truth" closing) — the skill's own "What Not Why" principle says to delete exactly this material, saving substantial tokens.

Split reference material into bundle files: references/labels.md (the 12-label vocabulary), references/exam-protocol.md (the 8-question template and scoring rubric), and keep SKILL.md as the concise conversion process.

Operationalize the Phase 6 validation step with an executable script or concrete command sequence for running and scoring the multi-model exam, since it is marked "non-negotiable" yet currently has no runnable form.

DimensionReasoningScore

Conciseness

The ~510-line body carries whole sections of marketing prose and backstory ("The paradox we proved", "The uncomfortable truth", "Real-World Results", three attention-mechanism theory sections, and anecdotal testimonials), which both pads tokens and explains LLM-processing concepts Claude already knows — ironically violating the skill's own "What Not Why" principle.

2 / 5

Actionability

Mostly executable guidance: a 12-label vocabulary table, concrete per-phase decomposition examples, a copy-paste bash measurement snippet, an 8-question exam template, and a complete XML output template. It falls short of 5 because key steps are unautomated — "Run multi-model test (minimum 2 models, 8 questions)" has no script or command to execute.

4 / 5

Workflow Clarity

The six conversion phases are clearly sequenced, and Stage 2 includes a backup step, explicit validation (multi-model testing with a revert rule: "If ANY model's score drops after conversion → revert that specific change"), and a restore command. It falls short of 5 because the operational workflow is scattered — the two-stage workflow only appears after ~390 lines of theory, and pass/fail scoring criteria are not operationalized.

4 / 5

Progressive Disclosure

The body is well-sectioned with headers and tables, but it is a monolithic ~18KB file with no bundle files: content that clearly belongs in separate references (the label vocabulary, the 8-question exam template, the real-world results narrative) is inlined, matching the anchor for some structure but content that should be separate is inline.

3 / 5

Total

13

/

20

Passed

Description

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

The description communicates a clear, distinctive capability but reads more like a product tagline than a trigger description. It answers "what" well yet entirely lacks a "when to use" clause and natural user trigger phrases.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user complains their CLAUDE.md or system prompt is too long, their AI ignores their rules, or they want to optimize token usage or rule compliance."

Include natural trigger synonyms users would actually say: "AI ignores my rules", "system prompt optimization", "reduce CLAUDE.md tokens", "migrate rules between Claude/Codex/Gemini/Grok".

Replace the benefit claims ("Battle-tested across 4 models") with one more concrete action verb describing what the skill does (e.g., "converts, validates across multiple models, and reports before/after compliance scores").

DimensionReasoningScore

Specificity

"Convert human-written CLAUDE.md into AI-native structured-label format" names the domain and one concrete action, but the remaining sentences ("Battle-tested across 4 models", "Same rules, fewer tokens, higher compliance") are benefit claims rather than actions, so coverage is not comprehensive.

3 / 5

Completeness

The "what" is clear (convert CLAUDE.md into a structured-label format), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Relevant keywords like "CLAUDE.md", "fewer tokens", and "compliance" are present, but natural user phrasings such as "AI ignores my rules", "system prompt too long", or "reduce context usage" are missing, matching the anchor for some relevant keywords without common variations.

3 / 5

Distinctiveness Conflict Risk

The CLAUDE.md-conversion niche is specific and clearly distinguishable, with only minor overlap risk against closely related CLAUDE.md-authoring skills (e.g., a user asking to "write or update my CLAUDE.md").

4 / 5

Total

13

/

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

skill_md_line_count

SKILL.md is long (519 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/ai-md/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.