Agent skill

oma-explainer

Turn a code change (diff, PR, branch, commit range) into a rich, self-contained interactive HTML explainer with Background / Intuition / Code / Quiz sections. Use for explain, walkthrough, code-change explanation, diff/PR/branch explainer requests — 설명서, 해설, コード解説, 代码讲解. Produces a single offline-capable HTML file with diagrams, callouts, and an accessible quiz.

first-flukegithub.com/first-flukeGitHub ↗
claude-codecodexcursorMIT
Install
npx skills add first-fluke/oh-my-agent --skill oma-explainer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 9 KB
Bundled scripts: none
Path: .agents/skills/oma-explainer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,204
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# oma-explainer — Interactive HTML Code-Change Explainer ## Scheduling ### Goal Generate an educational, self-contained interactive HTML document that explains a code change to a reader — deep skippable background for newcomers, core intuition with toy data, a comprehension- ordered code walkthrough, and a five-question quiz — saved under `.agents/results/explain/` and validated against a deterministic checklist. ### Intent signature - User invokes `/explain`, names this skill, or asks for a rich explanation/walkthrough of a diff, PR, branch, or commit range (설명서, 해설, コード解説, 代码讲解). - Another skill or workflow delegates "explain this change as a document" output. - Activation is slash/explicit/delegated only — this skill is intentionally excluded from keyword auto-detection ("explain" is everyday vocabulary; `convert` precedent). ### When to use - Explaining a PR, branch, commit range, or the current staged/unstaged change as a document - Onboarding a teammate onto a change they did not write - Producing a reviewable teaching artifact after a large or subtle change lands ### When NOT to use - Narrated explainer *video* → use `oma-video` (explainer mode); this skill produces HTML doc

What's inside
Steps it walks through
  1. Scheduling
  2. Goal
  3. Intent signature
  4. When to use
  5. When NOT to use
  6. Expected inputs
  7. Expected outputs
  8. Dependencies
  9. Control-flow features
  10. Structural Flow
  11. Entry
  12. Scenes
  13. Transitions
  14. Failure and recovery
Ships with 2 files
  • resources/document-structure.md
  • resources/html-contract.md
More from oh-my-agent
All skills →
About this skill
What does the oma-explainer skill do?

Turn a code change (diff, PR, branch, commit range) into a rich, self-contained interactive HTML explainer with Background / Intuition / Code / Quiz sections. Use for explain, walkthrough, code-change explanation, diff/PR/branch explainer requests — 설명서, 해설, コード解説, 代码讲解. Produces a single offline-capable HTML file with diagrams, callouts, and an accessible quiz.

How do I install it?

Run `npx skills add first-fluke/oh-my-agent --skill oma-explainer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From first-fluke/oh-my-agent, a repository with 1,204 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going