@harness-engineering/cli 1.23.2 → 1.24.1

package/dist/agents/skills/cursor/harness-planning/skill.yaml

@@ -1,6 +1,7 @@
 name: harness-planning
 version: "1.0.0"
 description: Structured project planning with harness constraints and validation
+stability: static
 cognitive_mode: constructive-architect
 triggers:
   - manual
@@ -9,6 +10,8 @@ triggers:
 platforms:
   - claude-code
   - gemini-cli
+  - cursor
+  - codex
 tools:
   - Bash
   - Read
@@ -22,6 +25,12 @@ cli:
     - name: path
       description: Project root path
       required: false
+    - name: spec-path
+      description: Path to approved spec (from brainstorming output or orchestrator)
+      required: false
+    - name: session-slug
+      description: Session slug for scoped state/handoff (passed by autopilot)
+      required: false
     - name: fast
       description: Skip skeleton pass — produce full plan directly
       required: false

package/dist/agents/skills/cursor/harness-pre-commit-review/skill.yaml

@@ -1,8 +1,9 @@
 name: harness-pre-commit-review
 version: "1.0.0"
 description: Lightweight pre-commit quality gate combining mechanical checks and AI review
+stability: static
 triggers: [manual, on_commit]
-platforms: [claude-code, gemini-cli]
+platforms: [claude-code, gemini-cli, cursor, codex]
 tools: [Bash, Read, Glob, Grep]
 cli:
   command: harness skill run harness-pre-commit-review

package/dist/agents/skills/cursor/harness-product-spec/skill.yaml

@@ -1,6 +1,7 @@
 name: harness-product-spec
 version: "1.0.0"
 description: User story generation, EARS acceptance criteria, and PRD creation from issues
+stability: static
 cognitive_mode: constructive-architect
 triggers:
   - manual
@@ -8,6 +9,8 @@ triggers:
 platforms:
   - claude-code
   - gemini-cli
+  - cursor
+  - codex
 tools:
   - Bash
   - Read

package/dist/agents/skills/cursor/harness-property-test/skill.yaml

@@ -1,6 +1,7 @@
 name: harness-property-test
 version: "1.0.0"
 description: Property-based and generative testing with fast-check, hypothesis, and automatic shrinking
+stability: static
 cognitive_mode: constructive-architect
 triggers:
   - manual
@@ -8,6 +9,8 @@ triggers:
 platforms:
   - claude-code
   - gemini-cli
+  - cursor
+  - codex
 tools:
   - Bash
   - Read

package/dist/agents/skills/cursor/harness-refactoring/skill.yaml

@@ -1,6 +1,7 @@
 name: harness-refactoring
 version: "1.0.0"
 description: Safe refactoring with validation before and after changes
+stability: static
 cognitive_mode: meticulous-implementer
 triggers:
   - manual
@@ -8,6 +9,8 @@ triggers:
 platforms:
   - claude-code
   - gemini-cli
+  - cursor
+  - codex
 tools:
   - Bash
   - Read
@@ -32,6 +35,11 @@ state:
   persistent: false
   files: []
 depends_on: []
+related_skills:
+  - gof-strategy-pattern
+  - gof-adapter-pattern
+  - gof-facade-pattern
+  - gof-decorator-pattern
 addresses:
   - signal: high-complexity
     metric: cyclomaticComplexity

package/dist/agents/skills/cursor/harness-release-readiness/SKILL.md

@@ -46,6 +46,22 @@ Before running checks, look for existing state:
 
 3. If no state file exists, this is a fresh run. Proceed directly to checks.
 
+#### Project Type Detection
+
+Before running any checks, verify this is an npm project:
+
+1. Check whether `package.json` exists at the project root.
+2. If `package.json` does **not** exist, exit immediately with:
+
+   ```
+   This project does not appear to be an npm project (no package.json found).
+   /harness:release-readiness is npm-focused and cannot audit this project type.
+
+   For general project health, use: /harness:verification
+   ```
+
+3. If `package.json` exists, continue to Monorepo Detection.
+
 #### Monorepo Detection
 
 Detect whether the project is a monorepo:

package/dist/agents/skills/cursor/harness-release-readiness/skill.yaml

@@ -1,6 +1,7 @@
 name: harness-release-readiness
 version: "1.0.0"
 description: Audit npm release readiness, run maintenance checks, offer auto-fixes, track progress across sessions
