CtrlK
BlogDocsLog inGet started
Tessl Logo

deepinit

Deep codebase initialization with hierarchical AGENTS.md documentation

51

Quality

40%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/deepinit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

17%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too terse and relies on technical jargon without explaining what concrete actions the skill performs or when it should be used. The term 'AGENTS.md' may be meaningful to those familiar with the convention but provides no context for skill selection. It lacks the explicit 'Use when...' clause critical for Claude to choose this skill appropriately.

Suggestions

Add a 'Use when...' clause with natural trigger terms like 'new project', 'codebase setup', 'generate documentation', 'onboard to codebase', or 'analyze project structure'.

Expand the capabilities section to list specific actions: e.g., 'Analyzes codebase structure, generates hierarchical AGENTS.md files, documents module relationships and conventions'.

Include user-friendly synonyms and variations: 'project documentation', 'codebase docs', 'agent configuration', 'repo initialization'.

DimensionReasoningScore

Specificity

Names the domain (codebase initialization) and mentions a specific artifact (hierarchical AGENTS.md documentation), but doesn't list concrete actions like 'analyze directory structure', 'generate documentation', or 'create agent configs'.

2 / 3

Completeness

Only partially addresses 'what' and completely lacks a 'when' clause. No explicit triggers or guidance on when Claude should select this skill.

1 / 3

Trigger Term Quality

Uses technical jargon ('hierarchical AGENTS.md') that users wouldn't naturally say. Missing common terms like 'setup', 'onboard', 'project structure', 'documentation generation', or 'codebase analysis'.

1 / 3

Distinctiveness Conflict Risk

'AGENTS.md' is somewhat distinctive, but 'codebase initialization' and 'documentation' are generic enough to potentially conflict with other documentation or setup skills.

2 / 3

Total

6

/

12

Passed

Implementation

62%

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

This skill provides a comprehensive framework for generating hierarchical AGENTS.md documentation with good workflow structure and validation steps. However, it suffers from verbosity (explaining concepts Claude knows), pseudocode instead of executable implementations, and could benefit from splitting detailed templates into separate reference files.

Suggestions

Replace the pseudocode Task() syntax with actual executable commands or clarify the specific tool/framework being used

Move the detailed AGENTS.md templates and example outputs to a separate TEMPLATES.md file, keeping only a minimal example in the main skill

Remove explanatory text about what AGENTS.md files are for - Claude understands documentation purposes

Add concrete file reading/writing code examples instead of describing the process abstractly

DimensionReasoningScore

Conciseness

The skill is moderately efficient but includes some unnecessary verbosity, such as explaining what AGENTS.md files are for (Claude would understand this) and providing overly detailed templates that could be more compact. The extensive example outputs add length without proportional value.

2 / 3

Actionability

Provides templates and structure but lacks fully executable code. The 'Task(subagent_type=...)' syntax appears to be pseudocode rather than real executable commands. Bash snippets are minimal and the workflow steps describe what to do conceptually rather than providing copy-paste ready implementations.

2 / 3

Workflow Clarity

Clear 5-step sequential workflow with explicit validation in Step 5. Includes a validation table with checks, verification methods, and corrective actions. The level-by-level generation approach with parent-first ordering shows good understanding of dependency sequencing.

3 / 3

Progressive Disclosure

Content is reasonably structured with clear sections, but everything is in one monolithic file. The extensive templates and examples could be split into separate reference files. No external file references are provided despite the content length warranting them.

2 / 3

Total

9

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
Yeachan-Heo/oh-my-claudecode
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.