CtrlK
BlogDocsLog inGet started
Tessl Logo

init-deep

(builtin) Initialize hierarchical AGENTS.md knowledge base

60

Quality

70%

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 ./plugins/omo/skills/init-deep/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 content is a tight, highly actionable orchestration playbook with concrete code, a scoring matrix, and a clear phased workflow. Its only weak spot is that the review phase reads as cleanup rather than an explicit validate→fix→retry loop on generated output.

DimensionReasoningScore

Conciseness

The body is largely telegraphic and assumes Claude's competence ("Telegraphic or die", terse tables, no concept explanations), with only minor over-explanation such as the repeated "this section wins" disclaimers, fitting score 4 rather than the fully lean score 5.

4 / 5

Actionability

It provides copy-paste-ready bash one-liners, a concrete scoring matrix with thresholds, decision rules, a TodoWrite block, and a full AGENTS.md template, covering the common cases as required for score 5.

5 / 5

Workflow Clarity

A clear four-phase sequence with explicit TodoWrite transitions and an existence-check file-writing guard exists, but Phase 4 review is described as cleanup rather than an explicit validate-then-retry feedback loop, leaving a minor validation gap at score 4 rather than 5.

4 / 5

Progressive Disclosure

The single self-contained SKILL.md is well-organized with clear headers, tables, and sections and needs no external references; per the simple-skill note this well-structured single file earns score 5.

5 / 5

Total

18

/

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 is specific and niche-scoped but terse: it states what the skill does without any "when to use it" trigger guidance. Adding a Use-when clause and a couple of natural synonyms would raise completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when bootstrapping or regenerating an AGENTS.md knowledge base for a repo, or when the user asks to document project structure."

Add natural synonyms ("project documentation", "repo knowledge base") so the description matches phrasings users actually say.

Optionally enumerate 1-2 concrete actions (e.g. "score directories by complexity and generate root + subdirectory AGENTS.md files") to lift specificity toward 4-5.

DimensionReasoningScore

Specificity

"Initialize hierarchical AGENTS.md knowledge base" names the domain and one concrete action but does not list multiple specific actions, matching the score-3 anchor and falling below the comprehensive multi-action score-4 anchor.

3 / 5

Completeness

It gives a clear "what" (initialize a hierarchical AGENTS.md knowledge base) but no "Use when..." trigger clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

"AGENTS.md" is a concrete natural term, but the description lacks synonyms or common variations ("docs", "documentation", "knowledge base"), matching score 3 rather than the broader coverage at score 4.

3 / 5

Distinctiveness Conflict Risk

The niche (hierarchical AGENTS.md generation) is mostly distinct with only minor overlap risk against general documentation skills, matching score 4 rather than the fully-triggered score-5 anchor.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
code-yeongyu/lazycodex
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.