Claude Skills by nexuslinkproductions

Client deliverable tracking and project management system for web agencies, design studios, marketing firms, and freelancers managing multiple simultaneous projects and client relationships. Use when the user says \"track deliverables\", \"what's overdue\", \"send a status update to client\", \"add a new project deliverable\", \"I need to see what's in review\", or when managing multiple client projects with deadlines and status tracking.

Secure local contract and document vault for managing business agreements with automatic expiration tracking, renewal deadline alerts, and compliance monitoring. Use when the user says \"track my contracts\", \"when does this lease expire\", \"add a new contract\", \"show me upcoming renewals\", \"what's my total subscription cost\", or when managing business agreements, leases, insurance policies, and SLAs with deadline awareness.

Wave-2 security hardening for Nexus Link — runs the diagnostic tools, dispatches the MURE build, verifies the gates. Invoke for "wave 2", "security hardening", "nexus security", "pre-customer security", "rls audit", "audit chain verify", "antipattern scan".

Always-on action boundary, risk classifier, and mutation approval gate for Yuri OS. Use when a user or agent invokes /yuri guard, /guard, or /ndig, or when any proposed action, tool call, or mutation needs risk classification, scope verification, and approval before execution.

Research and apply OpenAI/Codex workflow guidance, including docs, config, subagents, skills, memory, and local gpt-oss usage. Use when you need a compact, reusable brief for how to work safely and effectively with OpenAI agent tools.

Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; prioritize OpenAI docs MCP tools, use bundled references only as helper context, and restrict any fallback browsing to official OpenAI domains.

Compatibility redirect — opus-fleet's orchestration doctrine has moved to fleet-economy. This skill is a tombstone: it carries no roster, dispatch template, or execution rule of its own. If invoked by an old trigger (/opus-fleet, opus orchestrates, spawn agents, agent fleet, glm fleet), load fleet-economy instead.

Build compatibility adapters between Jarvis, OVOS, OpenClaw, and Oracle-native surfaces. Use when legacy triggers or old labels must be preserved while the visible OS surface is cleaned up.

Build Oracle memory surfaces: session logs, durable notes, local context, and retrieval. Use when the task touches historical context, research notes, or project memory on this OS.

Build Oracle registry surfaces for skills, packages, and installs. Use when the task touches local skill packs, discovery, publishing, or install/update flow on this OS.

Build Oracle task routing: session ownership, detached work, launch order, and handoff rules. Use when the task touches multi-step execution or agent swarm coordination on this OS.

Oracle audio-subsystem builder: STT, TTS, wakeword, call handoff, and audio routing for the Oracle shell. Invoke by name (oracle-voice) only when building the Oracle audio pipeline. NOTE: not the native dictation command — for Claude Code dictation use the built-in /voice.

Gates a lane claim against its WorkSubstrate scope and discovery footprint before the energy gate runs, verifying the lane stayed inside its granted authority. Use when a lane produces a claim that needs scope-and-footprint verification, or when invoking discovery-precision-gate to filter claims before energy evaluation.

Deterministic, read-only placement assessor that classifies YURI artifacts into canonical zones, scores purge candidates by hazard-decay staleness, and deduplicates. Use when generated artifacts (research docs, memories, reports, lane outputs, telemetry) need zone classification, staleness scoring, or dedup — or when invoking filing-assessor to recommend where an artifact belongs.

Foundry Core B bakeoff harness and promotion/demotion ledger that runs synthesized formula candidates up a staged promotion ladder and records every gate verdict to an append-only ledger. Use when formula candidates need scoring, promotion, or demotion through the staged ladder, or when invoking the bakeoff to test and govern formula quality.

Formula Foundry typing Core A — the legal-move generator that classifies formula input/output units into closed-set dimensions and rejects dimensionally-incoherent compositions. Use when composing formulas and needing to verify dimensional compatibility, cataloging formula banks, or checking whether one formula's output can legally feed another's input.

Human-readable cockpit that reads originator-telemetry.jsonl, groups by traceId, and prints a compact per-run timeline with elapsed time, heartbeat count, chars streamed, and status. Use when you need to see what a lane is doing without reading raw JSONL, or when invoking lane-telemetry-cockpit to inspect lane run summaries.

Mathematical memory for started-but-unclosed work that ranks open tasks, research, ideas, todos, skills, bugs, experiments, and handoffs by open mass (status, staleness, dependency centrality, risk, and value). Use when you need a math-grounded answer to 'what did we start but not finish?', or when invoking openprocess-pool to surface and prioritize unclosed work across all lanes.

LLM-wielded decoder instrument: translate text into a deterministic math object (tokens, numerology channels, dimensional classification). Use when the model needs a deterministic structural reading of text to reason over — e.g. decoding a brain dump's surface features, analyzing token patterns, or extracting numerology/dimensional signatures from input.

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.

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...

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

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.

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.

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.

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-cor...

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