- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add first-fluke/oh-my-agent --skill oma-docs -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add first-fluke/oh-my-agent --skill oma-docs -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add first-fluke/oh-my-agent --skill oma-docs -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add first-fluke/oh-my-agent --skill oma-docs -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/first-fluke/oh-my-agent/tree/HEAD/.agents/skills/oma-docsFrom the publisher
Keep documentation aligned with repository behavior and report verification limits.
Check references, update docs for a code diff, identify translation drift, or lint localized prose.
Repository documentation verification, diff-based synchronization, and translation maintenance.
oma docs migrate on explicit request (resources/commands.md); it is not a maintenance mode.Mode (verify, sync, i18n, or lint), target paths or diff range, and authorized edit scope. Use verify when no mode is specified.
Findings with paths and evidence, authorized patches when requested, and unresolved checks. CLI reports remain distinct from host-authored interpretation.
The oma docs CLI, Git for diff-based work, and repository docs. lychee is optional for URL verification. Read resources/commands.md for flags and output files of the selected mode.
verify: extract and resolve references, then summarize the report.sync: obtain candidates, read relevant docs and diffs, and apply only authorized corrections.i18n / lint: report drift or style issues; use oma-translation for authorized corrections.Report verified findings, edits made, and remaining gaps. A clean reference scan does not establish semantic correctness or complete translation quality.
resources/commands.md.oma docs verify --json, oma docs sync <range> --json, oma docs i18n --json, or oma docs lint --json as appropriate. For sync, use the requested range; otherwise staged changes, then HEAD~1..HEAD.docs.sync-patch-approval; bind instanceId and verification --instance to the doc path plus current patch revision (workflow Step 4 owns the command template). Existing authorization remains sufficient. Ask only about material missing decisions or new scope; continue independent work while waiting.Verification regenerates docs/generated/doc-refs.json; optional URL results go to docs/generated/url-drift.json. Sync's CLI emits candidate data; the host drafts and applies patches. i18n/lint commands report only. A workflow hook runs only when docs.auto_verify is enabled and is warn-only.
../_shared/core/execution-policy.md for authorization and completion..env*, private keys, credentials) in diff reports.oma-docs: skip, and configured exclusions. Missing gitignored runtime outputs are skipped, not broken references.resources/commands.md (selected operation only).../oma-translation/SKILL.md (localized correction).../_shared/core/execution-policy.md (when not already provided).Check documentation references, sync docs to code changes, and detect translation drift. Use for documentation maintenance in a repository.
---name: oma-docsdescription: Check documentation references, sync docs to code changes, and detect translation drift. Use for documentation…---# .agents/skills/oma-docs/SKILL.mdFAQ
Download .agents/skills/oma-docs/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/first-fluke/oh-my-agent.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.