+stability: static
 cognitive_mode: meticulous-verifier
 triggers:
   - manual
@@ -8,6 +9,8 @@ triggers:
 platforms:
   - claude-code
   - gemini-cli
+  - cursor
+  - codex
 tools:
   - Bash
   - Read

package/dist/agents/skills/cursor/harness-resilience/skill.yaml

@@ -1,6 +1,7 @@
 name: harness-resilience
 version: "1.0.0"
 description: Circuit breakers, rate limiting, bulkheads, retry patterns, and fault tolerance
+stability: static
 cognitive_mode: advisory-guide
 triggers:
   - manual
@@ -9,6 +10,8 @@ triggers:
 platforms:
   - claude-code
   - gemini-cli
+  - cursor
+  - codex
 tools:
   - Bash
   - Read
@@ -74,3 +77,8 @@ state:
   persistent: false
   files: []
 depends_on: []
+related_skills:
+  - resilience-circuit-breaker
+  - resilience-retry-pattern
+  - resilience-bulkhead-pattern
+  - resilience-fallback-pattern

package/dist/agents/skills/cursor/harness-roadmap/skill.yaml

@@ -1,12 +1,15 @@
 name: harness-roadmap
 version: "1.0.0"
 description: Create and manage a unified project roadmap from existing specs and plans
+stability: static
 cognitive_mode: constructive-architect
 triggers:
   - manual
 platforms:
   - claude-code
   - gemini-cli
+  - cursor
+  - codex
 tools:
   - Bash
   - Read

package/dist/agents/skills/cursor/harness-roadmap-pilot/skill.yaml

@@ -1,12 +1,15 @@
 name: harness-roadmap-pilot
 version: "1.0.0"
 description: AI-assisted selection of the next highest-impact roadmap item with scoring, assignment, and skill transition
+stability: static
 cognitive_mode: constructive-architect
 triggers:
   - manual
 platforms:
   - claude-code
   - gemini-cli
+  - cursor
+  - codex
 tools:
   - Bash
   - Read

package/dist/agents/skills/cursor/harness-router/SKILL.md

