Automated summary
Runs a harness test for an everything-evenhub skill by dispatching an implementer subagent guided by the skill, then a verifier subagent equipped with a structured checklist.
Strengths
- Cleanly separates implementation from verification through two distinct subagents
- Forces the verifier to read the actual files and re-run tsc/build instead of trusting the implementer's report
- Distinguishes implementation tests from audit tests (cross-check, sdk-ground-truth), which skip steps 3-4
- Produces a per-checklist-item PASS/FAIL score with suggestions for improving the skill
Limitations
- Tightly coupled to the everything-evenhub repo: paths, valid skill list and checklists are hardcoded
- Depends on specific subagent types (general-purpose, superpowers:code-reviewer), so it is not portable as-is
- Verdict quality depends entirely on the case and checklist files, which are not included in the SKILL.md
Use it when you need a reproducible check that an everything-evenhub skill actually produces the expected output.
Do not use it to test a skill from another repository or without the matching harness/cases and harness/checklists files.
Security analysis
CautionThe skill orchestrates file reads/writes, directory creation, build commands (npx tsc, npm run build), and subagent dispatch — all legitimate for a test harness and operating on repo-relative paths. There is meaningful execution surface (subagents following arbitrary skill content, recursive copy), but nothing destructive, exfiltrating, or hidden, so it warrants caution rather than a risky rating.
- •Uses Bash for mkdir/cp/npx/npm operations and dispatches subagents (general-purpose, sonnet) that execute arbitrary skill instructions — powerful but scoped to the repo
- •`cp -r harness/.output/quickstart/demo-glasses/ ...` could overwrite existing files in target dir if present
- •No destructive commands (rm -rf), no curl|sh piping, no secrets/token exfiltration, no obfuscated payloads, no safety-disabling instructions
Examples
/harness quickstart/harness glasses-ui/harness sdk-ground-truthname: harness description: Run harness tests to verify everything-evenhub skill quality. Dispatches an implementer subagent guided by the skill, then a verifier subagent with a structured checklist. Use to validate any skill works correctly. user-invocable: true allowed-tools: Read, Grep, Glob, Bash, Write, Edit, Agent argument-hint: <skill-name> (e.g., quickstart, glasses-ui)
You are running a harness test for an everything-evenhub skill. Follow these steps exactly. Do not improvise — the value of this harness is reproducibility.
Step 1: Determine the skill to test
Extract the skill name from $ARGUMENTS. Valid skills: quickstart, build-and-deploy, glasses-ui, handle-input, device-features, test-with-simulator, simulator-automation, font-measurement, sdk-reference, cli-reference, design-guidelines, cross-check, sdk-ground-truth.
Audit tests (cross-check, sdk-ground-truth): these do NOT use an implementer subagent. Skip Steps 3–4 and go directly to Step 5.
Step 2: Load all inputs
Read these 3 files (all paths relative to the everything-evenhub repo root):
plugins/everything-evenhub/skills/<skill-name>/SKILL.md→ store asSKILL_CONTENTharness/cases/<skill-name>.md→ store asCASE(extract the "Simulated User Request" and "Output Directory")harness/checklists/<skill-name>.md→ store asCHECKLIST
If any file is missing, tell the user and stop.
Step 3: Prepare output directory
- If the case specifies an output directory, create it:
mkdir -p <output-dir> - If the case requires a pre-existing project (e.g., glasses-ui needs the quickstart output), copy it:
cp -r harness/.output/quickstart/demo-glasses/ harness/.output/<skill-name>/demo-glasses/ - If no pre-existing project is needed and the skill generates files (quickstart, build-and-deploy), just create the output dir.
- If the skill is a reference/guidance skill that produces code in an existing project, ensure the project exists.
Step 4: Dispatch implementer subagent
Launch a general-purpose subagent with model sonnet using EXACTLY this prompt template (substitute the placeholders):
You are Claude Code executing a skill. Follow the skill instructions below to fulfill the user request.
## Skill Instructions
{SKILL_CONTENT}
## User Request
"{SIMULATED_USER_REQUEST from CASE}"
## Your Job
1. Execute the skill instructions to fulfill the user request
2. Work from: {OUTPUT_DIRECTORY from CASE}
3. After completing, if the skill produces code files, run:
- `npx tsc --noEmit` (TypeScript check)
- `npm run build` (Vite build)
If either fails, fix the code and re-run until both pass.
4. Report back: what you did, files changed, build results, any issues encountered
Wait for the subagent to complete and capture its report as IMPLEMENTER_REPORT.
Step 5: Dispatch verifier subagent
Launch a superpowers:code-reviewer subagent using EXACTLY this prompt template:
You are verifying the output of an everything-evenhub harness test.
## What Was Requested
{SIMULATED_USER_REQUEST from CASE}
## What Implementer Claims
{IMPLEMENTER_REPORT}
## CRITICAL: Do Not Trust the Report
Read the ACTUAL files on disk. Verify independently.
## Verification Checklist
{CHECKLIST content}
## Output Location
{OUTPUT_DIRECTORY from CASE}
## Instructions
1. Read every file referenced in the checklist
2. For code-producing skills, run `npx tsc --noEmit` and `npm run build` yourself
3. Report PASS or FAIL for each checklist item
4. For each FAIL: explain what's wrong and whether it's an agent error or a skill guidance gap
5. At the end provide: Score (X/Y), critical issues, skill improvement suggestions
Wait for the verifier to complete and capture its report as VERIFIER_REPORT.
Step 6: Report results
Present to the user in this format:
## Harness Result: <skill-name>
**Score:** X/Y PASS
### FAIL items (if any)
| # | Item | Issue | Cause (agent/skill) |
### Skill improvement suggestions (if any)
| # | Suggestion | Reason |
### Verdict: PASS / NEEDS_FIX
If there are skill improvements needed, ask: "Apply these fixes to the skill?"
Task
Run harness test for: $ARGUMENTS
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/skill-harness-tester-ms8gxmwz/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/skill-harness-tester-ms8gxmwz' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/skill-harness-tester-ms8gxmwz/download' --output '.skill-downloads/skill-harness-tester-ms8gxmwz/SKILL.md.part' && mv '.skill-downloads/skill-harness-tester-ms8gxmwz/SKILL.md.part' '.skill-downloads/skill-harness-tester-ms8gxmwz/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Grep, Glob, Bash, Write, Edit, Agent
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/skill-harness-tester-ms8gxmwz/SKILL.md' && test -s '.skill-downloads/skill-harness-tester-ms8gxmwz/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/harness' && cp -R '.skill-downloads/skill-harness-tester-ms8gxmwz' '.claude/skills/harness'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/skill-harness-tester-ms8gxmwz'openskills read 'skill-harness-tester-ms8gxmwz'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/skill-harness-tester-ms8gxmwz/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
ClickHouse Performance Comparison
Testing
Evaluate ClickHouse performance test results, check PR performance changes, compare with history, and assess whether a result is actionable.
Analyze CI Performance Reports
Testing
Analyze CI performance comparison reports for a ClickHouse PR. Cross-references master history to distinguish real regressions from flaky tests.
Santa Method
Testing
Multi-agent adversarial verification with two independent reviewers. Output is checked twice and iteratively fixed until both pass before shipping.