wiki

Persistent markdown project wiki stored under repository omx_wiki with keyword search and lifecycle capture

Quality

66%

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/wiki/SKILL.md

Quality

Content

80%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 highly actionable and well-structured with copy-paste commands and tight, padding-free sections. Its main weakness is the lack of validation around the destructive delete operation and the absence of an explicit multi-step workflow with checkpoints.

Suggestions

Add a validation step before 'wiki_delete' (e.g., run 'wiki_read' to confirm the page exists, or require the page title to be echoed back) so destructive operations are guarded.

Group the operations into a light workflow with explicit sequencing for the capture-then-query lifecycle rather than presenting them as a flat command catalog.

Trim the intro line 'Persistent, self-maintained markdown knowledge base...' since it duplicates the frontmatter description.

Dimension	Reasoning	Score
Conciseness	The body is lean: command examples, category/storage lists, and brief constraints with no conceptual padding; only a minor restatement of the description in the intro could be trimmed.	4 / 5
Actionability	Every operation ships a copy-paste-ready 'omx wiki' command with a concrete JSON '--input' payload covering the common cases (ingest, query, lint, add, list, read, delete, refresh).	5 / 5
Workflow Clarity	Operations are listed as independent commands rather than a sequenced workflow, and the destructive 'wiki_delete' has no validation checkpoint, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Under 50 lines with no bundle files and no need for external references, organized into clear sections (Operations, Categories, Storage, Cross-References, Auto-Capture, Hard Constraints).	5 / 5
	Total	17 / 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 clearly states what the skill is and where it lives, with a couple of concrete capabilities, but omits any explicit 'when to use' guidance and relies partly on jargon. It is moderately specific and fairly distinct, yet not comprehensive.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., when the user wants to record or look up project decisions, architecture notes, or session discoveries).

Replace or augment 'lifecycle capture' with plainer terms users would actually say (e.g., 'capture session discoveries', 'log decisions').

List a few more concrete capabilities (e.g., cross-link pages, tag/category filtering) to broaden the specificity beyond the two named actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('markdown project wiki') and two concrete actions ('keyword search', 'lifecycle capture'), but does not enumerate multiple specific capabilities comprehensively.	3 / 5
Completeness	Provides a clear 'what' but contains no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	'wiki' and 'keyword search' are natural terms, but 'lifecycle capture' is jargon and common variations/synonyms are absent.	3 / 5
Distinctiveness Conflict Risk	Targets a distinct niche (project wiki under omx_wiki) with minimal overlap risk, though explicit trigger phrases that would fully separate it from related skills are missing.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Yeachan-Heo/oh-my-codex
Path: plugins/oh-my-codex/skills/wiki/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.