## Problem/Motivation `docs/skill-authoring.md` explicitly states: > The only Drupal-wide required frontmatter fields are the Agent Skills required fields: `name` and `description`. Do not require Drupal-specific frontmatter such as `drupal-version`, `status`, `owner`, or `last-reviewed`. > > Lifecycle, ownership, freshness, and package/version metadata should be handled by the owning project, issue or merge request process, release/package metadata, registry, or future package-manager conventions. However, several existing skills ship a `metadata:` block containing exactly these discouraged fields (`status`, `drupal-version`, `last-reviewed`), and at least one skill's eval suite (`evals/drupal-render-pipeline/static-checks.json` S02) asserts those fields are *required* — directly contradicting the authoring guide. Affected skills include at minimum: - `skills/drupal-expert-corrections/SKILL.md` - `skills/drupal-render-pipeline/SKILL.md` ## Proposed Resolution 1. Audit all skills under `skills/` for `metadata:` blocks containing discouraged fields. 2. Remove those blocks from each skill. 3. Update any eval static checks that assert those fields are required (e.g. `drupal-render-pipeline` S02) to instead assert only `name` and `description`. 4. Confirm all skills still pass the eval suite after removal. ## Who can work on this? Novice-friendly — mechanical find-and-remove across skill files, with a straightforward eval fix. Good first issue for anyone familiar with the repo structure.