CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

init-deep

Initializes a hierarchical AGENTS.md knowledge base for a project. Use when a repo needs its structure, commands, and conventions documented for agents.

Quality

73%

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

Quality

Content

63%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 highly actionable, well-sequenced orchestration skill with concrete commands, quantified decision rules, and safety checks around file overwrites. Its weaknesses are the padded, repetitive Codex compatibility preamble that inflates token cost and the total absence of progressive disclosure — everything, including harness-routing boilerplate and templates, is inlined in one long file.

Suggestions

Move the Codex Harness Tool Compatibility preamble to a references/ file (e.g., references/codex-tool-compat.md) and keep a two-line pointer plus the single 'this section wins' rule in SKILL.md; this would materially improve both conciseness and progressive_disclosure.

De-duplicate the repeated "If a code block below conflicts with this section, this section wins" statement (stated three times) into one rule near the top of the compatibility section.

Extract the root AGENTS.md template into assets/ (e.g., agents-md-template.md) and reference it from Phase 3, keeping only the quality gates and section summary inline.

DimensionReasoningScore

Conciseness

The core workflow is genuinely lean ("Telegraphic or die", tight tables, copy-paste bash), but the 20+ line Codex compatibility preamble is noticeably padded: "If a code block below conflicts with this section, this section wins" is repeated three times, and the multi_agent_v1/v2 paragraph is a dense unbroken wall reiterating fork_context rules. This lands on anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') — not 2, since the routing text carries real harness-specific information rather than explaining concepts Claude already knows, and not 4 because the repetition is clearly trimmable.

3 / 5

Actionability

Concrete, executable guidance dominates: copy-paste bash measurement commands (find/wc/awk), fully specified agent-spawn calls with prompts, a quantified scoring matrix with thresholds, decision rules, and a complete AGENTS.md template. It stops short of anchor 5 because a few pieces remain illustrative pseudocode (the Phase 3 'for loc in AGENTS_LOCATIONS' loop with ${loc.path} interpolation and the Phase 1 'for each background task ID' collection snippet), matching anchor 4's 'concrete code or commands with minor gaps'.

4 / 5

Workflow Clarity

The four phases (Discovery → Scoring → Generate → Review) are clearly sequenced with a real-time TodoWrite checklist, explicit per-phase status transitions, quality gates ("50-150 lines, no generic advice"), a Phase 4 validation pass, a safety rule for overwriting existing files, and fallback paths ("Only if LSP is unavailable: explore agents + ast-grep alone, and mark reference centrality unmeasured"). It is not 5 because validation is a single pass with no re-check/error-recovery loop after generation, and the destructive --create-new path ("Read all existing first → then delete all → regenerate") has only the read-first safeguard with no post-regeneration verification.

4 / 5

Progressive Disclosure

The body has clear section structure (per-phase headers, <critical> blocks), but the skill is a single ~290-line file with no references or bundle files: the Codex harness compatibility preamble (roughly a quarter of the file) and the root AGENTS.md template are inlined content that could live in a separate reference file. This fits anchor 3 ('some structure but... content that should be separate is inline'); it is above anchor 2 because section headers and navigation are good, and below anchor 4 because nothing is split out.

3 / 5

Total

14

/

20

Passed

Description

70%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 solid third-person description with a clear 'what' and an explicit 'Use when...' clause naming the AGENTS.md artifact. Its main limitation is that it commits to only one action ('Initializes') and its trigger set, while good, omits natural synonyms users might say (CLAUDE.md, project docs, onboarding).

Suggestions

Enumerate the concrete operations in the description, e.g., 'Generates root and subdirectory AGENTS.md files, scores directory complexity to decide where files are needed, and updates existing files' — this would lift specificity toward 4-5.

Broaden trigger coverage with natural synonyms users actually say, such as 'AGENTS.md, CLAUDE.md, project documentation, onboarding docs, or documenting the codebase for agents'.

DimensionReasoningScore

Specificity

"Initializes a hierarchical AGENTS.md knowledge base" names the domain and one concrete action, with "structure, commands, and conventions" enumerating the deliverable's contents, but no second action (e.g., updates existing files, scores directory complexity) is stated. This matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive'); it is not 4 because several specific actions are not listed, and not 2 because the action and its scope are concrete rather than generic.

3 / 5

Completeness

Both parts are present: the 'what' ("Initializes a hierarchical AGENTS.md knowledge base for a project") is clear, and an explicit 'when' clause exists ("Use when a repo needs its structure, commands, and conventions documented for agents"). The 'when' is a needs-assessment condition rather than concrete user-utterance triggers (contrast anchor 5's 'when the user mentions PDFs, forms...'), matching anchor 4: both present, 'when' could be more explicit.

4 / 5

Trigger Term Quality

"Use when a repo needs its structure, commands, and conventions documented for agents" plus the artifact name "AGENTS.md" gives good natural keyword coverage (repo, structure, commands, conventions, documented, agents). It falls short of anchor 5's comprehensive synonym coverage (missing "CLAUDE.md", "project docs", "onboarding", "codebase documentation") but exceeds anchor 3's 'some relevant keywords' by naming the exact artifact users would mention.

4 / 5

Distinctiveness Conflict Risk

"hierarchical AGENTS.md knowledge base" carves a clear niche around a specific artifact, so it is mostly distinct with only minor overlap risk against closely related skills (a generic repo-init/CLAUDE.md documentation skill could also trigger on "repo needs... documented for agents"). It lacks the fully distinct trigger set of anchor 5 but is far more specific than anchors 2-3.

4 / 5

Total

15

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

code-yeongyu/lazycodex

Path

plugins/omo/skills/init-deep/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.