skill frontmatter: non-spec `trigger:` field — fold into description for Agent Skills spec conformance

[bencharoenwong]

Summary

The generated SKILL.md frontmatter (all host variants, checked at v0.8.34) carries a trigger: field:

---
name: graphify
description: "Use for any question about a codebase, ..."
trigger: /graphify
---

trigger is not part of the Agent Skills specification frontmatter schema (name, description, license, compatibility, metadata, allowed-tools).

Why it matters

1. It's a no-op where it looks load-bearing. Claude Code (and other spec-following hosts) only load name + description at startup for routing — trigger: is silently ignored, so any routing intent encoded there isn't seen unless duplicated in the description (yours already is: the description mentions graphify-out/ query routing).
2. Spec validators and commit gates now flag it. agentskills validate (skills-ref) rejects unexpected frontmatter fields, and downstream users running spec lint in CI/commit hooks get a standing warning on every graphify upgrade.

Suggested fix

Drop trigger: from the generated frontmatter and (if any variant's trigger text isn't already in its description) fold it into description — that's the only field hosts actually read for routing. The v0.8.x lean-skill redesign (#1106) already moved everything else in the right direction; this is the last non-spec field.

Happy to send a PR if useful.

[safishamsi]

Fixed in 8a04560.

Removed trigger: from the frontmatter of all 14 skill variants (13 split platforms via gen.py + aider monolith). The field is not part of the Agent Skills spec and was silently ignored by spec-following hosts anyway — routing intent lives entirely in the description field which already says "treated as a graphify query first when graphify-out/ exists".

agentskills validate should no longer flag graphify skills.