@@ -0,0 +1,154 @@
+# Harness Router
+
+> Natural language entry point to all harness skills. Classifies intent by scope/domain, confirms routing with reasoning, dispatches to the appropriate skill.
+
+## When to Use
+
+- When the user invokes `/harness` with a natural language description
+- When the user is unsure which harness skill to use
+- NOT when the user already knows the specific skill (e.g., `/harness:tdd`)
+- NOT for non-harness tasks (general coding, file operations, etc.)
+
+## Process
+
+### Iron Law
+
+**The router confirms before dispatching.** Never silently route. Always present the chosen skill, scope classification, and reasoning — then wait for confirmation.
+
+---
+
+### Phase 1: CLASSIFY — Parse Intent and Search
+
+1. **Check for empty input.** Show usage help and stop:
+
+   ```
+   Usage: /harness <describe what you want to do>
+   Examples:
+     /harness fix the button spacing on the settings page
+     /harness we need a notification system
+     /harness this page is slow
+     /harness redesign how the sidebar filters work
+     /harness clean up my code
+   I'll figure out the right skill and process level for you.
+   ```
+
+2. **Search the skill catalog.** Call `search_skills({ query: "<user's intent>" })` to get ranked matches.
+
+3. **Classify scope** into one of four tiers:
+
+   | Scope                | Signal Words                                       | Description                                |
+   | -------------------- | -------------------------------------------------- | ------------------------------------------ |
+   | **quick-fix**        | fix, tweak, adjust, update, change X to Y, correct | Small targeted change, no design decisions |
+   | **guided-change**    | redesign, refactor, improve, rework                | Moderate scope, clear architecture         |
+   | **full-exploration** | build, create, add system for, we need, design     | Ambiguous scope, design decisions needed   |
+   | **diagnostic**       | broken, slow, failing, debug, review, analyze      | Something broken or needs analysis         |
+
+   Additional signals: single file → lower ceremony; multiple systems → higher ceremony; error messages → diagnostic.
+
+4. **Map scope to entry skill:**
+
+   | Scope            | Primary Skill           | Alternates                                                        |
+   | ---------------- | ----------------------- | ----------------------------------------------------------------- |
+   | quick-fix        | `harness-tdd`           | `harness-refactoring` if structural                               |
+   | guided-change    | `harness-planning`      | `harness-architecture-advisor` if tradeoffs involved              |
+   | full-exploration | `harness-brainstorming` | —                                                                 |
+   | diagnostic       | `harness-debugging`     | `harness-code-review` for reviews, `harness-perf` for performance |
+
+   If `search_skills` results strongly favor a different skill, prefer search results. Scope classification is the fallback when search is ambiguous.
+
+5. **Assess confidence:**
+   - **High:** Top result clearly dominates and aligns with scope classification
+   - **Low:** Top 2-3 results close in score, or scope classification conflicts with search results
+
+---
+
+### Phase 2: CONFIRM — Present Decision with Reasoning
+
+**High confidence:**
+
+```
+This looks like a [scope-level] — [reasoning].
+I'll route to `harness:[skill]` because [why this skill fits].
+Proceed? (y / n / suggest another)
+```
+
+Wait for confirmation.
+
+**Low confidence (multiple candidates):**
+
+```
+This could be a few things:
+1. `harness:[skill-1]` — [description]
+2. `harness:[skill-2]` — [description]
+3. `harness:[skill-3]` — [description]
+Which fits best? (1 / 2 / 3)
+```
+
+Wait for the user to choose.
+
+**User rejects:** If they name a skill, confirm and dispatch. If they re-phrase, re-run CLASSIFY. Do not loop more than twice — after two misses, list all available skills and let the user pick.
+
+---
+
+### Phase 3: DISPATCH — Invoke Selected Skill
+
+1. **Pass original intent as context** so the user does not repeat themselves.
+2. **Invoke via `run_skill`:** `run_skill({ skill: "<selected-skill>", path: "<project-root>" })` with original intent as argument context.
+3. **Hand off cleanly.** Once invoked, the router's job is done. The dispatched skill owns all subsequent interaction.
+
+---
+
+## Examples
+
+**Quick Fix:** "fix the button spacing on the settings page"
+quick-fix — single component, clear target → `harness-tdd`
+
+**Guided Change:** "redesign how the sidebar filters work"
+guided-change — moderate scope, some decisions → `harness-planning` or `harness-architecture-advisor`
+
+**Full Exploration:** "we need a notification system"
+full-exploration — ambiguous scope, multiple approaches → `harness-brainstorming`
+
+**Diagnostic:** "this page is slow"
+diagnostic — performance symptom → `harness-perf`
+
+**Ambiguous:** "clean up my code"
+Could be refactoring, dead code, or architecture cleanup → Present candidates: `harness-refactoring`, `harness-codebase-cleanup`, `harness-cleanup-dead-code`
+
+## Harness Integration
+
+- **`search_skills`** — Phase 1: matches intent against the skill catalog. Returns ranked results.
+- **`run_skill`** — Phase 3: dispatches to selected skill with project path and original intent.
+- **`harness validate`** — Not used by the router. Validation is the dispatched skill's responsibility.
+
+## Success Criteria
+
+- Quick-fix intents route to `harness-tdd`, full-exploration to `harness-brainstorming`, diagnostics to appropriate diagnostic skill
+- Ambiguous intents present top 2-3 candidates for user choice
+- Confirmation always includes scope classification, chosen skill, and one-line reasoning
+- User can reject and re-phrase or pick a different skill
+- Dispatched skill receives original intent as context
+- `search_skills` MCP tool is used for matching — no custom scoring code
+- `/harness` with no arguments shows usage help
+
+## Rationalizations to Reject
+
+| Rationalization                                                           | Reality                                                                                                                                       |
+| ------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
+| "The intent is obvious, I can skip confirmation"                          | The Iron Law requires confirmation before every dispatch. Even obvious intents benefit from the user seeing scope classification.             |
+| "I should suggest downstream skills the dispatched skill will chain into" | Each skill owns its own transitions. Surfacing the full chain adds noise and duplicates logic in the dispatched skill.                        |
+| "Search results don't match well, so I'll guess based on keywords"        | If `search_skills` returns poor results, present top candidates and let the user choose. Guessing silently is worse than admitting ambiguity. |
+| "The user rejected twice, I should keep trying"                           | After two misses, list available skills and let the user pick directly. Do not loop indefinitely.                                             |
+
+## Gates
+
+- **No silent dispatch.** Every routing decision must be confirmed before the skill is invoked.
+- **No bypassing search_skills.** The skill catalog search must be used. Do not hardcode intent-to-skill mappings.
+- **No downstream chaining.** The router dispatches to exactly one skill. Do not pre-load or suggest follow-on skills.
+- **No more than two re-classification attempts.** After two rejections, show the full list.
+
+## Escalation
+
+- **`search_skills` returns no results:** Skills index may be stale. Suggest `harness update-skills-index` to regenerate, then retry.
+- **Intent spans multiple skills:** Ask: "This involves both [skill A] and [skill B]. Which should we start with?" Do not dispatch to multiple skills.
+- **Intent outside harness catalog:** Say so plainly: "This doesn't match any harness skill. Handle directly, or re-describe if you think a skill should apply."

