claudecode-omc 5.11.0 → 5.13.0

package/bundled/upstream/ecc/skills/laravel-verification/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: laravel-verification
 description: "Verification loop for Laravel projects: env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness."
-origin: ECC
+metadata:
+  origin: ECC
 ---
 
 # Laravel Verification Loop

package/bundled/upstream/ecc/skills/latency-critical-systems/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: latency-critical-systems
 description: Use for latency-sensitive systems such as realtime dashboards, market data, streaming agents, execution gateways, queues, caches, or HFT-like infrastructure where freshness and p95 latency matter.
-origin: ECC
+metadata:
+  origin: ECC
 tools: Read, Write, Edit, Bash, Grep, Glob
 ---
 

package/bundled/upstream/ecc/skills/lead-intelligence/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: lead-intelligence
 description: AI-native lead intelligence and outreach pipeline. Replaces Apollo, Clay, and ZoomInfo with agent-powered signal scoring, mutual ranking, warm path discovery, source-derived voice modeling, and channel-specific outreach across email, LinkedIn, and X. Use when the user wants to find, qualify, and reach high-value contacts.
-origin: ECC
+metadata:
+  origin: ECC
 ---
 
 # Lead Intelligence

package/bundled/upstream/ecc/skills/llm-trading-agent-security/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: llm-trading-agent-security
 description: Security patterns for autonomous trading agents with wallet or transaction authority. Covers prompt injection, spend limits, pre-send simulation, circuit breakers, MEV protection, and key handling.
-origin: ECC direct-port adaptation
+metadata:
+  origin: ECC direct-port adaptation
 version: "1.0.0"
 ---
 

package/bundled/upstream/ecc/skills/logistics-exception-management/SKILL.md

@@ -10,8 +10,8 @@ description: >
 license: Apache-2.0
 version: 1.0.0
 homepage: https://github.com/affaan-m/everything-claude-code
-origin: ECC
 metadata:
+  origin: ECC
   author: evos
   clawdbot:
     emoji: ""

package/bundled/upstream/ecc/skills/make-interfaces-feel-better/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: make-interfaces-feel-better
 description: Apply concrete design-engineering details that make interfaces feel polished. Use when reviewing or improving UI spacing, typography, borders, shadows, motion, hit areas, icons, text wrapping, and interaction states.
-origin: community
+metadata:
+  origin: community
 ---
 
 # Make Interfaces Feel Better

package/bundled/upstream/ecc/skills/manim-video/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: manim-video
 description: Build reusable Manim explainers for technical concepts, graphs, system diagrams, and product walkthroughs, then hand off to the wider ECC video stack if needed. Use when the user wants a clean animated explainer rather than a generic talking-head script.
-origin: ECC
+metadata:
+  origin: ECC
 ---
 
 # Manim Video

package/bundled/upstream/ecc/skills/market-research/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: market-research
 description: Conduct market research, competitive analysis, investor due diligence, and industry intelligence with source attribution and decision-oriented summaries. Use when the user wants market sizing, competitor comparisons, fund research, technology scans, or research that informs business decisions.
-origin: ECC
+metadata:
+  origin: ECC
 ---
 
 # Market Research

package/bundled/upstream/ecc/skills/marketing-campaign/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: marketing-campaign
 description: End-to-end marketing campaign planning and execution. Covers audience research, positioning, campaign angle definition, landing page copy, email sequences, social posts, ad copy, short-form video scripts, and content calendars. Use as the orchestration layer for multi-channel product launches.
-origin: ECC
+metadata:
+  origin: ECC
 ---
 
 # Marketing Campaign

package/bundled/upstream/ecc/skills/mcp-server-patterns/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: mcp-server-patterns
 description: Build MCP servers with Node/TypeScript SDK — tools, resources, prompts, Zod validation, stdio vs Streamable HTTP. Use Context7 or official MCP docs for latest API.
-origin: ECC
+metadata:
+  origin: ECC
 ---
 
 # MCP Server Patterns

package/bundled/upstream/ecc/skills/messages-ops/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: messages-ops
 description: Evidence-first live messaging workflow for ECC. Use when the user wants to read texts or DMs, recover a recent one-time code, inspect a thread before replying, or prove which message source was actually checked.
-origin: ECC
+metadata:
+  origin: ECC
 ---
 
 # Messages Ops

