Claude Skills by nexuslinkproductions

Nervous-system spine + afferent nerve: captures detected events once under a deterministic id and threads them across organs as OpenProcess entries. Use when durably recording an event (task/decision/fix/finding/idea/correction/build/handoff) so it survives compaction, closing an event, or pulling the open-work digest — e.g. after detecting something needing session continuity.

Retired skill tombstone. Do not invoke — use native planning plus llm-compat lanes for advisory work instead. Use when encountering a reference to /pco, /clone, or parallel-clone-orchestrator and need to redirect to the current replacement: native planning + llm-compat lanes.

Artifact perception, pattern extraction, weakness detection, and YURI-native reconstruction — inspired by Sharingan/Copy Technique, translated into enterprise-safe system behavior. Use when analyzing and integrating an external artifact (repo, document, PDF, prompt, codebase, system spec, workflow, memory log) into YURI without blind copying — e.g. 'analyze and integrate this safely', 'turn this into YURI OS DNA', or '/yuri pattern-mirror'.

Curated recipe for a PEER LANE (native Sonnet agent OR ollama nano-swarm) to build ONE alpha-factor-library signal/scoring/analysis module for the crypto trading engine — exact contract, signal interface, fail-open discipline, --test, capability tag, read-live-sigs, verify-locally, terse-data return. Use when dispatching a peer to build or extend an AFL module so the contract is not re-written each time.

Capture and compound pilot-user feedback (good + negative) into a ledger; ingest a pilot's git branch for passive signal; report polarity+tag patterns for improvement routing.

Optional human-in-the-loop (HITL) plan/diff review sublane — capture a plan, annotate it, ship structured feedback, and diff plan revisions. Mutually exclusive with the autonomous plan_dispatch_gate. AUTO-BLOCKS the next mutation with a reason until the plan is approved (review mode only, default OFF). Use when a human needs to review or annotate an agent plan before dispatch.

Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, or generate or update marketplace entries for plugin ordering and availability metadata.

Operational probability, calibration, and expected-value discipline for YURI OS decisions under uncertainty. Use when making or supporting a decision involving task priority, route selection, risk acceptance, opportunity ranking, forecast-backed planning, resource allocation, go/no-go judgment, escalation threshold, or postmortem calibration — e.g. '/yuri probability', '/probability', or '/pdc'.

Design, audit, and optimize prompts as task contracts with evidence, constraints, tool policy, output schemas, and evals. Use when the user asks for prompts, system instructions, prompting strategy, prompt quality, prompt optimization, RAG instructions, tool-agent instructions, or asks to avoid identity-roleplay phrasing.

Rewrite prompts, settings, tool loops, and structured output for Kimi K3 (model id kimi-k3, OpenAI Chat Completions compatible). Use when targeting Kimi K3 and you need reasoning_effort selection (low/high/max), strict json_schema structured output, tool-call / tool_call_id loop hygiene, automatic prefix caching, or removal of unsupported sampling controls. Triggers: 'adapt this for Kimi K3', 'prompt for kimi-k3', 'kimi k3 settings / reasoning_effort / json_schema / tool loop', or $prompting-...

Use when adapting, migrating, or writing a prompt or agent contract that will run on Claude Opus 5 (API id claude-opus-5) — legacy Opus/Sonnet prompts, coding, refactor, review, long-context, or multi-agent prompts; tuning effort, verbosity, progress cadence, subagent fan-out, or verification instructions; or diagnosing an unexpected refusal on a permitted internal task with route and context controls before any packet rewrite.

Use when evidence arrives in an ORDER that matters, when hypotheses interfere/are non-commuting, when you need the Schmidt coupling criterion for the cross-reference engine, or when a classical Bayes model may be missing order-effects — quantum-hypothesis-tracker.mjs does real-valued Hilbert-space hypothesis tracking (superposition until measurement, order-aware sequential evidence, QQ-equality), gated to beat classical Bayes on order-sensitive data without spurious control wins. Tier 3 of YU...

Identify recurring charges and subscriptions from receipts or email exports, and produce a clean summary with renewal dates, price changes, and cancellation drafts. Use when a user wants to audit spending without initiating payments or cancellations.

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Remotion best practices skill — stub. Populate with React-based video rendering patterns, composition structure, and YURI video generation workflows.

Build AE-grade 3D motion-design videos with Remotion (three.js + 2D overlays, frame-driven camera rigs, real scene transitions, cinematic motion blur, kinetic typography). Use when creating, extending, or rendering motion-graphics / presentation / explainer / promo / investor videos, or when adding 3D, transitions, motion blur, or kinetic type to a Remotion project.

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Convert mature research notes into draft Codex skills and supporting tool scaffolds. Use when a research thread has repeated stable behavior, enough evidence to justify reuse, and needs a reviewed draft before promotion into .claude/skills.

