skill

Manage local skills - list, add, remove, search, edit, setup wizard

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/oh-my-codex/skills/skill/SKILL.md

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 body is thorough and actionable with clear per-command workflows and validation for destructive ops, but it is markedly verbose and monolithic: heavy padding and large inlined templates/scripts that should be split into reference files. It would benefit substantially from trimming and progressive disclosure.

Suggestions

Move the four skill templates and the setup scan bash script into separate reference files under references/ and link to them from the body.

Remove general-knowledge padding ("Benefits of Local Skills", "Skill Quality Guidelines", "Tips for Users", "Future Enhancements", and the duplicate "Related Skills" block) that Claude already knows.

Trim the full example transcripts for each subcommand to one concise representative example to reduce token cost.

Dimension	Reasoning	Score
Conciseness	The ~830-line body has several padded sections Claude does not need ("Benefits of Local Skills", "Skill Quality Guidelines" with generic BAD/GOOD examples, "Tips for Users", "Future Enhancements", a duplicated "Related Skills" block, and four large inlined templates), plus full example transcripts for every subcommand.	2 / 5
Actionability	Guidance is concrete and largely executable: specific file paths (~/.codex/skills/), validation rules (lowercase/hyphens only), a real executable bash scan script, and copy-paste-ready skill templates, with only minor gaps in the interactive wizard flows which are described behaviorally.	4 / 5
Workflow Clarity	Each subcommand has clearly numbered steps, and destructive/batch operations (remove, sync) include explicit confirmation checkpoints and a dedicated Error Handling section, satisfying the destructive-operation validation requirement with only minor feedback-loop gaps.	4 / 5
Progressive Disclosure	Section headers are well organized, but the skill is a monolithic 830-line file with no bundle/reference files and large blocks that clearly belong in separate files (four templates, the scan bash script, full transcripts) inlined directly.	3 / 5
	Total	13 / 20 Passed

Description

58%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 clearly states what the skill does and enumerates concrete subcommands, but it entirely lacks a "when to use" trigger clause and relies on generic command verbs rather than natural user phrasings. It is functional but incomplete by this rubric's standards.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to manage, organize, create, or search local oh-my-codex skills."

Expand trigger terms with natural synonyms users actually say ("create/delete/find a skill") alongside the command verbs.

Optionally mention the other subcommands present in the body (sync, info, scan) so the description's coverage matches the skill.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("list, add, remove, search, edit, setup wizard") on a clearly named domain, but the actions are generic verb names rather than richly described operations, leaving minor coverage gaps (sync/info/scan from the body are omitted).	4 / 5
Completeness	The "what" is clear ("Manage local skills" plus enumerated commands) but there is no "Use when..." or equivalent trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Terms like "list, add, search, edit" are somewhat natural but are command verbs missing common user phrasings and synonyms ("create", "delete", "find"), so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	"Manage local skills" is a distinct meta-skill niche, but the generic verb triggers (list/add/search/edit) create minor overlap risk with other command-style skills.	4 / 5
	Total	14 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (837 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: Yeachan-Heo/oh-my-codex
Path: plugins/oh-my-codex/skills/skill/SKILL.md
Commit: e94437f

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.