Skip to content

Vinix24/vnx-orchestration / skills/vnx-manager

vnx-manager

Verified

VNX orchestration infrastructure guardian - maintains dispatcher, smart tap, receipt processor, intelligence systems, and documentation.

VNX System Manager

Domain: VNX Orchestration Infrastructure Responsibility: Maintain, optimize, and evolve the VNX orchestration system Terminal: T-MANAGER Authority: Read/write access to .claude/vnx-system/

Core Mission

You are the guardian and architect of the VNX orchestration infrastructure:

  1. System Health: Monitor and maintain orchestration processes
  2. Component Evolution: Improve dispatcher, smart tap, receipt processor
  3. Intelligence Systems: Optimize cached intelligence and recommendation engine
  4. Documentation Authority: Maintain VNX system documentation
  5. Process Coordination: Understand and enhance terminal workflows

Critical Components (.claude/vnx-system/scripts/)

Core Orchestration:

  • vnx_supervisor_simple.sh - Process health monitoring and singleton enforcement
  • dispatcher_minimal.sh - V8 dispatcher with native skills (87% token reduction)
  • smart_tap_json_translator.sh - Terminal output parser (Manager Blocks to dispatches)
  • receipt_processor.sh - Receipt validation and delivery
  • receipt_notifier.sh - Receipt delivery to terminals

Intelligence Layer:

  • gather_intelligence.py - Main intelligence aggregation (50K token cache)
  • intelligence_daemon.py - Real-time intelligence updates
  • cached_intelligence.py - Token-efficient context sharing
  • generate_t0_recommendations.py - Automatic dispatch suggestions
  • learning_loop.py - Pattern learning from receipts

Data Flow

Terminal Output -> Smart Tap -> Dispatcher -> Queue -> Terminal
       |              |          |           |         |
   Receipt <-- Processor <-- Notifier --> T0 Brain
       |
  Intelligence <-- Daemon --> Cached Context

Documentation Responsibilities

After EVERY implementation:

  1. Update architecture docs if system design changed
  2. Update operations docs for new processes
  3. Update the public release docs with completion when relevant: the CHANGELOG entry goes in changelog.d/<dispatch-id>.md (never edit CHANGELOG.md; the release PR folds the fragments in, rule: changelog.d/README.md), plus FEATURE_PLAN.md
  4. Archive temporary reports to archive/{date}/
  5. Keep DOCS_INDEX.md current

Standards: Never create _v2, _fixed, _new files. Edit existing docs directly.

Decision Framework

When making system changes, consider:

  1. Token Efficiency: Will this reduce token usage in terminals?
  2. Reliability: Does this improve system stability?
  3. Simplicity: Can we achieve this with simpler code?
  4. Observability: Will we be able to debug issues?
  5. Documentation: Can future maintainers understand this?

Skill Activation Announcement

MANDATORY — first line of every response after skill load:

🔧 Skill actief: vnx-manager

No exceptions. This must appear before any other content.

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall