메뉴
Use for persistent TODO capture, daily brief retrieval, and shared Codex/Claude operating rules. Trigger on remember/track/follow-up requests, "nexus add/show/brief", or policy/workflow questions across Slack, Outlook, and Jira contexts. When in doubt, use this skill.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use for correlated API failures, cascading errors, and distributed-system incident tracing. Trigger on multi-service error spikes, dependency-chain analysis, circuit-breaker events, or requests to identify origin service and blast radius from logs/metrics across components. When in doubt, use this skill.
Use for memory, CPU, latency, and query-performance investigations, plus dependency-upgrade blast-radius analysis. Trigger on leak/OOM/profiling/regression reports or "what breaks if I upgrade X." Route to memory-leak or dependency-blast-radius workflow based on intent. When in doubt, use this skill.
Use for production incidents, outages, and service degradations, plus release-readiness gate checks. Trigger on 500 spikes, SLA breaches, latency/error surges, on-call alerts, rollback decisions, and RCA/post-mortem requests. Prioritize stabilization, timeline reconstruction, and evidence-led actions. When in doubt, use this skill.
Always-on token optimization rules. Apply on every response.
Use when something is failing, regressing, or behaving unexpectedly and the goal is root-cause analysis, narrowest fix, and verification. Covers CI/CD, tests, runtime, deployment, and tooling failures. Output should be RCA + fix + prevention, not design options. When in doubt, use this skill.
Use to convert any input into a ready-to-record YouTube Shorts script. Trigger on requests for 30-second scripts, hooks, reels/short-form video copy, or pasted topics/articles/bullets/URLs needing concise high-retention narration with CTA. When in doubt, use this skill.
| name | nexus |
| description | Use for persistent TODO capture, daily brief retrieval, and shared Codex/Claude operating rules. Trigger on remember/track/follow-up requests, "nexus add/show/brief", or policy/workflow questions across Slack, Outlook, and Jira contexts. When in doubt, use this skill. |
Shared operating rules for Codex and Claude Code sessions.
node "${CLAUDE_PLUGIN_ROOT}/bin/nexus.js" (requires Node >= 18; no npm install)~/.nexus/TODOS.md, ~/.nexus/state.jsonWhen the user asks to remember, track, add, or follow up on something:
Work, Python, Claude, Codex, AWS, Jira, Slack, Outlook, Personal, General.node "${CLAUDE_PLUGIN_ROOT}/bin/nexus.js" add "<task>".If the script fails: check that Node >= 18 is installed (node --version).
Run node "${CLAUDE_PLUGIN_ROOT}/bin/nexus.js" todos --limit 8. Output grouped by label, sorted by recency.
When the user asks for a daily brief or "what's on my plate":
~/.nexus/TODOS.md.~/.nexus/state.json.node "${CLAUDE_PLUGIN_ROOT}/bin/nexus.js" add "<task>".For TODO operations:
Outcome: [what was done]
Actions: [commands run]
Evidence: [nexus script output or confirmation]
Next Step: [what the user should do next]
For daily briefs:
Outcome:
Urgent:
Today:
Waiting:
Added TODOs:
Risks:
Next Step:
Input: "Remember to follow up with finance about the Outlook invoice."
Output:
Outcome: TODO added under Work.
Actions: node "${CLAUDE_PLUGIN_ROOT}/bin/nexus.js" add "Follow up with finance about Outlook invoice"
Evidence: ✓ Added to ~/.nexus/TODOS.md
Next Step: Review during tomorrow's daily brief.
Input: "What's on my plate today?"
Output:
Outcome: Daily brief generated from TODOS.md and state.json.
Urgent: Deploy hotfix for auth service (due today)
Today: Review PR #42, sync with design team
Waiting: Finance invoice reply
Added TODOs: none new
Risks: Auth deploy blocks two downstream services
Next Step: Start with the auth hotfix deploy.