How do I install the Cc Opus First Pass skill?

Run npx skillmds@latest add xukai-ye/cc-opus-first-pass in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cc Opus First Pass safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cc Opus First Pass?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cc Opus First Pass free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cc Opus First Pass?

Xukai-YE (@xukai-ye) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cc Opus First Pass by xukai-ye — Agent Skill

Name: Cc Opus First Pass
Rating: 4.5 (4 reviews)
Author: Xukai-YE

File contents

CC Opus First Pass

Use this skill to classify a task into the 3-tier system and produce an analysis brief.

Model order (always Opus-first for analysis):

claude-opus-4-6
claude-sonnet-4-6
opus
sonnet

3-Tier Classification

Classify into exactly one tier: TINY, MEDIUM, or HIGH-RISK.

The classifier is risk-first: the highest-risk signal present determines the tier.

Risk Signals

Signal	Low	Moderate	High
Files / modules / layers	1 file, local path	2-4 files, 1 module boundary	Crosses modules or layers
Auth / security	None	Minor permission check	Trust boundary, secrets, auth flow
State / concurrency	None	Simple state update	Shared state, locks, async coordination
Schema / migration	None	Additive field	Breaking change or migration
Build / config / deps	None	Config value tweak	Build system, CI, or new dependency
Public API surface	None	Backward-compatible addition	Breaking change or redesign
Blast radius clarity	Obvious	Mostly clear	Hard to reason about
Design tradeoffs	None	Minor choice	Significant alternatives

Decision

TINY: All signals low. <= 15 lines, 1 file, obvious blast radius. -> Skip this skill; Codex handles directly.
MEDIUM: Any moderate signal and no high signals. -> cc-main-implement -Tier medium (Sonnet-first).
HIGH-RISK: Any high signal. -> Full orchestration: plan review -> cc-main-implement -Tier high-risk (Opus-first) -> checkpoint reviews.

Highest-risk signal wins.

Workflow

Classify the task.
If TINY, skip this skill and proceed in Codex.
If MEDIUM or HIGH-RISK, invoke the bundled script:

powershell -NoProfile -ExecutionPolicy Bypass -File "scripts/invoke-cc-opus-first-pass.ps1" `
  -UserRequest "$ARGUMENTS" `
  -WorkingDirectory "$PWD"

If specific files are already known, include them as context paths:

powershell -NoProfile -ExecutionPolicy Bypass -File "scripts/invoke-cc-opus-first-pass.ps1" `
  -UserRequest "$ARGUMENTS" `
  -WorkingDirectory "$PWD" `
  -ContextPaths "src/app.ts","src/auth.ts"

Read Claude Code output and use it as a first-pass brief, not as unquestioned truth.
Codex still owns:

final implementation decisions
actual edits
verification
final user-facing explanation

Failure Handling

If Claude Code is unavailable, not authenticated, or the command fails:

note the failure briefly
continue locally in Codex
do not block the task solely because the external first pass is unavailable

Expected Claude Output

The script asks Claude Code for:

Tier Verdict: TINY, MEDIUM, or HIGH-RISK
Risk Signal Assessment (which signals triggered and at what level)
Why (concise justification)
Likely Affected Files
Implementation Plan
Risks and Edge Cases
Suggested Tests
Patch Sketch

Use that output to guide the Codex implementation and review pass.

---name: cc-opus-first-passdescription: Use to classify a coding task into the 3-tier system (tiny/medium/high-risk) and get an analysis brief before implementation. Always uses Opus 4.6 first for deep reasoning. Skip for tasks that are obviously tiny.---# CC Opus First PassUse this skill to classify a task into the 3-tier system and produce an analysis brief.Model order (always Opus-first for analysis):- `claude-opus-4-6`- `claude-sonnet-4-6`- `opus`- `sonnet`## 3-Tier ClassificationClassify into exactly one tier: **TINY**, **MEDIUM**, or **HIGH-RISK**.The classifier is **risk-first**: the highest-risk signal present determines the tier.### Risk Signals| Signal | Low | Moderate | High ||--------|-----|----------|------|| Files / modules / layers | 1 file, local path | 2-4 files, 1 module boundary | Crosses modules or layers || Auth / security | None | Minor permission check | Trust boundary, secrets, auth flow || State / concurrency | None | Simple state update | Shared state, locks, async coordination || Schema / migration | None | Additive field | Breaking change or migration || Build / config / deps | None | Config value tweak | Build system, CI, or new dependency || Public API surface | None | Backward-compatible addition | Breaking change or redesign || Blast radius clarity | Obvious | Mostly clear | Hard to reason about || Design tradeoffs | None | Minor choice | Significant alternatives |### Decision- **TINY**: All signals low. <= 15 lines, 1 file, obvious blast radius. -> Skip this skill; Codex handles directly.- **MEDIUM**: Any moderate signal and no high signals. -> `cc-main-implement -Tier medium` (Sonnet-first).- **HIGH-RISK**: Any high signal. -> Full orchestration: plan review -> `cc-main-implement -Tier high-risk` (Opus-first) -> checkpoint reviews.**Highest-risk signal wins.**## Workflow1. Classify the task.2. If `TINY`, skip this skill and proceed in Codex.3. If `MEDIUM` or `HIGH-RISK`, invoke the bundled script:```powershellpowershell -NoProfile -ExecutionPolicy Bypass -File "scripts/invoke-cc-opus-first-pass.ps1" ` -UserRequest "$ARGUMENTS" ` -WorkingDirectory "$PWD"```4. If specific files are already known, include them as context paths:```powershellpowershell -NoProfile -ExecutionPolicy Bypass -File "scripts/invoke-cc-opus-first-pass.ps1" ` -UserRequest "$ARGUMENTS" ` -WorkingDirectory "$PWD" ` -ContextPaths "src/app.ts","src/auth.ts"```5. Read Claude Code output and use it as a first-pass brief, not as unquestioned truth.6. Codex still owns:- final implementation decisions- actual edits- verification- final user-facing explanation## Failure HandlingIf Claude Code is unavailable, not authenticated, or the command fails:- note the failure briefly- continue locally in Codex- do not block the task solely because the external first pass is unavailable## Expected Claude OutputThe script asks Claude Code for:1. Tier Verdict: TINY, MEDIUM, or HIGH-RISK2. Risk Signal Assessment (which signals triggered and at what level)3. Why (concise justification)4. Likely Affected Files5. Implementation Plan6. Risks and Edge Cases7. Suggested Tests8. Patch SketchUse that output to guide the Codex implementation and review pass.

Frequently asked questions

Cc Opus First Pass