Agent skill

Oma Docs

by first-fluke in first-fluke/oh-my-agent

Check documentation references, sync docs to code changes, and detect translation drift.

MITAuto-check: notesWriting & Content

Install Oma Docs

skills CLI
$ npx skills add first-fluke/oh-my-agent --skill oma-docs -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install first-fluke/oh-my-agent oma-docs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/oma-docs .claude/skills/oma-docs && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
oma-docs
GitHub stars
1.3k
Token cost
~1.3k tokens
SKILL.md length
653 words
Files
2
Skills in repo
57
Repo updated
First seen
Licence
MIT

At a glance

Check documentation references, sync docs to code changes, and detect translation drift.

  • Works in 5 steps: Select mode, paths/diff, and… → Run oma docs verify --json, oma docs… → Inspect the structured results. Verify… → …
  • Documentation maintenance in a repository
  • SKILL.md covers Scheduling, Structural Flow, Logical Operations and References
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Oma Docs is an agent skill from first-fluke/oh-my-agent. Check documentation references, sync docs to code changes, and detect translation drift. Use for documentation maintenance in a repository.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `resources/commands.md`).

It sits in Writing & Content, covering Translation. The repository describes itself as: Mechanical verification for AI coding agents — skills pack or full harness (stop-hook gates, artifact checks, independent judges). The licence is MIT.

When your agent uses it

  • Documentation maintenance in a repository
  • Tasks that involve Translation

Example prompts

  • “/oma-docs”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Select mode, paths/diff, and authorization from the request. Read only the matching section of resources/commands.md.
  2. Run oma docs verify --json, oma docs sync --json, oma docs i18n --json, or oma docs lint --json as appropriate. For sync, use the…
  3. Inspect the structured results. Verify each proposed correction against current code and document context. Exclude secret-bearing files…
  4. Apply corrections already authorized by the user or assigned task. In an active OMA docs-sync workflow, first record each patch's actual…
  5. Re-run affected checks after edits and record remaining failures. Regenerate the reference index once after a patch batch when needed.

What it can do on your machine

Read from SKILL.md and the folder at commit f65bbc0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Oma Docs loads about 1.3k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 653 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~37
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:69
    - Do not expose secret-bearing files (`.env*`, private keys, credentials) in diff reports.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from first-fluke/oh-my-agent at commit f65bbc0, republished under its MIT licence (© first-fluke). 653 words, ~1,312 tokens.

Download SKILL.mdSave it as .claude/skills/oma-docs/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
oma-docs
description
Check documentation references, sync docs to code changes, and detect translation drift. Use for documentation maintenance in a repository.

Documentation Maintenance

Scheduling

Goal

Keep documentation aligned with repository behavior and report verification limits.

Intent signature

Check references, update docs for a code diff, identify translation drift, or lint localized prose.

When to use

Repository documentation verification, diff-based synchronization, and translation maintenance.

When NOT to use
  • General source research -> oma-search.
  • Application implementation -> the owning specialist.
  • Translating known text -> oma-translation.
Expected inputs

Mode (verify, sync, i18n, or lint), target paths or diff range, and authorized edit scope. Use verify when no mode is specified.

Expected outputs

Findings with paths and evidence, authorized patches when requested, and unresolved checks. CLI reports remain distinct from host-authored interpretation.

Dependencies

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.

Structural Flow

Transitions
  • 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.
  • Review-only requests produce proposals. Existing scoped edit requests authorize applying those corrections without another per-file approval.
Failure and recovery
FailureRecovery
Missing CLIState up front that the automated check is unavailable, then inspect manually anyway: list the target markdown files, extract [text](path), ![alt](path), and href/src targets, resolve each relative to its containing file, and report which resolved paths are missing. Skip http(s) URLs and note them as unverified scope. Label the result "manual inspection — oma docs verify did not run"; never present it as CLI output and never make installing the CLI a prerequisite
Missing lychee or incomplete URL scanReport core results and the unverified URL scope
One document cannot be parsedRecord the skipped file and continue other documents
Patch does not applyRe-read the affected current content and make the equivalent authorized correction
Index write failsReport the failure; do not claim the index or check is complete
Exit

Report verified findings, edits made, and remaining gaps. A clean reference scan does not establish semantic correctness or complete translation quality.

Logical Operations

Show full SKILL.md (307 more words)Show less
Canonical command path
  1. Select mode, paths/diff, and authorization from the request. Read only the matching section of resources/commands.md.
  2. Run 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.
  3. Inspect the structured results. Verify each proposed correction against current code and document context. Exclude secret-bearing files and values from patches and reports.
  4. Apply corrections already authorized by the user or assigned task. In an active OMA docs-sync workflow, first record each patch's actual apply/skip action, rationale, and evidence with 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.
  5. Re-run affected checks after edits and record remaining failures. Regenerate the reference index once after a patch batch when needed.
Resource scope and effects

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.

Guardrails
  • Follow ../_shared/core/execution-policy.md for authorization and completion.
  • Keep review-only requests read-only and changes within the assigned diff or acceptance criteria.
  • Do not expose secret-bearing files (.env*, private keys, credentials) in diff reports.
  • The CLI produces structured data; the host performs natural-language synthesis. Do not invent CLI findings or call a vendor LLM API from the docs CLI.
  • Honor ignore blocks, oma-docs: skip, and configured exclusions. Missing gitignored runtime outputs are skipped, not broken references.
  • Preserve language, terminology, and placeholders when applying localized corrections.

References

  • Mode commands, flags, and outputs: resources/commands.md (selected operation only).
  • Translation: ../oma-translation/SKILL.md (localized correction).
  • Authorization: ../_shared/core/execution-policy.md (when not already provided).

© first-fluke, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/oma-docs of first-fluke/oh-my-agent.

  • SKILL.md
  • resources/commands.md

