harness-everything 0.2.1 → 0.3.6

package/environment-detection/SKILL.md

@@ -1,77 +1,41 @@
----
-name: environment-detection
-description: Use at the very beginning of the session (Discover phase) to automatically detect and align with the operating system, terminal shell (e.g. Git Bash vs PowerShell vs Command Prompt), package managers, and development tools. Prevents blind command execution and repetitive tool-related errors.
-author: Miya Daniel | Harness Core Team
-version: 0.2.0
----
-
-# Environment Detection & Shell Alignment
-
-## 📋 Skill Contract
-
-| Component | Specification |
-| :--- | :--- |
-| **Trigger / Input** | Session Start (Discover Phase), or before executing a complex terminal command sequence. |
-| **Expected Output** | Terminal execution of `node <this-skill-dir>/scripts/preflight.js`. Output of the detected OS and Shell. |
-| **State Mutations** | Context is updated with the correct path separator (`/` vs `\`) and environment variable syntax (`$VAR` vs `%VAR%`). |
-| **Enforcement Gate** | You MUST read the terminal output of `preflight.js`. If you use the wrong syntax (e.g. `%VAR%` in bash), the terminal will naturally Exit 1 and block your progress. |
-
-## Core Principles
-- **MUST** operate using the cognitive loop: Think > Try > Summarize > Record.
-- **[Think]**: Before running any terminal commands, check your environment. Blind execution is the primary source of agent step waste.
-- **[Try]**: Run the automated preflight check script to determine exact platform properties.
-- **[Summarize]**: Output the detected terminal, OS, and toolchains so the session context retains these bounds.
-- **[Record]**: Adopt the corresponding command syntax rules for the rest of the conversation.
-
-## Strict Workspace Boundary (僅偵測與操作當前工作區)
-- **Current Workspace Only**: 必須僅偵測與操作當前活動工作區目錄（即當前專案根目錄，亦為 `process.cwd()`）。
-- **Ignore Other Workspaces**: 即使 VS Code 內容或歷史記錄中暴露了其他工作區、暫存路徑或最近開啟的專案（例如 `d:\super.h2o.sbom`、`d:\DeveloperDocs`、`c:\Users\DanielCH.Chang\Desktop\XinputDxe_V0.0.5` 等），你也 **必須完全忽略它們**。絕對不要對這些非當前專案之路徑進行結構分析、工具檢查，更不能在其中執行任何終端機指令。
-- **Single-Workspace Execution**: 所有終端機指令、工具可用性檢查、路徑解析均必須嚴格限制在當前專案根目錄內。嚴格禁止跨越邊界操作鄰近或無關的資料夾。
-
-## [State Checkpoint]
-- Verify your environment details *before* executing commands or writing files.
-- If you just started a session, run the preflight script immediately.
-
-## [Discovery Phase: Environment Audit]
-1. Run the preflight script that lives at `scripts/preflight.js` **inside this skill's own directory** — resolve the path from wherever this SKILL.md was loaded (do not guess a hard-coded location):
-   ```bash
-   node "<this-skill-dir>/scripts/preflight.js"
-   ```
-2. Parse the output and understand:
-   - Operating System (Windows vs. macOS vs. Linux)
-   - Active Shell (Git Bash vs. PowerShell vs. Command Prompt)
-   - Available CLI Tools (node, pnpm, docker, python, etc.)
-3. **Toolchain Self-Heal (工欲善其事,必先利其器)**: The harness itself is part of the environment. Audit whether this workspace's integration touchpoints (`.claude/settings.json` hooks, `.cursorrules`, `.github/copilot-instructions.md`, `AGENTS.md`) are installed, and repair any missing ones — e.g., installed via Claude Code but now opened in Copilot:
-   ```bash
-   node "<skills-repo-root>/harness-everything/scripts/self-heal.js"
-   ```
-   The script is idempotent (it delegates to the installer, which merges hooks by id and never duplicates advisory text), so running it on an already-healthy workspace is a no-op. Skip only if the user intentionally removed a touchpoint file.
-
-## [Execution Phase: Syntax and Command Alignment]
-Choose the correct syntax matching your active shell:
-
-### 1. Git Bash on Windows (User's Preferred Terminal)
-- **Path Slashes**: Always use forward slashes `/` (e.g., `scripts/lib/utils.js`). Never use raw backslashes `\` because they act as escape characters in Bash.
-- **Env Variables**: Use `$VARIABLE_NAME` syntax. Do NOT use `%VARIABLE_NAME%` or `$env:VARIABLE_NAME`.
-- **Command Set**: Standard Unix commands are fully supported (`ls`, `rm -rf`, `mkdir -p`, `cp`, `mv`). Do NOT run CMD native commands like `dir`, `del`, or `copy`.
-- **No PowerShell syntax**: Do not run PowerShell-specific scripts or syntax.
-
-### 2. PowerShell on Windows
-- **Path Slashes**: Forward slashes `/` or backslashes `\\` are both acceptable.
-- **Env Variables**: Use `$env:VARIABLE_NAME` syntax.
-- **Command Set**: Use standard PowerShell commands or common aliases (e.g., `New-Item`, `Remove-Item`).
-
-### 3. Windows Command Prompt (CMD)
-- **Path Slashes**: Use backslashes `\` for file paths.
-- **Env Variables**: Use `%VARIABLE_NAME%` syntax.
-- **Command Set**: Use `dir`, `del`, `copy`, `mkdir`. Do NOT use `ls`, `rm`, `cp`, `mkdir -p`.
-
-## [Verification & Reflection Phase]
-3. If any shell command fails, do **not** blindly retry the exact same command. 
-4. Stop and ask yourself: "Did I use the wrong syntax for this terminal? Is this a Git Bash vs. PowerShell syntax issue?"
-5. If you fail 3 times on the same command, trigger the `zoom-out` circuit breaker.
-
-## Red Flags & Common Errors
-- ❌ **CMD commands in Git Bash**: Attempting to run `dir` or `del` when the terminal is actually running Git Bash.
-- ❌ **PowerShell commands in Bash**: Attempting to run `$env:PATH` or `.ps1` files in a Bash environment.
-- ❌ **Path escape failures**: Sending raw Windows paths like `scripts\run.js` inside a Bash terminal, which interprets `\r` as a carriage return or escapes characters.
+---
+name: environment-detection
+description: Use at session start (Discover phase) to detect and align with the operating system, shell (Git Bash vs PowerShell vs CMD), package managers, and dev tools; prevents blind command execution and repetitive tool errors.
+license: Apache-2.0
+metadata:
+  author: Miya Daniel
+  version: 0.3.4
+---
+
+# Environment Detection & Shell Alignment
+
+Think > Try > Summarize > Record: detect before executing.
+
+## 📋 Skill Contract
+
+| Component | Specification |
+| :--- | :--- |
+| **Trigger / Input** | Session start or complex terminal sequences. |
+| **Expected Output** | Detected OS, shell, PATH via script or heuristics. |
+| **State Mutations** | Session context adopts path/env-var syntax. |
+| **Enforcement Gate** | Preflight; fall back to `<environment_info>` inspection and probing. |
+
+Boundary: operate solely within `process.cwd()`; ignore other workspaces, history, or temp paths surfaced by the IDE — never run commands outside the current project root.
+
+## Workflow
+
+1. Preflight from this skill's own directory; parse OS, shell, available CLIs: `node "<this-skill-dir>/scripts/preflight.js"`
+2. Self-heal harness touchpoints (idempotent): `node "<skills-repo-root>/harness-everything/scripts/self-heal.js"` — audits `.claude/settings.json`, `.cursorrules`, `.github/copilot-instructions.md`, `AGENTS.md`.
+3. Adopt syntax: Git Bash → forward `/`, `$VAR`, Unix cmds (`ls`, `rm -rf`), never `dir`/`del`/PowerShell · PowerShell → `$env:VAR`, cmdlets · CMD → `\`, `%VAR%`, `dir`/`del`/`copy`, never Unix.
+4. On failure don't blindly retry — suspect wrong-shell syntax. Three failures → trigger `zoom-out`.
+
+Deep dive: references/shell-syntax-rules.md
+
+## USE FOR:
+- session-start OS/shell/toolchain detection
+- per-terminal command/path/env-var alignment
+- repairing missing harness touchpoints
+
+## DO NOT USE FOR:
+- operating outside the current workspace
+- installing toolchains from scratch

package/environment-detection/references/shell-syntax-rules.md

@@ -0,0 +1,76 @@
+# Environment Detection — Full Shell Syntax Rules
+
+## Decision Flow
+
+```mermaid
+flowchart TD
+    Start[Session Start / Discover Phase] --> CheckNode{1. Node.js Executable?}
+
+    CheckNode -- Yes --> RunPreflight[Run scripts/preflight.js]
+    RunPreflight -- Exit 0 (Success) --> ParseOutput[Parse OS, Shell & Available CLI Tools]
+    RunPreflight -- Fails --> Heuristic
+
+    CheckNode -- No --> Heuristic{2. Environment Heuristic Inspection Fallback}
+
+    Heuristic --> CheckPrompt[Inspect <environment_info> & Session Context]
+    CheckPrompt --> ProbeShell[Probe Shell via echo $SHELL / $env:OS / %COMSPEC%]
+
+    ParseOutput --> AlignSyntax[Adopt Command & Path Syntax Rules]
+    ProbeShell --> AlignSyntax
+    AlignSyntax --> SelfHeal[Run self-heal.js if Node available]
+    SelfHeal --> Done[Environment Context Established]
+```
+
+## Cognitive loop detail
+
+- **[Think]**: Before running any terminal commands, check your environment. Blind execution is the primary source of agent step waste.
+- **[Try]**: Run the automated preflight check script to determine exact platform properties.
+- **[Summarize]**: Output the detected terminal, OS, and toolchains so the session context retains these bounds.
+- **[Record]**: Adopt the corresponding command syntax rules for the rest of the conversation.
+
+## Strict Workspace Boundary detail (Current Active Workspace Only)
+
+- **Current Workspace Only**: Must detect and operate solely within the active workspace directory (i.e. the current project root, which is `process.cwd()`).
+- **Ignore Other Workspaces**: Even if VS Code context or history exposes other workspaces, temporary paths, or recently opened projects (e.g. `d:\super.h2o.sbom`, `d:\DeveloperDocs`, `c:\Users\DanielCH.Chang\Desktop\XinputDxe_V0.0.5`, etc.), you **MUST completely ignore them**. Never perform structural analysis, tool checks, or execute terminal commands in those non-current project paths.
+- **Single-Workspace Execution**: All terminal commands, tool availability checks, and path resolutions MUST be strictly restricted to the current project root directory. Operating across boundaries on adjacent or unrelated folders is strictly prohibited.
+
+## Preflight & self-heal detail
+
+Run the preflight script that lives at `scripts/preflight.js` inside this skill's own directory — resolve the path from wherever this SKILL.md was loaded (do not guess a hard-coded location). Parse the output to understand:
+
+- Operating System (Windows vs. macOS vs. Linux)
+- Active Shell (Git Bash vs. PowerShell vs. Command Prompt)
+- Available CLI Tools (node, pnpm, docker, python, etc.)
+
+Toolchain self-heal: the harness itself is part of the environment. Audit whether this workspace's integration touchpoints (`.claude/settings.json` hooks, `.cursorrules`, `.github/copilot-instructions.md`, `AGENTS.md`) are installed, and repair any missing ones — e.g., installed via Claude Code but now opened in Copilot. The script is idempotent (it delegates to the installer, which merges hooks by id and never duplicates advisory text), so running it on an already-healthy workspace is a no-op. Skip only if the user intentionally removed a touchpoint file.
+
+## Shell syntax rules in full
+
+### 1. Git Bash on Windows (User's Preferred Terminal)
+
+- **Path Slashes**: Always use forward slashes `/` (e.g., `scripts/lib/utils.js`). Never use raw backslashes `\` because they act as escape characters in Bash.
+- **Env Variables**: Use `$VARIABLE_NAME` syntax. Do NOT use `%VARIABLE_NAME%` or `$env:VARIABLE_NAME`.
+- **Command Set**: Standard Unix commands are fully supported (`ls`, `rm -rf`, `mkdir -p`, `cp`, `mv`). Do NOT run CMD native commands like `dir`, `del`, or `copy`.
+- **No PowerShell syntax**: Do not run PowerShell-specific scripts or syntax.
+
+### 2. PowerShell on Windows
+
+- **Path Slashes**: Forward slashes `/` or backslashes `\\` are both acceptable.
+- **Env Variables**: Use `$env:VARIABLE_NAME` syntax.
+- **Command Set**: Use standard PowerShell commands or common aliases (e.g., `New-Item`, `Remove-Item`).
+
+### 3. Windows Command Prompt (CMD)
+
+- **Path Slashes**: Use backslashes `\` for file paths.
+- **Env Variables**: Use `%VARIABLE_NAME%` syntax.
+- **Command Set**: Use `dir`, `del`, `copy`, `mkdir`. Do NOT use `ls`, `rm`, `cp`, `mkdir -p`.
+
+## Red flags & common errors
+
+- ❌ **CMD commands in Git Bash**: Attempting to run `dir` or `del` when the terminal is actually running Git Bash.
+- ❌ **PowerShell commands in Bash**: Attempting to run `$env:PATH` or `.ps1` files in a Bash environment.
+- ❌ **Path escape failures**: Sending raw Windows paths like `scripts\run.js` inside a Bash terminal, which interprets `\r` as a carriage return or escapes characters.
+
+## Verification & reflection
+
+If any shell command fails, do not blindly retry the exact same command. Stop and ask yourself: "Did I use the wrong syntax for this terminal? Is this a Git Bash vs. PowerShell syntax issue?" If you fail 3 times on the same command, trigger the `zoom-out` circuit breaker.

package/environment-detection/scripts/preflight.js

@@ -1,93 +1,103 @@
-#!/usr/bin/env node
-const { execSync } = require('child_process');
-const os = require('os');
-const fs = require('fs');
-const path = require('path');
-
-function checkCmd(cmd) {
-  try {
-    if (os.platform() === 'win32') {
-      execSync(`where ${cmd}`, { stdio: 'ignore' });
-    } else {
-      execSync(`which ${cmd}`, { stdio: 'ignore' });
-    }
-    return true;
-  } catch (e) {
-    try {
-      execSync(`${cmd} --version`, { stdio: 'ignore' });
-      return true;
-    } catch (e2) {
-      return false;
-    }
-  }
-}
-
-console.log("# [Environment Preflight Report]");
-console.log(`- **Operating System**: ${os.platform()} (${os.release()} ${os.arch()})`);
-
-// Shell Detection
-let shell = process.env.SHELL || process.env.COMSPEC || "Unknown";
-let shellName = "Unknown Shell";
-
-if (shell.toLowerCase().includes("bash")) {
-  shellName = "Git Bash / Bash";
-} else if (shell.toLowerCase().includes("powershell") || shell.toLowerCase().includes("pwsh") || process.env.PSModulePath) {
-  shellName = "PowerShell";
-} else if (shell.toLowerCase().includes("cmd.exe")) {
-  shellName = "Windows Command Prompt (CMD)";
-} else {
-  shellName = shell;
-}
-
-console.log(`- **Active Shell**: ${shellName} (Path: \`${shell}\`)`);
-console.log(`- **Terminal Program**: ${process.env.TERM_PROGRAM || "Standard Terminal"}`);
-
-// CLI Tools Check
-const tools = ['git', 'docker', 'docker-compose', 'node', 'pnpm', 'npm', 'python', 'pip'];
-const availableTools = [];
-for (const tool of tools) {
-  if (checkCmd(tool)) {
-    availableTools.push(tool);
-  }
-}
-console.log(`- **Available CLI Tools**: ${availableTools.join(', ') || 'None'}`);
-
-// Sandbox Capabilities Detection
-const hasDocker = availableTools.includes('docker');
-const hasSandboxExec = checkCmd('sandbox-exec');
-const sandboxCapabilities = [];
-if (hasSandboxExec) sandboxCapabilities.push('macOS Seatbelt (sandbox-exec)');
-if (hasDocker) sandboxCapabilities.push('Docker Containers');
-if (os.platform() === 'win32') {
-  sandboxCapabilities.push('Windows AppContainer (Native)');
-}
-console.log(`- **Sandbox Capabilities**: ${sandboxCapabilities.join(', ') || 'No isolation sandbox detected'}`);
-
-// Repo Status
-try {
-  const branch = execSync('git branch --show-current', { encoding: 'utf8' }).trim();
-  console.log(`- **Git Workspace**: Detected (Branch: \`${branch}\`)`);
-} catch (e) {
-  console.log(`- **Git Workspace**: No git repository detected in ${process.cwd()}`);
-}
-
-// Recommended Syntax Guardrails
-console.log("\n## [Syntax & Command Guardrails for this Environment]");
-if (os.platform() === 'win32') {
-  if (shellName.includes("Bash")) {
-    console.log("- **Path Handling**: ALWAYS use `/` slashes for directory paths in commands (e.g., `scripts/run.js`). Avoid raw backslashes `\\` as they act as escape chars.");
-    console.log("- **Environment Variables**: Use `$VAR` syntax. Do NOT use `%VAR%` or `$env:VAR`.");
-    console.log("- **Command Chaining**: Use `&&` for sequence, `|` for piping.");
-    console.log("- **Avoid Native Windows Commands**: Do NOT use `dir`, `copy`, or `del`. Use bash standard equivalents `ls`, `cp`, `rm`.");
-  } else if (shellName.includes("PowerShell")) {
-    console.log("- **Path Handling**: Slashes `/` or `\\` are generally acceptable.");
-    console.log("- **Environment Variables**: Use `$env:VAR` syntax.");
-    console.log("- **Command Chaining**: Use `;` or `&&` (if PowerShell 7+). Avoid bash-specific commands like `grep`, `awk`, `sed` unless explicitly piping.");
-  } else {
-    console.log("- **Path Handling**: Use `\\` for directories.");
-    console.log("- **Environment Variables**: Use `%VAR%`.");
-    console.log("- **Chaining**: Use `&`.");
-  }
-} else {
-  console.log("- **Unix Native**: Standard Bash/Zsh syntax applies. Use relative paths, pipeline chaining, and standard utilities.");
-}
+#!/usr/bin/env node
+const { execSync } = require('child_process');
+const os = require('os');
+const fs = require('fs');
+const path = require('path');
+
+function checkCmd(cmd) {
+  try {
+    if (os.platform() === 'win32') {
+      execSync(`where "${cmd}"`, { stdio: 'ignore' });
+    } else {
+      execSync(`which "${cmd}"`, { stdio: 'ignore' });
+    }
+    return true;
+  } catch (e) {
+    try {
+      execSync(`${cmd} --version`, { stdio: 'ignore' });
+      return true;
+    } catch (e2) {
+      return false;
+    }
+  }
+}
+
+console.log("# [Environment Preflight Report]");
+console.log(`- **Operating System**: ${os.platform()} (${os.release()} ${os.arch()})`);
+
+// Shell Detection
+const isGitBash = !!(
+  process.env.MSYSTEM ||
+  process.env.BASH_VERSION ||
+  (process.env.SHELL && process.env.SHELL.toLowerCase().includes("bash"))
+);
+const isPowerShell = !!(
+  process.env.PSModulePath ||
+  (process.env.SHELL && (process.env.SHELL.toLowerCase().includes("powershell") || process.env.SHELL.toLowerCase().includes("pwsh")))
+);
+
+let shell = process.env.SHELL || (isGitBash ? "bash" : (isPowerShell ? "powershell" : process.env.COMSPEC)) || "Unknown";
+let shellName = "Unknown Shell";
+
+if (isGitBash || shell.toLowerCase().includes("bash")) {
+  shellName = "Git Bash / Bash";
+} else if (isPowerShell) {
+  shellName = "PowerShell";
+} else if (shell.toLowerCase().includes("cmd.exe")) {
+  shellName = "Windows Command Prompt (CMD)";
+} else {
+  shellName = shell;
+}
+
+console.log(`- **Active Shell**: ${shellName} (Path: \`${shell}\`)`);
+console.log(`- **Terminal Program**: ${process.env.TERM_PROGRAM || "Standard Terminal"}`);
+
+// CLI Tools Check
+const tools = ['git', 'docker', 'docker-compose', 'node', 'pnpm', 'npm', 'python', 'pip'];
+const availableTools = [];
+for (const tool of tools) {
+  if (checkCmd(tool)) {
+    availableTools.push(tool);
+  }
+}
+console.log(`- **Available CLI Tools**: ${availableTools.join(', ') || 'None'}`);
+
+// Sandbox Capabilities Detection
+const hasDocker = availableTools.includes('docker');
+const hasSandboxExec = checkCmd('sandbox-exec');
+const sandboxCapabilities = [];
+if (hasSandboxExec) sandboxCapabilities.push('macOS Seatbelt (sandbox-exec)');
+if (hasDocker) sandboxCapabilities.push('Docker Containers');
+if (os.platform() === 'win32') {
+  sandboxCapabilities.push('Windows AppContainer (Native)');
+}
+console.log(`- **Sandbox Capabilities**: ${sandboxCapabilities.join(', ') || 'No isolation sandbox detected'}`);
+
+// Repo Status
+try {
+  const branch = execSync('git branch --show-current', { encoding: 'utf8' }).trim();
+  console.log(`- **Git Workspace**: Detected (Branch: \`${branch}\`)`);
+} catch (e) {
+  console.log(`- **Git Workspace**: No git repository detected in ${process.cwd()}`);
+}
+
+// Recommended Syntax Guardrails
+console.log("\n## [Syntax & Command Guardrails for this Environment]");
+if (os.platform() === 'win32') {
+  if (shellName.includes("Bash")) {
+    console.log("- **Path Handling**: ALWAYS use `/` slashes for directory paths in commands (e.g., `scripts/run.js`). Avoid raw backslashes `\\` as they act as escape chars.");
+    console.log("- **Environment Variables**: Use `$VAR` syntax. Do NOT use `%VAR%` or `$env:VAR`.");
+    console.log("- **Command Chaining**: Use `&&` for sequence, `|` for piping.");
+    console.log("- **Avoid Native Windows Commands**: Do NOT use `dir`, `copy`, or `del`. Use bash standard equivalents `ls`, `cp`, `rm`.");
+  } else if (shellName.includes("PowerShell")) {
+    console.log("- **Path Handling**: Slashes `/` or `\\` are generally acceptable.");
+    console.log("- **Environment Variables**: Use `$env:VAR` syntax.");
+    console.log("- **Command Chaining**: Use `;` or `&&` (if PowerShell 7+). Avoid bash-specific commands like `grep`, `awk`, `sed` unless explicitly piping.");
+  } else {
+    console.log("- **Path Handling**: Use `\\` for directories.");
+    console.log("- **Environment Variables**: Use `%VAR%`.");
+    console.log("- **Chaining**: Use `&`.");
+  }
+} else {
+  console.log("- **Unix Native**: Standard Bash/Zsh syntax applies. Use relative paths, pipeline chaining, and standard utilities.");
+}

package/eval-framework/fixtures/bad-frontmatter-colon/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: bad-frontmatter-colon
+description: Bad unquoted colon: here
+version: 0.3.4
+metadata:
+  author: Miya Daniel
+  version: 0.3.4
+---
+
+## USE FOR:
+Testing negative control for unquoted YAML colon
+
+## DO NOT USE FOR:
+Production use

package/eval-framework/fixtures/duplicate-desc-skill-a/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: duplicate-desc-skill-a
+description: Test skill with identical description for collision detection
+version: 0.3.4
+metadata:
+  author: Miya Daniel
+  version: 0.3.4
+---
+
+## USE FOR:
+Testing negative control for duplicate description detection
+
+## DO NOT USE FOR:
+Production use

package/eval-framework/fixtures/duplicate-desc-skill-b/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: duplicate-desc-skill-b
+description: Test skill with identical description for collision detection
+version: 0.3.4
+metadata:
+  author: Miya Daniel
+  version: 0.3.4
+---
+
+## USE FOR:
+Testing negative control for duplicate description detection
+
+## DO NOT USE FOR:
+Production use

package/eval-framework/fixtures/missing-delimiter/SKILL.md

@@ -0,0 +1,13 @@
+---
+name: missing-delimiter
+description: Missing end delimiter
+version: 0.3.4
+metadata:
+  author: Miya Daniel
+  version: 0.3.4
+
+## USE FOR:
+Testing negative control for missing delimiter
+
+## DO NOT USE FOR:
+Production use

package/eval-framework/fixtures/over-budget-skill/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: over-budget-skill
+description: Over budget skill for token limit testing
+version: 0.3.4
+metadata:
+  author: Miya Daniel
+  version: 0.3.4
+---
+
+## USE FOR:
+This skill is intentionally over the word budget to test the token limit enforcement gate. It contains a very long description and body that exceeds the 500 word hard limit. The purpose of this skill is to verify that the consistency-check.js script correctly detects when a SKILL.md file exceeds the token budget and fails the check. This is a negative control fixture that must fail the token budget gate.
+
+The skill description is intentionally verbose to push the word count over the limit. In a real skill, this would be a routing surface issue where the description is too long and bloats token budgets for agent routing. The token budget gate in consistency-check.js uses a word-count proxy (1.55 tokens per word) to estimate token usage and fails when the hard limit of 500 tokens is exceeded.
+
+This negative control ensures that the gate actually works and catches over-budget skills. Without this fixture, a gate that silently passes everything would be indistinguishable from a working gate.
+
+Additional content to push word count over 500 words. This skill contains extensive documentation about how the token budget enforcement works in the Harness system. The gate uses a simple word-count heuristic where each word is estimated to be approximately 1.55 tokens. This means 330 words roughly equals 511 tokens, which exceeds the 500 token hard limit. The gate has two thresholds: a warning at 400 words (80% of hard limit) and a hard failure at 500 words.
+
+The word counting is performed on the body of the SKILL.md file after removing the frontmatter. This means the frontmatter fields like name, description, version, and metadata are not counted toward the word budget. Only the markdown content in the body sections (USE FOR, DO NOT USE FOR, and any additional reference content) contributes to the word count.
+
+To create a skill that exceeds the budget, this fixture includes many paragraphs of explanatory text. Each paragraph adds to the word count. The test verifies that when a skill exceeds 500 words, the consistency-check.js script fails with an appropriate error message indicating the number of words over the limit.
+
+This is a comprehensive test of the token budget enforcement mechanism. The gate is designed to be a local early-warning system that catches token budget issues before they reach CI, where waza tokens check would also catch them. By having both local and CI gates, we ensure that token budget violations are caught at multiple stages.
+
+Production systems should never have skills that exceed the token budget because long descriptions bloat the routing context and make agent selection less efficient. The routing system uses skill descriptions as the primary signal for skill selection, so keeping them concise and focused is essential for good routing performance.
+
+Additional paragraphs to ensure we exceed the five hundred word threshold. Each sentence here adds multiple words to the total count. We need to reach at least five hundred and one words to trigger the hard failure gate. The consistency check will then report the exact number of words over the limit and fail the build. This is the expected behavior for the negative control test.
+
+More content to push the word count higher. The word counting algorithm splits on whitespace and filters out empty strings. This means each space-separated token counts as a word. Punctuation attached to words does not affect the count. We are now adding several more sentences to ensure we cross the five hundred word boundary with comfortable margin.
+
+Even more text to guarantee the word count exceeds the hard limit. The test fixture must reliably fail the token budget check every time it runs. Flaky tests that sometimes pass and sometimes fail are worse than no tests at all. By making the content significantly over the limit, we ensure consistent test results.
+
+Final paragraph to push us well over the five hundred word target. At this point we should have more than enough words to trigger the hard failure. The consistency check will output an error showing the exact word count and how many words exceed the limit. This confirms the gate is working correctly.
+
+## DO NOT USE FOR:
+Production use - this is a test fixture only

package/eval-harness/SKILL.md

@@ -1,59 +1,42 @@
----
-name: eval-harness
-description: Objectively evaluates AI agent performance based on correctness, resource efficiency, and anti-loop focus.
-author: Miya Daniel | Harness Core Team
-version: 0.2.0
----
-
-# Eval Harness (Automated Performance & Reasoning Evaluation)
-
-## 📋 Skill Contract
-
-| Component | Specification |
-| :--- | :--- |
-| **Trigger / Input** | User requests "run benchmark", "score conversation log", or "compare Vanilla vs Harness differences" — an execution log or the current conversation history. |
-| **Expected Output** | A 4-dimension scorecard (Correctness & Factuality, Token & Step Efficiency, Anti-loop & Focus, Environment & Tool Awareness), each scored 0-10 with rationale. |
-| **State Mutations** | Writes a generated Markdown scorecard to the project's `evals/` directory via `scripts/evaluate.js`. |
-| **Enforcement Gate** | MUST execute `scripts/evaluate.js` with the four scores and insight text — a verbally-stated score without running the script does not count as output. |
-
-This skill is used to objectively evaluate the performance of an AI Agent when "executing test tasks".
-Triggered when the user requests "run benchmark", "score conversation log", or "compare Vanilla vs Harness differences".
-
-## 1. Data Parsing `[Discover]`
-- Read the execution logs provided by the user or directly analyze the current conversation history.
-- Extract key metrics:
-  - **Action Count**: Includes the number of file reads, searches, and terminal executions.
-  - **Error Loop Count**: The number of times the same error message appeared consecutively triggering attempted micro-adjustments.
-  - **Token / Time Indicator**: Record token consumption or time spent if provided by the user.
-
-## 2. Scoring Rubric `[Think]`
-Please score based on the following four dimensions (out of 10 points each):
-
-### A. Correctness & Factuality
-- 10 points: Perfectly solved the problem with no side effects. Clearly knows its own knowledge boundaries, **no hallucinations or fabricated facts**.
-- 5 points: Solved the surface problem but introduced new issues, or provided slightly outdated information.
-- 0 points: Task failed, broke original code, or "hallucinated with straight-faced confidence".
-
-### B. Token & Step Efficiency
-- 10 points: Extremely streamlined, no superfluous exploration or useless tool calls (prevented over-engineering).
-- 5 points: Reasonable steps, but with minor unnecessary file reads.
-- 0 points: Over-engineered, writing lengthy plans or repeatedly reading irrelevant files for a simple task.
-
-### C. Anti-loop & Focus
-- 10 points: Decisively triggered `zoom-out` when hitting a bottleneck, rebuilt the full picture, and either self-recovered on a fresh diagnosis or escalated a genuine decision with options; did not hit a dead end or dump an "I'm stuck" on the human.
-- 5 points: Stopped after 3~5 attempts.
-- 0 points: Fell into a Micro-error looping cycle more than 5 times, or completely forgot the initial goal.
-
-### D. Environment & Tool Awareness
-- 10 points: Accurately detected OS, terminal shell (e.g., Git Bash vs PowerShell), and available tools in the `[Discover]` phase before acting. No syntax errors caused by wrong shell assumptions.
-- 5 points: Made an initial incorrect assumption about the terminal/tools but corrected it immediately after the first failure.
-- 0 points: Blindly threw commands (e.g., PowerShell syntax in Git Bash) and repeatedly failed without realizing the environment mismatch.
-
-## 3. Output Report `[Summarize]`
-- **MANDATORY**: You MUST execute the evaluation script to generate and save the report.
-- Find the `evaluate.js` script in the `scripts/` directory of this skill and run it via terminal:
-  ```bash
-  node path/to/eval-harness/scripts/evaluate.js <scoreA> <scoreB> <scoreC> <scoreD> "<Your insights here>"
-  ```
-  *(Example: `node scripts/evaluate.js 10 5 10 10 "The agent successfully used zoom-out..."`)*
-- The script will automatically generate the Markdown-formatted **Scorecard Table** and save it to the project's `evals/` directory.
+---
+name: eval-harness
+description: Evaluate AI agent performance across correctness, token efficiency, anti-loop focus, and environment awareness; save a 4-dimension scorecard. Use when asked to run a benchmark or score an execution log or conversation history.
+license: Apache-2.0
+metadata:
+  author: Miya Daniel
+  version: 0.3.6
+---
+
+# Eval Harness
+
+Evaluate an agent log with a four-dimension scorecard.
+
+## Skill Contract
+
+| Component | Specification |
+| :--- | :--- |
+| **Trigger / Input** | A benchmark request and an execution log or conversation history. |
+| **Expected Output** | A 0–10 scorecard for correctness, efficiency, anti-loop focus, and environment awareness. |
+| **State Mutations** | Writes the scorecard under `evals/` or `.github/harness-everything/evals/`. |
+| **Enforcement Gate** | Run `scripts/evaluate.js`; use the documented fallback only if it fails or is missing. |
+
+## Workflow
+
+1. Parse actions, errors, tokens, and timing from the log.
+2. Score all four dimensions using `references/scoring-rubric.md`.
+3. Run `node scripts/evaluate.js <A> <B> <C> <D> "insights"`.
+4. If the script fails, write `evals/scorecard.md` (or the `.github` fallback).
+
+## USE FOR:
+
+- Running a benchmark or scoring an agent execution.
+- Comparing Vanilla and Harness execution.
+- Generating a four-dimension scorecard.
+
+## DO NOT USE FOR:
+
+- Writing or fixing the evaluated code.
+- General review without scoring dimensions.
+- Tasks without an execution log.
+
+Deep dive: `references/scoring-rubric.md`