wiki

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

Quality

72%

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

87%

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

The body is concise, fully actionable, and well-organized for a simple skill, but destructive operations (delete, refresh) lack validation/confirmation checkpoints and lint is not embedded as a pre- or post-step, which caps workflow clarity at 2.

Suggestions

Add a validation checkpoint around destructive ops, e.g. run 'omx wiki wiki_read' to confirm the target page before 'wiki_delete', and document confirming the page is safe to remove.

Wire wiki_lint into a feedback loop: lint before ingest/add and re-lint after bulk refresh, with explicit 'fix and re-run' guidance on failure.

Note that wiki_refresh is a batch operation; state what it rewrites and whether a backup or dry-run is available to make the workflow safe-by-default.

Dimension	Reasoning	Score
Conciseness	The body is lean and operational with no concept explanations or padding (e.g., the omx_wiki/*.md storage lines, the one-line Hard Constraints), matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	Every operation ships a copy-paste-ready command with a real argument payload, e.g. 'omx wiki wiki_ingest --input '{"title":...}' --json', matching the fully executable, specific-examples anchor.	3 / 3
Workflow Clarity	Operations are clearly listed and runnable, but destructive/batch operations like 'wiki_delete' and 'wiki_refresh' have no validation or confirmation checkpoints, and wiki_lint is not wired into a validate-then-proceed feedback loop, so workflow clarity is capped at 2 per the rubric guidelines.	2 / 3
Progressive Disclosure	The skill is under 50 lines with no external bundle files and no need for them, yet is organized into clear sections (Operations, Categories, Storage, Cross-References, Auto-Capture, Hard Constraints), meeting the rubric's allowance for simple skills to score 3 on well-organized sections alone.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 conveys a clear, distinct niche and concrete capabilities but is written as noun phrases without an explicit 'Use when...' trigger clause, capping completeness and specificity. Adding a 'Use when...' clause and natural user-facing trigger terms would raise it to the top band.

Suggestions

Append an explicit 'Use when...' clause naming natural trigger situations (e.g., 'Use when capturing project knowledge, recalling past decisions, or searching notes by keyword or tag').

Reword capabilities as concrete actions in third person (e.g., 'Stores, searches, and retrieves markdown pages') to lift specificity toward the score-3 anchor.

Add common user-facing trigger variations to the description or triggers (e.g., 'notes', 'knowledge base', 'project memory') alongside 'wiki'.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete capabilities ('markdown project wiki stored under repository omx_wiki', 'keyword search and lifecycle capture'), but describes capabilities as noun phrases rather than listing multiple specific actions in verb form, so it falls short of the score-3 anchor.	2 / 3
Completeness	It clearly answers 'what' the skill does, but there is no explicit 'Use when...' clause or equivalent trigger guidance, which the rubric guidelines state caps completeness at 2.	2 / 3
Trigger Term Quality	The separate triggers array supplies natural wiki phrases ('wiki add', 'wiki query', 'wiki read'), but the description string itself leans technical ('lifecycle capture') and lacks common user-facing variations, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The description carves out a clear niche (a markdown project wiki under omx_wiki with keyword search) with distinct wiki triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 12 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: 435d4a9

Reviewed: 2 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.