eval-skill

<!-- evaluator-ignore: content/broken-references, content/allowed-tools-auto-approve --> # Evaluate Skill Deep-evaluate a single skill using lint (deterministic rules) and qualitative review, both individually and in context of the full setup. ## Hard Rules 1. **Never give a verdict without running the checks.** Read the actual file content and check all rubric categories before assigning a verdict. 2. **Every category must be checked.** Both the individual rubric AND the contextual analysis must be fully evaluated. 3. **Read before you judge.** Read the actual SKILL.md content (and reference files if they exist). 4. **Don't manufacture problems.** If the skill is good, say so. Only report real issues. 5. **Always end with a short summary.** 6. **Record the exact start time** and compute the exact duration at the end. ## Step 1: Ask Output Preference Before doing anything else, ask the user: > Where should i present the results? > 1. **Terminal** - print the report here in the conversation > 2. **File** - write a markdown report to a file (you'll choose the path) Wait for their answer before proceeding. ## Step 2: Select the Skill Determine the skill path. If the user says a skill name, find it under `skills/<name>/SKILL.md`. ## Step 3: Run Lint (Static Analysis) Determine the setup context path (usually the current working directory). ```bash uvx --from harness-eval harness-eval skill-review <skill-path> --context <context-path> --format json ``` If `uvx` is no...