プロトタイプ · プレビュー版:公式レジストリのすべてのサーバーを掲載し、30分ごとに同期しています。Google でログインするとレビューを書けます。プロトタイプ · 30分ごとに更新
PopNx MCPAIを使う人のためのMCPサーバー · やさしい言葉で解説

oh-my-claudecode Skill

リポジトリ ↗

作者:Yeachan-Heo★ 40,943 (whole repo)85 個の skill

★ Stars are for the whole repo, not each skill

Pick the skill to install

What it does

This repo is a collection of 85 skills

  • Connects Instruction files the AI reads, with steps that call an outside service
  • Account or key Some steps need a key for Anthropic, TYPESAFE_API_KEY (per the README)
  • Category コーディング
Maker’s original description
Teams-first Multi-agent orchestration for Claude Code
作者向け:README にバッジを付ける

作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/yeachan-heo-oh-my-claudecode.svg)](https://mcp.popnx.com/en/skills/yeachan-heo-oh-my-claudecode)

一緒に使える

同じ作業で AI をサービスにつなぐ MCP

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

作者:morluto広く使われている↓ 38.9万/週★ 46.9万7 日前更新

MCP · サービスにつなぐパソコンで動く

Fallow

Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.

作者:fallow-rs広く使われている↓ 244.1万/週★ 5385今日更新

MCP · サービスにつなぐパソコンで動く

似た Skill

同じ種類の作業。Skill 一覧と同じ並び

似たものと比べる
これ
oh-my-claudecode
reaandrej-karpathy-skillsgraphifyMoneyPrinterTurbo
作者Yeachan-Heomorlutomultica-aiGraphify-Labsharry0703
Skill 数851111
GitHub スター40,943468,733234,332150,287144,566
最終コード更新2026年11月19日2026年11月19日2026年4月20日2026年11月18日2026年11月18日
ライセンスMITMIT–Apache-2.0MIT

Yeachan-Heo による 85 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません

Pick the skill to install

Install only the ones you use. Open a skill to see how to install it

This set has 85 skills, too many to install at once: every installed skill’s description loads into every chat, so the AI picks the wrong one more easily. Pick only the ones you use from the list below

  • agent-doc-discipline

    Writing-time discipline for documents agents consume (the five surfaces, specs, tickets, .omc/skills/) — every rule checkable and carrying a why, steps before reference, one meaning in one home, no restating what the environment already says. Mandatory at drydock seed generation and the launch C5 s…

  • ai-slop-cleaner

    Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode

  • architect

    Settle types and module shape before cross-boundary code — competing designs explored in parallel, compared on API surface and invariants, decision recorded with rejected alternatives and an accepted-deviations register.

  • architecture-survey

    Periodic architecture survey — walks the module graph and reports ranked deepening candidates (shallow modules, hypothetical seams, logic behind the wrong seam). Survey, not rescue: it finds candidates and hands them to the captain; it never refactors on its own.

  • arena

    Run N parallel candidates at one brief and synthesize: rubric-first framing, isolated fan-out, a cross-judge on a different model, criterion-by-criterion pick, hand grafting. When one attempt would lock in the wrong shape.

  • ask

    Process-first advisor routing for Claude, Codex, Gemini, Antigravity, Grok, Cursor, or Muse via `omc ask`, with artifact capture and no raw CLI assembly

  • ask-navigator

    Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then work the frontier one ticket per session until the way is clear, and hand the collapsed decisions to /launch as a mission brief. Wayfinding…

  • autopilot

    Full autonomous execution from idea to working code

  • autoresearch

    Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior

  • babysit

    Drive an open PR to merge-ready on the watch-pr verdict policy — watch checks and review state, fix CI, address comments; never merges, rebases, or force-pushes. For 'get this green' or 'babysit PR #N'.

  • benchmark-checklist

    Vet a measured number before reporting or acting on it: name the limiter, measure the claimed work, repeat with variance, rule out the observer, label every claim. For any speedup, regression, or score you are about to report.

  • blast-radius

    Map what a change could break beyond the diff — dependents found by search and AST, classified certain/likely/unlikely — and prove the certain and likely ones by running their checks. Before risky refactors or signature changes.

  • bro

    Restate the last technical message in plain human language — no jargon, no shorthand, every fact and number kept. For 'say it plainly' or when a reply was too dense.

  • cancel

    Cancel any active OMC mode (autopilot, ralph, ultragoal, swarm, ultrapilot, pipeline, team) and clean up retired legacy state

  • commands

    No description from the maker

  • configure-notifications

    Configure notification integrations (Telegram, Discord, Slack) via natural language

  • correct

    Find the mistakes agents keep repeating in this repo and make each impossible at the highest enforcing level — lint rule, type guard, runtime check, script, then text — with every enforcement proven to fire.

  • create-formal-verification-skill

    Verify the project's riskiest invariant with TLA+, Lean, or Kani — chosen by property shape — and leave a project-local skill the next agent reruns; assumptions are part of the deliverable. For properties tests cannot reach.

  • create-verification-skill

    Generate the project's own verify skill: build/test/lint commands discovered by running them, a feature map of what each covers, manual checks, and an earned first verdict. Run once per repo.

  • debug

    Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction

  • deep-interview

    Socratic deep interview with mathematical ambiguity gating before explicit execution approval

  • deepinit

    Deep codebase initialization with hierarchical AGENTS.md documentation

  • diagram

    Use the smallest visual when prose must carry structure—control flow, call depth, module ownership, or change shape: pseudocode, call tree, component/file tree, Mermaid diagram, or diff. Skip it when prose already answers the question.

  • drydock

    Lay the keel of the shipyard harness in any repo — the 4-pillar shared environment (Context, Rules, Tools, Standards), seeded as two faces on day one (CLAUDE.md + GLOSSARY.md) with every other surface appearing on first use, so that every human and agent inherits the same design language and anyone…

  • execute

    Carry an approved task through to working, verified code

  • external-context

    Invoke parallel document-specialist agents for external web searches and documentation lookup

  • figure-it-out

    Design a rigorous bespoke playbook for a task no bundled skill fits — steps that each end in a check, verification commands, failure branches — stored where the checker validates and anchor-validated. For recurring unusual task shapes.

  • fix-ci

    Find the failing checks on the current PR, read their logs, classify the failure (real / flaky / environmental), fix the real ones with focused changes, and rerun to green with evidence. Use when CI is red and the failure is yours to fix.

  • fix-merge-conflicts

    Resolve merge conflicts non-interactively: start the integration, read both sides' intent from their commits, preserve both intents, validate on the resolved tree. Never force-pushes shared branches.

  • get-pr-comments

    Fetch and triage review threads on a PR: threads deduped with resolution state, each with a fix/dismiss/ask recommendation, bot findings read skeptically. Before addressing review feedback.

  • graph

    Deterministic orchestration graph runtime - declarative DAG pipelines with journal-based crash recovery

  • harbor

    Harbor intake for external work — the captain only handles unresolved decisions. Sweeps incoming issues and PRs, verifies every claim before disposition, reuses every decision already made, and hands the maintainer a docket whose pending items each carry one question with options, recommendation, i…

  • hillclimb

    Sustained single-metric improvement loop — hypothesis, before/after measurement against a fixed baseline, decision log, one accepted commit per verified win. For targets climbed over multiple rounds; not one-off fixes.

  • how

    Walk through how a subsystem works — a fast explorer maps the territory, an explainer writes the layered walkthrough. Use for "how does X work", onboarding on unfamiliar code, or before changing a subsystem you cannot yet explain.

  • hud

    Configure HUD display options (layout, presets, display elements)

  • in-your-own-words

    Play back the goal, the problem, and the success check in your own words when a brief is genuinely ambiguous — vague, contested, or leaving real forks open — so misunderstanding is caught cheaply. Not for well-specified or routine tasks.

  • intent

    Shipyard's internal requirements intake for non-engineer contributors (support/ops) — turn a pasted chat log or verbal problem report into a five-section intent.md through numbered batch questioning with a completion gate, walk it through tracker review with harbor's four records, and hand the acce…

  • interrogate

    Adversarial pass over a diff or design: three reviewers on different models each try to break it — correctness, security, edge cases — findings merged by severity into a blocking verdict. For contested or high-risk changes.

  • ketchup

    Catch up on everything since your last message: a 1-3 sentence executive summary, one status line per action item with evidence links, and open questions. For 'catch me up' after stepping away.

  • ketchup-video

    Catch the user up like /ketchup, with a short subtitled video of slides for what happened and the waiting calls as text under it. Use for /ketchup-video.

  • launch

    Shipyard's governed delivery pipeline — converge the mission, synthesize a durable spec, decompose vertical-slice tickets with blocking edges, run the frontier in parallel via team, close with verification, and report with a full decision log. Two entry gates — the yard gate (drydock audit) and the…

  • loft

    Loft the shape before cutting steel — answer a design question that prose cannot settle by building a throwaway artifact: a pure logic module in a clickable shell, or structurally different UI variants behind one route. The captain reacts to the artifact; the answer folds into the decision; the art…

  • maintain-formal-verification-skill

    Re-sync an existing formal verification skill after the covered code changed: re-check every assumption, update cited lines, rerun the tool; formally-verified only after a green rerun.

  • maintain-verification-skill

    Re-sync the project's verification skill when its commands drift — re-run each recorded command, update expectations and the feature map to what is true now, record the verdict actually earned.

  • map

    The yard's skill map — which skill owns which job, in delivery-loop order. Use when something needs doing but not which of the shipped skills owns it; the map routes, it never executes.

  • minimal-code-discipline

    YAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away

  • minimal-prose-discipline

    Writing-time discipline for the prose an agent speaks to a human (replies, reports, pointers): a protected core never rewritten (code, commands, paths, errors, negators, numbers), filler dies, no narration, auto-clarity where terse misleads

  • models

    Interactive setup for role-based model routing: edit team.roleRouting (provider, tier, per-provider reasoning effort; orchestrator model-only), check panel diversity, warn on missing provider CLIs.

  • omc-doctor

    Diagnose and fix oh-my-claudecode installation issues

  • omc-setup

    Install or refresh oh-my-claudecode for plugin, npm, and local-dev setups from the canonical setup flow

  • personal-mode

    Draft a user-level behavior profile from recent transcripts — cross-project preferences, habits, and standing calls stored under the user skills dir so every project's agents work the way you work. For 'make agents work like me'.

  • plan

    Strategic planning with optional interview workflow

  • pr

    Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.

  • principles

    Twenty-four engineering principles in five groups, mapped to the lane carrying each — premise testing, root causes, honest verification, domain modeling, convergence, context discipline. For design, debugging, or delegation briefs.

  • project-session-manager

    Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions

  • ralph

    Self-referential loop until task completion with configurable verification reviewer

  • ralplan

    Consensus planning entrypoint that auto-gates vague ralph/autopilot/team requests before execution

  • recall

    Reconstruct working context from artifacts in trust order — state files, notepad, verification ledger, decision trail, transcript tail — then report where work stands and the next action. After a break or crash.

  • refit

    Cross-session environment retrospective driven by OMC's own instrumentation — trace timelines, friction reports, logs, and plan notepads. Every finding lands on the surface that owns the fix (deterministic check, steering volume, tooling, or information access); nothing is written without user appr…

  • reflect

    After a long task, a three-reviewer panel audits the session transcript — tooling, judgment, missed alternatives — and proposes concrete skill edits. Findings feed skillify. For banking marathon-session lessons.

  • release

    Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASE_RULE.md, then guides the release

  • remember

    Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs

  • research

    Investigate an open question and return grounded, sourced findings

  • review

    Evaluate finished work for defects, risk, and simplification before it ships

  • sdd

    Spec-Driven Development. Interview → spec with acceptance criteria → plan → test-first execution. `/sdd full` runs the 6-phase pipeline instead.

  • self-improve

    Autonomous evolutionary code improvement engine with tournament selection

  • session-flow

    Reorient in the current Claude Code session with an evidence-backed map of its goal, pivots, outcomes, current step, and open decisions.

  • sharpen

    Aim a vague task at its real target without overspecifying: name the consumer, the observable change, the done-check, and the non-goals; at most one question when a real fork remains.

  • show-me-your-work

    Append-only decision trail for long or autonomous work: one TSV row per non-obvious decision — what was chosen, what was rejected and why, the deciding evidence. For work a human will audit later.

  • skill

    Manage local skills - list, add, remove, search, edit, setup wizard

  • skillify

    Turn a repeatable workflow from the current session into a reusable OMC skill draft

  • stacked-delivery

    Deliver a queue of changes as one linear stacked PR chain — each PR lands on the last, verdicts record patch-ids, rebases trigger re-verification, and landing goes bottom-up only. For 'stack them, I'll land them' or review-gated queues.

  • statechart

    Check a TLA+ model of a system that moves between states, such as a product flow or a protocol, and draw it as a Mermaid statechart. The report gives the shortest path to each state that breaks a rule. Use for /statechart.

  • tdd

    Test-first at pre-agreed seams — one test, one implementation, tracer-bullet red/green; independent expected values; substitutions only at the seam's boundary class; launch Phase 4 reference.

  • teachGoes with this repo’s lessons

    Explain a subsystem to a learner by composing how and why — the walkthrough cited to code, the decisions that shaped it, paced with a prediction check. For onboarding and knowledge transfer.

  • team

    N coordinated agents on shared task list using Claude Code implicit agent teams

  • technical-writing

    One layered standard for shipping prose — docs, RFCs, readmes, PR descriptions, commit messages: outcome first, one meaning one home, checkable statements, no filler. Composes with minimal-prose-discipline.

  • trace

    Evidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode

  • typescript-best-practices

    TypeScript grounding for type-system discipline: discriminated unions over flags, satisfies, parse-don't-validate at boundaries, branded primitives, no non-null assertions on external data.

  • ultragoal

    Durable multi-goal workflow that persists plan/ledger artifacts under .omc/ultragoal and prints Claude /goal handoff text for the active session

  • verify

    Verify that a change really works before you claim completion

  • visual-verdict

    Structured visual QA verdict for screenshot-to-reference comparisons

  • what-did-i-get-done

    Summarize authored commits over a period, grouped by theme with commit-range evidence, mechanical churn separated, and unfinished branches named. For standups and 'what did I get done'.

  • why

    Investigate why code is the way it is from evidence — human rulings verbatim, git archaeology, linked issues, incident records — every claim labeled evidence, inference, or guess. For 'why was this built this way'.

  • wiki

    LLM Wiki — persistent markdown knowledge base that compounds across sessions (Karpathy model)

Skill と MCP の違い

MCP = 手

AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。

Skill = 手順書

作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。

重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。

使えるアプリ

Claude CodeCodexCursorGemini CLI

提供元の README と repo のフォルダから判断

インストール

Pick a skill first

This repo has 85 skills. Pick one from the list above; its page shows every way to install it, including letting the AI install it and a ZIP

Let the AI install it
Upload to claude.ai

Go to the skill list ↑

提供元の最初の手順:カタログを追加(これだけでは Skill は入りません)

作者のコマンドを隠しています · GitHub のこのリポジトリからインストールしないため · 確認を通らなかったためコマンドを隠しています · 作者の GitHub ページからインストールしてください

提供元の README から引用。提供元のコードをダウンロードして実行します

話し合い

質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。

まだ投稿はありません。最初の質問や共有をどうぞ。

ここの投稿は利用者によるもので、PopNx チームのものではありません。

ログインして投稿

GitHub の情報

GitHub スター
40,943
Stars are for the whole repo, not each skill
提供元
Yeachan-Heo
ライセンス
MIT
最終コード更新
2026年11月19日
repo 内の SKILL.md(翻訳版とテンプレートを含む)
85
トピック
agentic-coding, ai-agents, automation, claude, claude-code, multi-agent-systems, oh-my-opencode, opencode, parallel-execution, vibe-coding