Open the folder on GitHubat commit f65bbc0

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in first-fluke/oh-my-agent, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Oma Docs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Oma Docs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Oma Docs this skillfirst-fluke/oh-my-agent1.3k—~1.3kAutomated safety check: NotesMIT
Translation Diff ExportDevolutions/UniGetUI26k—~1.1kAutomated safety check: PassMIT
Sync Translationssymfony/symfony31k—~1.9kAutomated safety check: PassMIT
Translation Diff ImportDevolutions/UniGetUI26k—~750Automated safety check: PassMIT
Translation Diff TranslateDevolutions/UniGetUI26k—~934Automated safety check: PassMIT
Generate Translationspayloadcms/payload45k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Translation Diff Export

    Devolutions/UniGetUI

    Compares UniGetUI JSON locale files against English, identifies untranslated or source-changed keys, and generates patch, reference, and handoff files for a target language.

    26k GitHub stars~1.1k tokensUpdated today
    Writing & ContentAuto-check passed
  • Sync Translations

    symfony/symfony

    Synchronize translation catalogs across maintained Symfony branches: find messages that newer branches added to the English catalogs but that are still missing from the oldest maintained branch…

    31k GitHub stars~1.9k tokensUpdated today
    Writing & ContentAuto-check passed
  • Translation Diff Import

    Devolutions/UniGetUI

    Merges translated key-value pairs from a UniGetUI JSON localization patch back into the full language file and validates the merged result.

    26k GitHub stars~750 tokensUpdated today
    Writing & ContentAuto-check passed
  • Translation Diff Translate

    Devolutions/UniGetUI

    Translates a sparse UniGetUI JSON language patch, writes completed entries into the working copy, preserves placeholders and terminology, and prepares the patch for merge-back.

    26k GitHub stars~934 tokensUpdated today
    Writing & ContentAuto-check passed
  • Generate Translations

    payloadcms/payload

    A skill your agent uses when new translation keys are added to packages to generate new translations strings

    45k GitHub stars~1.1k tokensUpdated today
    Writing & ContentAuto-check passed
  • Drives long-form fiction, scripts, storyboards, interactive films and long-document translation through InkOS, with every change made by a typed action.

    10k GitHub starsUsed in 1 repo~1.1k tokens
    Writing & ContentAuto-check passed

More from first-fluke/oh-my-agent

All 57 skills in this repo
  • OMA Multi-Agent Orchestration

    first-fluke/oh-my-agent

    Decomposes a complex feature into tasks, dispatches parallel specialist agents with durable state, and supervises verification, QA review and retries.

    1.3k GitHub stars~4.1k tokensUpdated today
    Auto-check passed
  • Oma Video

    first-fluke/oh-my-agent

    Create short, explainer, or recorded-demo videos through the OMA video CLI.

    1.3k GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed
  • OMA Multi-Agent Orchestrator

    first-fluke/oh-my-agent

    Splits a complex feature into prioritized tasks, spawns specialist CLI subagents in parallel, tracks them through shared memory and verifies each result.

    1.3k GitHub stars~3.1k tokensUpdated today
    Auto-check passed
  • Architecture Decisions and ADRs

    first-fluke/oh-my-agent

    Evaluates system boundaries and tradeoffs and writes architecture recommendations, option comparisons or ADRs, with a Mermaid diagram when structure changes.

    1.3k GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • OMA Backend Agent

    first-fluke/oh-my-agent

    Backend specialist for APIs, database work, authentication and migrations that follows clean architecture with router, service and repository layers.

    1.3k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • oma Bootstrap

    first-fluke/oh-my-agent

    Installs or checks the oma CLI and its runtimes (bun, uv, serena) in a fresh workspace so that oma-* skills can run their commands.

    1.3k GitHub stars~719 tokensUpdated today
    Auto-check passed

Questions about Oma Docs

What does Oma Docs do?

Check documentation references, sync docs to code changes, and detect translation drift. Oma Docs is an agent skill from first-fluke/oh-my-agent. Check documentation references, sync docs to code changes, and detect translation drift.

When should I use Oma Docs?

Oma Docs fits situations like: documentation maintenance in a repository; tasks that involve Translation.

How do I install Oma Docs in Claude Code?

Run `npx skills add first-fluke/oh-my-agent --skill oma-docs -a claude-code`. Or copy the skill folder (skills/oma-docs in first-fluke/oh-my-agent) into .claude/skills/oma-docs in your project. Claude Code loads it when a task matches its description.

How do I install Oma Docs in Codex?

Run `npx skills add first-fluke/oh-my-agent --skill oma-docs -a codex`. Or copy the skill folder (skills/oma-docs in first-fluke/oh-my-agent) into .agents/skills/oma-docs in your project. Codex loads it when a task matches its description.

Can I use Oma Docs in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add first-fluke/oh-my-agent --skill oma-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/oma-docs, .gemini/skills/oma-docs, .github/skills/oma-docs and .opencode/skills/oma-docs in your project.

What does Oma Docs need to run?

SKILL.md names no scripts, command-line tools or credentials: Oma Docs is instructions for the agent only.

Does Oma Docs access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Oma Docs safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Oma Docs use?

Oma Docs is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Oma Docs use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Oma Docs?

Skills that share tags, products or a category with Oma Docs: Translation Diff Export (Devolutions/UniGetUI, 26k stars), Sync Translations (symfony/symfony, 31k stars), Translation Diff Import (Devolutions/UniGetUI, 26k stars) and Translation Diff Translate (Devolutions/UniGetUI, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Oma Docs?

first-fluke (a GitHub organization) maintains it in first-fluke/oh-my-agent, which has 1,338 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on October 8, 2026.

Source: first-fluke/oh-my-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.