package/dist/agents/skills/cursor/harness-router/skill.yaml

@@ -0,0 +1,47 @@
+name: harness-router
+version: "1.0.0"
+description: Natural language router to harness skills — classifies intent, confirms, dispatches
+stability: static
+cognitive_mode: analytical-classifier
+command_name: harness
+triggers:
+  - manual
+platforms:
+  - claude-code
+  - gemini-cli
+  - cursor
+  - codex
+tools:
+  - Read
+  - Glob
+  - Grep
+cli:
+  command: harness skill run harness-router
+  args:
+    - name: intent
+      description: Natural language description of what the user wants
+      required: true
+mcp:
+  tool: run_skill
+  input:
+    skill: harness-router
+    path: string
+type: rigid
+tier: 1
+phases:
+  - name: classify
+    description: Parse intent and search skills index for matches
+    required: true
+  - name: confirm
+    description: Present routing decision with scope and reasoning
+    required: true
+  - name: dispatch
+    description: Invoke selected skill via run_skill with original intent
+    required: true
+state:
+  persistent: false
+  files: []
+depends_on: []
+addresses:
+  - signal: high-complexity
+    weight: 0.3

package/dist/agents/skills/cursor/harness-secrets/SKILL.md

@@ -48,7 +48,7 @@
 
    CRITICAL (2):
      src/config/database.ts:8 -- Hardcoded PostgreSQL connection string with password
-     src/services/stripe.ts:3 -- Stripe secret key (sk_live_...)
+     src/services/stripe.ts:3 -- Stripe secret key (sk_example_...)
 
    HIGH (3):
      docker-compose.yml:15 -- MySQL root password in plaintext
@@ -135,7 +135,7 @@
 
    ```typescript
    // BEFORE (hardcoded)
-   const stripe = new Stripe('sk_live_abc123...');
+   const stripe = new Stripe('sk_example_abc123...');
 
    // AFTER (externalized)
    const stripe = new Stripe(process.env.STRIPE_SECRET_KEY!);
@@ -218,7 +218,7 @@ Phase 1: SCAN
   Scanned: 86 files
   Findings: 4
 
-  CRITICAL: src/payments/stripe.ts:5 -- sk_live_EXAMPLE_KEY_REDACTED_0000
+  CRITICAL: src/payments/stripe.ts:5 -- sk_example_EXAMPLE_KEY_REDACTED_0000
   HIGH: docker-compose.yml:22 -- POSTGRES_PASSWORD=supersecret
   MEDIUM: src/config/jwt.ts:3 -- JWT_SECRET = "my-jwt-secret-key"
   LOW: tests/fixtures/auth.ts:8 -- fake-api-key-for-testing (false positive)

package/dist/agents/skills/cursor/harness-secrets/skill.yaml

@@ -1,6 +1,7 @@
 name: harness-secrets
 version: "1.0.0"
 description: Vault integration, credential rotation, and environment variable hygiene
+stability: static
 cognitive_mode: meticulous-verifier
 tier: 3
 internal: false
@@ -31,6 +32,8 @@ triggers:
 platforms:
   - claude-code
   - gemini-cli
+  - cursor
+  - codex
 tools:
   - Bash
   - Read

package/dist/agents/skills/cursor/harness-security-review/skill.yaml

@@ -1,6 +1,7 @@
 name: harness-security-review
 version: "1.0.0"
 description: Deep security audit with OWASP baseline and stack-adaptive analysis
+stability: static
 cognitive_mode: meticulous-implementer
 triggers:
   - manual
@@ -8,6 +9,8 @@ triggers:
 platforms:
   - claude-code
   - gemini-cli
+  - cursor
+  - codex
 tools:
   - Bash
   - Read
@@ -74,3 +77,13 @@ stack_signals:
   - docker
   - api
 depends_on: []
+related_skills:
+  - owasp-auth-patterns
+  - owasp-injection-prevention
+  - owasp-xss-prevention
+  - owasp-security-headers
+  - security-threat-modeling-stride
+  - security-threat-modeling-process
+  - security-zero-trust-principles
+  - security-audit-log-design
+  - security-injection-families

package/dist/agents/skills/cursor/harness-security-scan/skill.yaml

@@ -1,6 +1,7 @@
 name: harness-security-scan
 version: "1.0.0"
 description: Lightweight mechanical security scan for health checks
+stability: static
 cognitive_mode: meticulous-implementer
 triggers:
   - manual
@@ -8,6 +9,8 @@ triggers:
 platforms:
   - claude-code
   - gemini-cli
+  - cursor
+  - codex
 tools:
   - Bash
   - Read
@@ -36,6 +39,12 @@ phases:
   - name: scan
     description: Run SecurityScanner and filter by severity threshold
     required: true
+related_skills:
+  - security-threat-modeling-stride
+  - security-threat-modeling-process
+  - security-zero-trust-principles
+  - security-audit-log-design
+  - security-injection-families
 state:
   persistent: false
   files: []

package/dist/agents/skills/cursor/harness-skill-authoring/SKILL.md

@@ -51,6 +51,116 @@
 
 3. **Key difference in SKILL.md:** Rigid skills require `## Gates` and `## Escalation` sections. Flexible skills may omit them (though they can include them if useful).
 
