Skip to content

[B6] Trigger phrase lists in skill descriptions — 7 skills affected #653

@synerbot

Description

@synerbot

Several skills include "Use when user says X" or "Triggers on..." in their description field. Per B6, trigger phrases are acceptable when they supplement a clear value sentence, but flagged when the value sentence is weak.

Assessment by skill:

Skill Value sentence Trigger phrases Assessment
github-create-pr "Create GitHub PRs using templates." ✅ "crear pr", "create pr"... (5 phrases) Borderline — value sentence is clear but trigger list dominates
syner-boundaries "Validate that proposals respect Syner's operational boundaries." ✅ "Triggers on 'check boundaries'..." Acceptable — value clear, triggers supplement
workflow-reviewer "Review GitHub Actions workflows before running." ✅ "Triggers on 'review workflow'..." Acceptable — value clear
create-syner "Scaffold syner components." ✅ "when the user says 'crear', 'new'" Borderline — value sentence is brief
create-syner-agent "Create syner agents." ✅ "when user says 'crear agente'" Borderline — value sentence is very brief
create-syner-app "Scaffold new applications following the syner common stack." ✅ "when the user says 'nueva app'" Acceptable — value sentence is specific
syner-enhance-skills "Improve an existing skill by auditing and applying fixes." ✅ 'enhance skill', 'improve skill'... Acceptable

Options:

A) Clean up the weakest cases (surgical)

  • github-create-pr: The description IS mostly trigger phrases. Rewrite: "Create GitHub PRs using project templates. Handles auth, template selection, and PR creation."
  • create-syner-agent: "Create syner agents." is thin. Expand to: "Create syner agents that run in isolated contexts and can be invoked via the Task tool."
  • Leave the others as-is (acceptable per spec).

B) Remove all trigger phrases from descriptions (strict interpretation)

  • Clean but may reduce discoverability for the orchestrator when routing.
  • Trigger phrases in descriptions help the routing system match intent to skill.

C) Keep as-is (accept supplemental trigger phrases as ecosystem pattern)

  • All 7 cases have clear value sentences as the first sentence.
  • Trigger phrases help with routing discovery without replacing the value.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions