CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-md

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

33

Quality

30%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-awesome-skills-claude/skills/ai-md/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

27%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads more like a research paper or blog post advocating for the AI.MD methodology than a concise, actionable skill file. While it contains genuinely useful content — the label vocabulary, the template, the conversion phases, and the anti-patterns table — these are buried in extensive theoretical explanations, persuasive rhetoric, and real-world case studies that dramatically inflate token cost. The skill would benefit enormously from being split into a lean SKILL.md overview with references to supporting detail files.

Suggestions

Cut the 'Why It Works' section entirely (Mechanisms 1-3) — Claude doesn't need to understand attention theory to follow conversion instructions. Move to a separate THEORY.md if users want it.

Extract the 'Special Techniques' and 'Real-World Results' sections into separate reference files (TECHNIQUES.md, RESULTS.md) and link from the main skill with one-line summaries.

Remove all persuasive/rhetorical content ('The uncomfortable truth', 'The paradox we proved', 'This is not optional') — these are human-facing arguments, not AI instructions.

Consolidate the core skill into: (1) the label vocabulary table, (2) the 6-phase process as a concise checklist, (3) the template, and (4) the two-stage workflow with backup — targeting under 100 lines total.

DimensionReasoningScore

Conciseness

Extremely verbose at ~400+ lines. Extensively explains HOW and WHY LLMs process instructions (attention splitting, semantic anchoring) — concepts that are explanatory background, not actionable instructions. The 'Why It Works' section alone is pure theory that Claude doesn't need. Massive amounts of commentary, metaphors ('hash table lookup instead of full-text search'), and persuasive rhetoric ('The uncomfortable truth') waste tokens.

1 / 3

Actionability

The conversion phases (1-6) provide a structured process with concrete examples of input→output transformations, and the template is copy-paste ready. However, much of the content is conceptual explanation rather than executable guidance — the bash snippet is useful but the multi-model testing protocol is aspirational rather than directly executable by Claude. The label vocabulary table and template are genuinely actionable.

2 / 3

Workflow Clarity

The six-phase conversion process (Understand→Decompose→Label→Structure→Resolve→Test) is clearly sequenced, and the two-stage workflow (Preview→Distill) includes a backup step. However, validation checkpoints are weak — Phase 6 testing requires '2+ different LLM models' which Claude cannot orchestrate itself, and there's no feedback loop for what to do if the conversion produces worse results beyond 'revert that specific change.'

2 / 3

Progressive Disclosure

No bundle files are provided, yet this is a monolithic ~400-line document with no references to external files. The 'Why It Works' theory section, the detailed technique explanations, the anti-patterns table, and the real-world results could all be split into separate reference files. Everything is inline in one massive wall of content with no progressive disclosure structure.

1 / 3

Total

6

/

12

Passed

Description

32%Scale 1-3

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 identifies a specific artifact (CLAUDE.md) and a transformation action but relies heavily on marketing language ('battle-tested', 'higher compliance') instead of concrete capability details. It completely lacks a 'Use when...' clause, making it difficult for Claude to know when to select this skill. The description would benefit from replacing promotional claims with specific actions and explicit trigger conditions.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to optimize, compress, or reformat their CLAUDE.md file into a token-efficient structured format.'

Replace marketing fluff ('battle-tested across 4 models', 'higher compliance') with concrete actions like 'Parses markdown sections, converts prose rules into labeled directives, reduces token count while preserving instruction semantics.'

Include natural trigger term variations users might say, such as 'optimize CLAUDE.md', 'compress system instructions', 'reformat project rules', or 'reduce token usage in CLAUDE.md'.

DimensionReasoningScore

Specificity

It names the domain (CLAUDE.md conversion) and one action (convert to structured-label format), but doesn't list multiple concrete actions. The phrases 'battle-tested across 4 models' and 'fewer tokens, higher compliance' are marketing fluff rather than specific capabilities.

2 / 3

Completeness

It partially answers 'what' (convert CLAUDE.md to structured-label format) but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also not very clear, so this scores a 1.

1 / 3

Trigger Term Quality

Includes 'CLAUDE.md' which is a relevant trigger term, and 'structured-label format' provides some specificity. However, it misses natural variations users might say like 'optimize CLAUDE.md', 'compress instructions', 'reformat system prompt', or 'AI-readable format'.

2 / 3

Distinctiveness Conflict Risk

The mention of 'CLAUDE.md' and 'structured-label format' provides some distinctiveness, but 'convert' is generic and could overlap with other formatting or documentation transformation skills. The niche is somewhat clear but not sharply defined.

2 / 3

Total

7

/

12

Passed

Validation

81%

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

Validation — 9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

frontmatter_unknown_keys

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

Warning

Total

9

/

11

Passed

Repository
popey/claude-code-skills
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.