+### Phase 2B: CHOOSE TYPE — Knowledge Skills
+
+Knowledge skills encode domain reference material (design patterns, architectural guidance, best practices) as first-class skills. They are _not_ behavioral — they do not define process phases, require tools, or maintain state. Agents receive them as contextual guidance alongside behavioral skills.
+
+**Choose `type: knowledge` when:**
+
+- The skill encodes "know things" content, not "do things" process
+- The content is reference material an agent should _consult_ rather than _execute_
+- The skill maps cleanly to a technology vertical (e.g., React patterns, TypeScript generics, OWASP rules)
+- The skill's value is educational depth that benefits from progressive disclosure
+- NOT when the skill requires tools, phases, or state — those are rigid or flexible skills
+- NOT when the skill is a harness process skill (planning, execution, brainstorming)
+
+**Knowledge skill `skill.yaml` template:**
+
+```yaml
+name: <technology-prefix>-<pattern-name> # e.g., react-hooks-pattern, ts-generics-pattern
+version: '1.0.0'
+description: <one-line summary>
+cognitive_mode: advisory-guide # always advisory-guide for knowledge skills
+type: knowledge
+tier: 3
+triggers:
+  - manual
+platforms:
+  - claude-code
+  - gemini-cli
+  - cursor
+tools: [] # knowledge skills declare no tools
+paths:
+  - '**/*.tsx' # file-type-specific globs only — see rules below
+related_skills:
+  - <complementary-knowledge-skill> # other knowledge skills in the same vertical
+stack_signals:
+  - typescript
+  - react
+keywords:
+  - hooks
+  - custom-hooks
+metadata:
+  author: <author-name>
+  upstream: '<source-url>' # provenance tracking
+state:
+  persistent: false
+  files: []
+depends_on: []
+```
+
+**`paths` authoring rules (critical — read carefully):**
+
+The `paths` field is a list of minimatch glob patterns matched against the user's recent/changed files. A match boosts the skill's dispatch score by 0.20 (the paths scoring weight). Incorrect globs cause false activation.
+
+Rules:
+
+1. **Use file-type-specific globs only.** `**/*.tsx`, `**/*.vue`, `*.sql`, `Dockerfile` are correct. `**/*.ts` is incorrect — it activates for every TypeScript project regardless of context.
+2. **The lesson from Vue skills:** `**/*.ts` was initially added to Vue skills and had to be removed. TypeScript files exist in every project; Vue-specific content should only activate on `**/*.vue` files.
+3. **Config file patterns are safe.** `playwright.config.ts`, `prisma/schema.prisma`, `drizzle.config.ts` are sufficiently specific.
+4. **When in doubt, leave `paths: []`.** A skill with `paths: []` scores 0.0 on the paths dimension but can still surface via keyword and stack_signals matching.
+5. **Test your globs.** After adding paths, verify the skill surfaces when the target file is present and does NOT surface when an unrelated file is present (e.g., a Vue skill must not activate when only `.ts` files are present).
+
+**`related_skills` authoring rules:**
+
+The `related_skills` field lists skill names that complement the current skill. These are surfaced as secondary knowledge recommendations when the current skill is dispatched — this works for both knowledge skills (when auto-injected) and behavioral skills (when recommended).
+
+Rules:
+
+1. **Only reference skills that genuinely complement each other.** A React hooks skill relates to React compound pattern, not to OWASP security rules.
+2. **Reference by exact skill name** (directory name, e.g., `react-compound-pattern`, not `React Compound Pattern`).
+3. **Keep lists short (2–5 entries).** More than 5 related skills dilutes the signal.
+4. **Bidirectionality is not required** but is good practice — if skill A lists skill B, skill B should list skill A.
+
+**Knowledge skill `SKILL.md` structure:**
+
+Knowledge skills use a two-section disclosure model. The `## Instructions` section (~5K tokens max) is auto-injected into agent context on high-confidence matches. The `## Details` section is loaded on-demand for educational depth.
+
+```markdown
+# <Pattern Name>
+
+> <One-sentence description>
+
+## When to Use
+
+- [Specific activation conditions]
+- NOT when [boundary conditions]
+
+## Instructions
+
+[Agent-facing directives — concise, actionable, <5K tokens]
+[This section is auto-injected on high-confidence dispatch]
+
+## Details
+
+[Educational depth — patterns, examples, trade-offs]
+[This section is loaded on-demand when the agent explicitly requests it]
+
+## Source
+
+[Link to original source / upstream]
+```
+
+The `## Details` heading is the boundary marker. Everything before it is the Instructions section. The progressive disclosure split happens at `\n## Details`.
+
+**Schema constraints enforced automatically:**
+
+- `type: knowledge` → `phases` must be empty or omitted
+- `type: knowledge` → `tools` must be empty
+- `type: knowledge` → `state.persistent` must be false
+- `type: knowledge` → `cognitive_mode` defaults to `advisory-guide`
+- `type: knowledge` → `tier` defaults to 3
+
 ### Phase 3: WRITE SKILL.YAML — Define Metadata
 
 1. **Create the skill directory** under `agents/skills/<platform>/<skill-name>/`.