package/bundled/upstream/ecc/skills/ml-adoption-playbook/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: ml-adoption-playbook
+description: End-to-end methodology for AI agents and software engineers to add machine learning algorithms to existing non-ML codebases. Covers problem framing, data readiness, architectural decoupling, and baseline model integration.
+origin: ECC
+---
+
+# ML Adoption Playbook
+
+This skill provides an adaptive methodology for implementing machine learning models into existing software engineering projects. It bridges the gap between traditional SWE and MLOps by structuring how ML should be researched, decoupled, trained, and integrated.
+
+## When to Activate
+
+- A user asks to "add ML" or "add an algorithm" to their existing codebase.
+- Planning the integration of a new model (e.g., recommendation, classification, forecasting) into a non-ML application.
+- Structuring a workflow for an agent to build, train, and deploy an ML component adaptively.
+
+## Phase 1: Problem Framing & Feasibility
+
+Before writing model code, establish the "why" and "how".
+- **Heuristic Check:** Ask the user if a simple heuristic (e.g., regex, rule-based sorting) could solve the problem faster. If yes, start there.
+- **Metric Definition:** Define what business metric the ML model is trying to improve (e.g., click-through rate, reduced latency).
+- **Mistake Budget:** Define what a "bad" prediction looks like and how the system should handle it.
+
+## Phase 2: Data Readiness
+
+ML is useless without clean, accessible data.
+- **Audit Data Sources:** Identify where the training data lives. Is it a live database, a static CSV, or an API?
+- **Data Contract:** Establish a schema for the input data. What features are required? What happens if a feature is missing?
+- **Leakage Prevention:** Ensure the user's proposed data split does not accidentally leak future information into the training set (e.g., chronological splitting for time-series data).
+
+## Phase 3: Architectural Integration & Decoupling
+
+Do not tightly couple model inference to core business logic.
+- **API Boundary:** Suggest placing the model behind an API endpoint (e.g., using `fastapi-patterns` or `django-patterns`) or a dedicated service class.
+- **Fallback Mechanisms:** Design a default state. If the model takes too long to respond or throws an error, the system must gracefully fall back to a hardcoded rule.
+- **Feature Flags:** Wrap the new ML inference call in a feature flag so it can be rolled out (or rolled back) safely.
+
+## Phase 4: Model Implementation & Training
+
+Structure the code for reproducibility and iteration.
+- **Start Simple:** Build a baseline model first (e.g., a simple scikit-learn Logistic Regression or a barebones PyTorch linear layer).
+- **Reproducibility:** Apply `pytorch-patterns` or similar best practices: fix random seeds, make code device-agnostic, and explicitly document tensor/array shapes.
+- **Automated Evidence:** Require tests for the data transforms and inference schema. Do not accept a model without an evaluation script comparing it against the baseline.
+
+## Phase 5: Handoff to MLOps
+
+Once the baseline model is integrated, shift focus to continuous operations.
+- **Refer to `mle-workflow`:** Guide the user toward setting up experiment tracking, model registries, and drift detection.
+- **CI/CD:** Add the model evaluation step to the existing CI pipeline to ensure future commits do not degrade model performance.
+
+## Iterative Agent Workflow
+
+When assisting a user via this playbook, agents should:
+1. **Ask clarifying questions** to complete Phase 1 before proposing architectures.
+2. **Draft a data contract** in Phase 2 for user approval.
+3. **Write the decoupling interface** (API/Service) in Phase 3 *before* writing the training loop.
+4. **Deliver a reproducible script** in Phase 4 that trains the model and saves the artifact.

package/bundled/upstream/ecc/skills/mle-workflow/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: mle-workflow
 description: Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML systems beyond one-off notebooks.
-origin: ECC
+metadata:
+  origin: ECC
 ---
 
 # Machine Learning Engineering Workflow

package/bundled/upstream/ecc/skills/motion-patterns/SKILL.md

@@ -337,8 +337,7 @@ export function ExpandingCard({ title, body }: { title: string; body: string })
     duration: motionTokens.duration.normal,
     ease: motionTokens.easing.smooth,
   }}
->
-  {children}
+> {children}
 </motion.div>
 ```
 

package/bundled/upstream/ecc/skills/motion-ui/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: motion-ui
 description: "Production-ready UI motion system for React/Next.js. Use when implementing animations, transitions, or motion patterns."
-origin: ECC
+metadata:
+  origin: ECC
 ---
 
 # Motion System v4.2

package/bundled/upstream/ecc/skills/mysql-patterns/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: mysql-patterns
 description: MySQL and MariaDB schema, query, indexing, transaction, replication, and connection-pool patterns for production backends.
-origin: ECC
+metadata:
+  origin: ECC
 ---
 
 # MySQL Patterns

package/bundled/upstream/ecc/skills/nanoclaw-repl/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: nanoclaw-repl
 description: Operate and extend NanoClaw v2, ECC's zero-dependency session-aware REPL built on claude -p.
-origin: ECC
+metadata:
+  origin: ECC
 ---
 
 # NanoClaw REPL

package/bundled/upstream/ecc/skills/nestjs-patterns/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: nestjs-patterns
 description: NestJS architecture patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production-grade TypeScript backends.
-origin: ECC
+metadata:
+  origin: ECC
 ---
 
 # NestJS Development Patterns

package/bundled/upstream/ecc/skills/netmiko-ssh-automation/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: netmiko-ssh-automation
 description: Safe Python Netmiko patterns for read-only collection, bounded batch SSH, TextFSM parsing, guarded config changes, timeouts, and network automation error handling.
-origin: community
+metadata:
+  origin: community
 ---
 
 # Netmiko SSH Automation

package/bundled/upstream/ecc/skills/network-bgp-diagnostics/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: network-bgp-diagnostics
 description: Diagnostics-only BGP troubleshooting patterns for neighbor state, route exchange, prefix policy, AS path inspection, and safe evidence collection.
-origin: community
+metadata:
+  origin: community
 ---
 
 # Network BGP Diagnostics

package/bundled/upstream/ecc/skills/network-config-validation/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: network-config-validation
 description: Pre-deployment checks for router and switch configuration, including dangerous commands, duplicate addresses, subnet overlaps, stale references, management-plane risk, and IOS-style security hygiene.
-origin: community
+metadata:
+  origin: community
 ---
 
 # Network Config Validation

package/bundled/upstream/ecc/skills/network-interface-health/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: network-interface-health
 description: Diagnose interface errors, drops, CRCs, duplex mismatches, flapping, speed negotiation issues, and counter trends on routers, switches, and Linux hosts.
-origin: community
+metadata:
+  origin: community
 ---
 
 # Network Interface Health

package/bundled/upstream/ecc/skills/nextjs-turbopack/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: nextjs-turbopack
 description: Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.
-origin: ECC
+metadata:
+  origin: ECC
 ---
 
 # Next.js and Turbopack

package/bundled/upstream/ecc/skills/nodejs-keccak256/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: nodejs-keccak256
 description: Prevent Ethereum hashing bugs in JavaScript and TypeScript. Node's sha3-256 is NIST SHA3, not Ethereum Keccak-256, and silently breaks selectors, signatures, storage slots, and address derivation.
-origin: ECC direct-port adaptation
+metadata:
+  origin: ECC direct-port adaptation
 version: "1.0.0"
 ---
 

package/bundled/upstream/ecc/skills/nutrient-document-processing/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: nutrient-document-processing
 description: Process, convert, OCR, extract, redact, sign, and fill documents using the Nutrient DWS API. Works with PDFs, DOCX, XLSX, PPTX, HTML, and images.
-origin: ECC
+metadata:
+  origin: ECC
 ---
 
 # Nutrient Document Processing

package/bundled/upstream/ecc/skills/nuxt4-patterns/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: nuxt4-patterns
 description: Nuxt 4 app patterns for hydration safety, performance, route rules, lazy loading, and SSR-safe data fetching with useFetch and useAsyncData.
-origin: ECC
+metadata:
+  origin: ECC
 ---
 
 # Nuxt 4 Patterns

package/bundled/upstream/ecc/skills/openclaw-persona-forge/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: openclaw-persona-forge
 description: "为 OpenClaw AI Agent 锻造完整的龙虾灵魂方案。根据用户偏好或随机抽卡， 输出身份定位、灵魂描述(SOUL.md)、角色化底线规则、名字和头像生图提示词。 如当前环境提供已审核的生图 skill，可自动生成统一风格头像图片。 当用户需要创建、设计或定制 OpenClaw 龙虾灵魂时使用。 不适用于：微调已有 SOUL.md、非 OpenClaw 平台的角色设计、纯工具型无性格 Agent。 触发词：龙虾灵魂、虾魂、OpenClaw 灵魂、养虾灵魂、龙虾角色、龙虾定位、 龙虾剧本杀角色、龙虾游戏角色、龙虾 NPC、龙虾性格、龙虾背景故事、 lobster soul、lobster character、抽卡、随机龙虾、龙虾 SOUL、gacha。"
-origin: community
+metadata:
+  origin: community
 ---
 
 # 龙虾灵魂锻造炉

package/bundled/upstream/ecc/skills/opensource-pipeline/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: opensource-pipeline
 description: "Open-source pipeline: fork, sanitize, and package private projects for safe public release. Chains 3 agents (forker, sanitizer, packager). Triggers: '/opensource', 'open source this', 'make this public', 'prepare for open source'."
-origin: ECC
+metadata:
+  origin: ECC
 ---
 
 # Open-Source Pipeline Skill

package/bundled/upstream/ecc/skills/orch-add-feature/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: orch-add-feature
+description: Orchestrate building a brand-new feature end to end — research, plan, TDD implementation, review, and gated commit — by delegating each phase to the matching ECC agent. Use when adding a capability that does not exist yet.
+metadata:
+  origin: ECC
+---
+
+# orch-add-feature
+
+Actor · action · target: **orch · add · feature**. Thin wrapper over the shared
+engine in [`orch-pipeline`](../orch-pipeline/SKILL.md).
+
+## When to Use
+
+- The user wants a capability that does **not exist yet** ("add", "build",
+  "implement", "support …").
+- It is net-new behavior — not a correction (`orch-fix-defect`) and not an
+  alteration of existing behavior (`orch-change-feature`).
+
+## Operation settings
+
+- **Default size floor:** standard — run Research + Plan unless clearly small.
+- **Phase mask:** 0 → 1 → 2 → 4 → 5 → 6 (skip 3 Scaffold; that is MVP-only).
+- **First move (phase 4):** write *new* failing tests for the new behavior, then
+  implement to green.
+
+## How It Works
+
+1. Run the `orch-pipeline` engine with the settings above.
+2. Classify size first; small / trivial features collapse toward 4 → 5 → 6.
+3. Stop at **Gate 1** (plan approval) and **Gate 2** (pre-commit).
+4. Add `security-reviewer` if the feature touches a security trigger.
+
+> Related: `/feature-dev` is a standalone version of this flow. `orch-add-feature`
+> differs by sharing the `orch-pipeline` engine — the size classifier and the two
+> gates — with the rest of the family, so it right-sizes trivial features to 4 → 5 → 6.
+
+## Example
+
+```
+orch-add-feature: add OAuth2 login to nws-poller
+→ research existing auth libs → plan task_list  [GATE 1: approve]
+→ TDD each task → code-review (+ security-reviewer: auth path)
+→ commit  [GATE 2: confirm]
+```

package/bundled/upstream/ecc/skills/orch-build-mvp/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: orch-build-mvp
+description: Orchestrate bootstrapping a working MVP from a design or spec document — ingest the doc, plan thin vertical slices, scaffold the first end-to-end slice, then TDD-implement, review, and gated commit. Use to turn an SDD/PRD into a running starting point.
+metadata:
+  origin: ECC
+---
+
+# orch-build-mvp
+
+Actor · action · target: **orch · build · mvp**. Thin wrapper over the shared
+engine in [`orch-pipeline`](../orch-pipeline/SKILL.md).
+
+## When to Use
+
+- The user has a **design / spec document** (SDD, PRD, system_design) and wants a
+  working vertical slice bootstrapped from it.
+- Takes a doc path as its argument, e.g. `civicpulse/docs/SDD-v0.6.md`.
+
+## Operation settings
+
+- **Default size floor:** large — this is the full pipeline including Scaffold.
+- **Phase mask:** 0 (read the spec) → 1 → 2 (heavy) → 3 (scaffold) → 4 → 5 → 6.
+- **First move (phase 0 → 2):** read the doc; extract scope, locked decisions,
+  and the feature list; order it into **thin vertical slices** (one end-to-end
+  path first, not all-models-then-all-views). Phase 3 stands up that first slice.
+
+## How It Works
+
+1. Run the `orch-pipeline` engine with the settings above.
+2. **Reuse the existing GAN harness** instead of hand-rolling an iterate loop:
+   - Translate the SDD into `gan-harness/spec.md` + `gan-harness/eval-rubric.md`
+     (this stands in for what `gan-planner` would generate — you already have the spec).
+   - Drive the build with `/gan-build "<one-line brief>" --skip-planner`
+     (defaults: `--max-iterations 15`, `--pass-threshold 7.0`,
+     `--eval-mode playwright`; use `--eval-mode code-only` for non-UI slices).
+   - That command runs the `gan-generator` → `gan-evaluator` loop and writes
+     `gan-harness/feedback/feedback-NNN.md` until the score passes or plateaus.
+3. Stop at **Gate 1** (slice plan) and **Gate 2** (pre-commit). Commit the
+   scaffold and each slice as separate `feat:` commits.
+4. Add `security-reviewer` for any slice touching a security trigger.
+
+## Example
+
+```
+orch-build-mvp: civicpulse/docs/SDD-v0.6.md
+→ read SDD → slice list (vertical) → scaffold slice 1  [GATE 1: approve]
+→ /gan-build --skip-planner (generator → evaluator loop) scores vs spec → review
+→ commit feat:  [GATE 2: confirm] → next slice
+```

package/bundled/upstream/ecc/skills/orch-change-feature/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: orch-change-feature
+description: Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit. Use when behavior is not broken but should be different.
+metadata:
+  origin: ECC
+---
+
+# orch-change-feature
+
+Actor · action · target: **orch · change · feature**. Thin wrapper over the
+shared engine in [`orch-pipeline`](../orch-pipeline/SKILL.md).
+
+## When to Use
+
+- An existing feature **works**, but the desired behavior is different ("change",
+  "adjust", "make it also …", "instead of X do Y").
+- Distinguish from siblings:
+  - **not** broken → not `orch-fix-defect` (no bug to reproduce).
+  - **not** new → not `orch-add-feature` (the capability already exists).
+
+## Operation settings
+
+- **Default size floor:** small — most tweaks are a function or two.
+- **Phase mask:** 0 → (1 only if the new behavior needs research) → light 2 →
+  4 → 5 → 6.
+- **First move (phase 4):** update the *existing* tests to express the new
+  desired behavior, then change the implementation until they pass. Changing the
+  tests first is what separates a tweak from a fix.
+
+## How It Works
+
+1. Run the `orch-pipeline` engine with the settings above.
+2. Keep the plan light — only `standard`+ size warrants the full `planner` pass.
+3. Stop at **Gate 1** (plan / changed-test approval) and **Gate 2** (pre-commit).
+4. Add `security-reviewer` if the change touches a security trigger.
+
+## Example
+
+```
+orch-change-feature: make nws-poller alert at 2 warnings instead of 3
+→ update threshold tests to new spec → change impl to green
+→ code-review → commit  [GATE 2: confirm]
+```

package/bundled/upstream/ecc/skills/orch-fix-defect/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: orch-fix-defect
+description: Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit — by delegating each phase to the matching ECC agent. Use when existing behavior is broken or wrong.
+metadata:
+  origin: ECC
+---
+
+# orch-fix-defect
+
+Actor · action · target: **orch · fix · defect**. Thin wrapper over the shared
+engine in [`orch-pipeline`](../orch-pipeline/SKILL.md).
+
+## When to Use
+
+- Something is **broken**: wrong output, an error, a crash, a regression.
+- Distinguish from siblings:
+  - behavior is correct but you want it different → `orch-change-feature`.
+  - the capability does not exist yet → `orch-add-feature`.
+
+## Operation settings
+
+- **Default size floor:** small (often trivial).
+- **Phase mask:** 0 → (light 2 only if root cause is non-obvious or standard+) →
+  4 → 5 → 6. Research (1) is usually skipped.
+- **First move (phase 4):** reproduce the bug as a **new failing** test
+  (regression test), then fix until it goes green. Proving the bug exists first
+  is what separates a fix from a tweak.
+
+## How It Works
+
+1. Run the `orch-pipeline` engine with the settings above.
+2. If the root cause is unclear, scope it with `code-explorer` before the red
+   test; escalate build breaks to `build-error-resolver` / `/build-fix`.
+3. Stop at **Gate 1** (only if a plan was produced) and **Gate 2** (pre-commit).
+4. Add `security-reviewer` if the defect sits in a security-sensitive path.
+
+## Example
+
+```
+orch-fix-defect: poller crashes on empty NWS response
+→ write failing test reproducing the crash → fix to green
+→ code-review → commit  [GATE 2: confirm]   (commit: fix:)
+```