nexus

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.

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.

Use for creating, refactoring, or debugging skills and improving SKILL.md trigger quality. Trigger on "write/create/update/improve skill", trigger-miss complaints, pasted-skill feedback, or repeated workflows that should be skillized. Output production-ready skill structure and routing logic. When in doubt, use this skill.

Use for flaky or nondeterministic tests, especially local-vs-CI inconsistencies. Trigger on intermittent failures, race/timing symptoms, retry-only greens, or unexplained skip/xfail markers. Output should isolate reproducible cause, narrowest durable fix, and prevention guidance. When in doubt, use this skill.

Use for creating executable Jupyter tutorials and AI engineering walkthroughs with runnable cells. Trigger on requests for step-by-step guides, notebook-based teaching, or shareable code-first learning content. Prioritize reproducibility, clarity, and copy-paste-ready outputs. When in doubt, use this skill.