@@ -86,6 +196,12 @@ state:
     - <state-file-path> # List state files if persistent
 depends_on:
   - <prerequisite-skill> # Skills that must be available (not necessarily run first)
+# Optional fields (required for knowledge skills, optional for behavioral skills)
+paths: [] # File-type-specific glob patterns for dispatch boost
+related_skills: [] # Complementary skill names (surfaces related knowledge when dispatched)
+metadata: # Provenance and authorship metadata
+  author: <author>
+  upstream: '<source-url>'
 ```
 
 3. **Validate the YAML.** Ensure proper indentation, correct field names, and valid values. The `name` field must match the directory name exactly.
@@ -171,6 +287,8 @@ Evaluate every skill along two dimensions:
 - **Clear activation + vague implementation** = trap. The skill fires correctly but the agent has no concrete instructions, leading to inconsistent results.
 - **Ambiguous activation + specific implementation** = wasted. Great instructions that never get used because the agent does not know when to activate the skill.
 
+**Knowledge skills** follow the same quality matrix. "Clear activation" for a knowledge skill means `paths` globs and `stack_signals` are specific enough to surface the skill without false positives. "Specific implementation" means the `## Instructions` section is concise and actionable.
+
 Use this checklist as a final quality gate before declaring a skill complete.
 
 ## Harness Integration

package/dist/agents/skills/cursor/harness-skill-authoring/skill.yaml

@@ -1,12 +1,15 @@
 name: harness-skill-authoring
 version: "1.0.0"
 description: Create and maintain harness skills following the rich skill format
+stability: static
 cognitive_mode: constructive-architect
 triggers:
   - manual
 platforms:
   - claude-code
   - gemini-cli
+  - cursor
+  - codex
 tools:
   - Bash
   - Read