Eval Criteria: ai-layer-kit/skills/SCOPING.md

Eval Criteria: ai-layer-kit/skills/SCOPING.md

Created: 2026-05-26 Target: production-lines/digital-talent/templates/ai-layer-kit/skills/SCOPING.md Purpose: Convention reference for the paths: frontmatter on talent skills. Cited by USAGE.md (Section A step 5) and the assembly-checklist (Phase D.kit).

Questions

Rule clarity

  1. Is the core rule ("declare paths: or document why global") stated as a single imperative within the first 10 lines?
  2. Is the exception (when omitting paths: is intentional) explicit, not implied?

Syntax verifiability

  1. Is the frontmatter format shown as a complete, copy-pasteable code block?
  2. Does the format example include all required skill frontmatter fields (description, allowed-tools, model, paths)?

Decision guidance

  1. Does the doc provide at least 3 distinct skill-kind categories with concrete example paths?
  2. Are anti-patterns called out with example values (not just abstract warnings)?

Actionability

  1. Is the migration step phrased as checkboxes Pablo can tick during assembly?
  2. Does the doc include a smoke-test method to verify scoping actually works?

Self-containment & cross-references

  1. Does the doc name the related artifacts (USAGE.md, assembly-checklist-template.md, and the example skill file) so a reader can navigate the kit?
  2. Is at least one concrete example of a properly-scoped skill provided (inline or linked by exact filename)?

Token economy

  1. Is the file under 60 content lines?
  2. Does each section earn its weight (no section that could be folded into another without loss)?