eval
Scaffold PoC projects, test workflows against eval criteria. Use for /eval, "test this workflow". NOT for scoring (/eval-score) or improving (/autoimprove).
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Scaffold PoC projects, test workflows against eval criteria. Use for /eval, "test this workflow". NOT for scoring (/eval-score) or improving (/autoimprove).
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
Create premium Accenture-branded PowerPoint presentations following Tufte data visualization principles and Dieter Rams design philosophy. Use when creating slides, presentations, or decks for Accenture corporate settings that require (1) Accenture brand identity (purple A100FF chevron logo clean layouts) (2) Minimal data-focused design (Tufte less but better) (3) Executive-ready aesthetics for boardroom presentations client pitches or internal reports
Route proposed additions to the global Codex control plane by deciding whether a request belongs in `~/.codex/AGENTS.md`, a global workflow or reference doc under `~/.codex/docs`, `~/.codex/bin/workflow.py`, or an enforceable non-prose surface. Use when asked to "add this to global AGENTS", "promote this workflow to global", "add a new global trigger", or decide whether something should be a trigger, workflow, reference, hook, lint rule, or runtime guard.
Add, remove, serve, test, and operate a server-backed in-page agent feedback capability for HTML artifacts, static pages, or local app builds. Use when the user wants Browser-style annotation inside the artifact/app itself, marker-local chat, comment-triggered agent work, queued marker processing, deterministic install/remove scripts, preflight/closeout checks, browser acceptance evidence, or progressive-disclosure access to marker context.
Audits any agent harness codebase against 13 meta-principles of quality, scores each 0 to 10 with code citations, generates a self-contained HTML report for operators, and writes an agent-readable AGENTS.md improvement directive with file-level architecture recommendations to reach 9.5 or better. Use when the user wants to audit or rate an agent harness, evaluate harness quality, score an agent framework, get a roadmap for improving a harness, run agentharness-audit, audit this harness, rate Hermes, audit Codex, or audit a Claude Code harness. Not for individual skill audits or general code review.
Use when controlling ChatGPT Atlas through Codex Computer Use, especially browser tasks where context efficiency matters: fewer screenshots, fewer UI snapshots, fewer clicks, and cleaner browser state.
Audit project against golden principles, produce scorecard. Use for /audit, "check project quality". NOT for system setup health (/harness-audit) or eval scoring (/eval-score).
| name | eval |
| description | Scaffold PoC projects, test workflows against eval criteria. Use for /eval, "test this workflow". NOT for scoring (/eval-score) or improving (/autoimprove). |
| model | sonnet |
| effort | medium |
| disable-model-invocation | true |
| allowed-tools | Read, Write, Bash, Glob, Grep |
EXECUTE this skill now. Follow the workflow steps below using the provided $ARGUMENTS. Do NOT describe, summarize, or explain this skill — run it.
EVAL_DIR: C:/Users/gurusharan.gupta/Agents/Claude Code/evalSCAFFOLDS_DIR: C:/Users/gurusharan.gupta/Agents/Claude Code/eval/scaffoldsCRITERIA_DIR: C:/Users/gurusharan.gupta/Agents/Claude Code/eval/criteriaHISTORY_PATH: C:/Users/gurusharan.gupta/Agents/Claude Code/eval/history/eval-history.jsonDEFAULT_TARGET: C:/Users/gurusharan.gupta/Agents/eval-pocParse $ARGUMENTS to determine action:
/eval scaffold <template> [target-path] — Copy scaffold to target, init git/eval criteria <workflow-name> — Display eval checklist + prompts/eval list — List all criteria files with latest scores/eval (no args) — Show usage helpFor scoring and history, use /eval-score (separate skill).
/eval scaffold <template> [target-path]SCAFFOLDS_DIR/<template>/
node-api, python-cliDEFAULT_TARGET if not specifiedcp -r SCAFFOLDS_DIR/<template>/* <target>/
cp -r SCAFFOLDS_DIR/<template>/.* <target>/ 2>/dev/null # hidden files if any
cd <target> && git init && git add -A && git commit -m "Initial scaffold from eval/<template>"
Scaffold created: <target>
Template: <template>
Deliberately missing: CLAUDE.md, .claude/, docs/, tests, formatting config
Next steps:
1. Open a NEW Claude Code session: cd <target> && claude
2. Use one of these prompts:
Cold start: "<prompt from criteria>"
Explicit: "<prompt from criteria>"
Adversarial: "<prompt from criteria>"
3. After the agent finishes, return here and run:
/eval score <workflow-name> <target>
/eval criteria <workflow-name>CRITERIA_DIR/<workflow-name>.jsonEval Criteria: <name>
<description>
Checks (N total, max score: 100):
# Weight Severity Type Description
────────────────────────────────────────────────────────────────
1 20 critical file_exists CLAUDE.md was created
2 5 critical file_contains CLAUDE.md contains Commands section
3 10 recommended dir_exists docs/exec-plans/active/ exists
...
Test Prompts:
Cold start: "I have a Node.js API project..."
Explicit: "Run /init-project on this project..."
Adversarial: "This codebase is a mess..."
/eval listCRITERIA_DIR/ (exclude _template.json)Available Eval Criteria:
Name Checks Latest Score Latest Grade Runs
──────────────────────────────────────────────────────────────
init-project 13 90/100 A 3
golden-principles 8 — — 0
code-review 8 — — 0