个人作者

justnnc

更新于 2026-10-22

Skills
25
仓库
1
职业覆盖
0
场景覆盖
0
Stars
★ 0

justnnc 的 Skills 25

justnnc
justnnc/skills

codex-worker

The OpenAI Codex CLI as a worker under Claude. Use when the user names Codex ("have Codex review this", "ask Codex", "run this on Codex", "hand this to Codex"), wants work done on Codex's quota instead of Claude tokens, or wants a review from another model family. Not for tasks that need this conversation's context, the user's running application, or tools only Claude has.

★ 0
justnnc
justnnc/skills

claude-worker

A headless Claude Code run started in another repository, so the work loads that repository's own instructions instead of the current session's. Use when work belongs to a different repository than the one this session is in ("do this in the other repo", "work on the docs repo from here"), when a subagent would carry the wrong project's rules, or when a run needs its own tool set or settings. Not for work in the current repository (use an ordinary subagent), anything that needs a conversation mid-run, or tasks that need this session's context.

★ 0
justnnc
justnnc/skills

spec-audit

A read-only audit of a project's specs against the work that just landed. Use when a batch, feature or set of changes has been merged or is about to be pushed, when the user asks whether a spec is up to date, accurate or drifted from the code, or before a design discussion leans on a spec's text. Not for writing a new spec or design document, reviewing a design document, reviewing code for bugs, or planning work that is not built yet.

★ 0
justnnc
justnnc/skills

skill-craft

A craft checklist for agent skills. Use when the user asks to write, improve, review, test or tighten a skill, a SKILL.md, an agent definition or a reusable brief, or asks why an agent skips, misreads or never triggers a skill. Not for the subject matter of a skill, only how it is written.

★ 0
justnnc
justnnc/skills

prove-by-running

Execution proof that a script or tool works. Use when about to trust a new or changed script, hook, migration or release tool, and always for anything that rewrites git history, publishes or pushes, deletes, or transforms data; also when the user asks "does this actually work", "test this script", "prove it" or "try it on a copy first". Not for reviewing code by reading it, for writing unit tests of a library, or for fixing the faults found.

★ 0
justnnc
justnnc/skills

parallel-refactor

A fan-out of one large mechanical code change across parallel subagents. Use when a refactor, rename, migration or API move touches hundreds of call sites across many files, when the user asks to split a change per file or component or hand it to several agents at once, or asks how big a change is and whether it is mechanical. Not for edits inside one file, a redesign whose target shape is not yet decided, or a change small enough to make serially.

★ 0
justnnc
justnnc/skills

how-it-works

A cited, read-only explanation of how a mechanism in a codebase works. Use when the user asks "how does X work in this code", "where is Y computed", "walk me through Z", or wants a reference implementation read to compare with their own, in a large or unfamiliar codebase. Not for a file or function already known (just read it), bug hunting or debugging, reviewing a diff, or changing code.

★ 0
justnnc
justnnc/skills

feature-spec

A path from a feature idea to a written design document the user has decided. Use when the user wants to explore, scope or specify a new feature, tool or plugin, asks "does this already exist?" or "should we build this?" before building it, or asks for a spec or design doc for something not yet built. Not for implementing or planning the build of a feature already designed, auditing a spec against built code, reviewing a finished plan, or a single decision that needs no research.

★ 0
justnnc
justnnc/skills

adversarial-review

A red-team review of a proposal before it is built or acted on. Use when the user asks for an adversarial, red-team or devil's-advocate review, or when a design, plan, change or analysis is about to be decided and nobody has tried to break it. Not for checking numbers or hunting bugs in a code diff.

★ 0
justnnc
justnnc/skills

graders

暂无简介

★ 0
justnnc
justnnc/skills

graders

暂无简介

★ 0
justnnc
justnnc/skills

graders

暂无简介

★ 0
justnnc
justnnc/skills

graders

暂无简介

★ 0
justnnc
justnnc/skills

graders

暂无简介

★ 0
justnnc
justnnc/skills

graders

暂无简介

★ 0
justnnc
justnnc/skills

graders

暂无简介

★ 0
justnnc
justnnc/skills

graders

暂无简介

★ 0
justnnc
justnnc/skills

graders

暂无简介

★ 0