Analyze sales conversations, buyer signals, omissions, objections, positive momentum, retention, referrals, and depth-psychology hypotheses with evidence-tiered ethical guardrails. Use when the user asks for sales strategy, sales scripts, buyer psychology, closing, objection handling, NEPQ, Raving Fans, Jungian sales reads, or customer delight.

Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.

When verifying security/enforcement/safety claims — each layer needs its own evidence; don't over-extend a verified claim to the next unverified layer

Scaffolds per-repo configuration (issue tracker, triage labels, domain doc layout) that engineering skills assume. Use when first running `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` in a new repo, or when those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

User-invoked reverse-engineering + enhancement protocol for any source artifact: repos, codebases, docs, PDFs, screenshots, specs, workflows. Observe deeply, extract underlying technique (not property), expose weaknesses, then rebuild as a legally clean, Yuri OS / Yuri-aligned diamond design via 9-phase pipeline. Use when the user says \"activate Sharingan\", \"reverse-engineer this\", \"copy the technique not the code\", or wants to deeply understand and rebuild an artifact from first princi...

Guides creation and update of Codex skills with specialized knowledge, workflows, or tool integrations. Use when the user says \"create a new skill\", \"make a skill for X\", \"update this skill\", or wants to extend Codex capabilities with a reusable custom skill.

Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).

Use when executing implementation plans with independent tasks in the current session

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions \"red-green-refactor\", wants integration tests, or asks for test-first development.

Use before claiming a test/validator/gate result is commit-linked, on origin/main, on a specific sha, green-on-HEAD, or pre-existing — to avoid attributing worktree-derived results to a commit without verifying all inputs. Requires disposable-fresh worktree for clean-checkout reruns (never checkout over an existing path).

Three.js animation - keyframe animation, skeletal animation, morph targets, animation mixing. Use when animating objects, playing GLTF animations, creating procedural motion, or blending animations.

Three.js scene setup, cameras, renderer, Object3D hierarchy, coordinate systems. Use when setting up 3D scenes, creating cameras, configuring renderers, managing object hierarchies, or working with transforms.

Three.js geometry creation - built-in shapes, BufferGeometry, custom geometry, instancing. Use when creating 3D shapes, working with vertices, building custom meshes, or optimizing with instanced rendering.

Three.js interaction - raycasting, controls, mouse/touch input, object selection. Use when handling user input, implementing click detection, adding camera controls, or creating interactive 3D experiences.

Three.js lighting - light types, shadows, environment lighting. Use when adding lights, configuring shadows, setting up IBL, or optimizing lighting performance.

Three.js asset loading - GLTF, textures, images, models, async patterns. Use when loading 3D models, textures, HDR environments, or managing loading progress.

Three.js materials - PBR, basic, phong, shader materials, material properties. Use when styling meshes, working with textures, creating custom shaders, or optimizing material performance.

Three.js post-processing - EffectComposer, bloom, DOF, screen effects. Use when adding visual effects, color grading, blur, glow, or creating custom screen-space shaders.

Three.js shaders - GLSL, ShaderMaterial, uniforms, custom effects. Use when creating custom visual effects, modifying vertices, writing fragment shaders, or extending built-in materials.

Three.js textures - texture types, UV mapping, environment maps, texture settings. Use when working with images, UV coordinates, cubemaps, HDR environments, or texture optimization.

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

Native token efficiency mode that compresses output, minimizes verbosity, and enables caveman-style communication. Use when the user wants to save tokens, reduce output length, work in minimal-verbosity mode, or mentions token budgets or caveman mode.

The DECISION LENS for trading peers — recalls the CURRENT signal snapshot per market from the live ledger and renders it through the sim arsenal off ONE call: quantum factor-circuit order-optimal sequencing + decision-sim CVaR-robust sizing, sized against the MEASURED per-factor edge (from the edge-audit), correlation-aware. Emits an actionable call per market {side, sizePct, confidence, sequence}. Flat/zero-size when there is no measured edge after cost — the honest default. Sibling of trade...

The EDGE LENS for trading peers — recalls EVERY factor/indicator running from the live forecast ledger (no enumeration) and renders the whole pile through the edge arsenal off ONE call: multi-horizon scoring (the ladder) + deflated Sharpe (overfit) + Benjamini-Hochberg FDR (multiple-testing across the fleet) + spread-bounce + maker-fee falsification, then ranks only what survives ALL of it. Use when a peer must answer \"does ANY running factor have real, overfit-corrected, multiple-testing-co...

Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Resolves and loads task-relevant skills from the canonical local skill root after the workspace authority chain is loaded. Use when the user wants to discover available skills, load skill capabilities, or needs to know what skills are available for a task.

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

VideoDB integration skill — stub. Populate with VideoDB API usage, query patterns, and YURI integration notes when VideoDB is actively used.