admin-valentin/agent-skill-creator
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
agent-skill-creator/scenarios/SC-066-activation-trigger-phrases.scenario.md
francylisboacharuto bac2b27bb8 feat: v4.0 Cross-Platform Modernization — Agent Skills Open Standard compliance 
BREAKING CHANGES:
- Remove -cskill suffix from all skill names (use standard kebab-case)
- Simplify marketplace.json to only official fields (fixes Issue #5)
- SKILL.md body must be <500 lines (progressive disclosure via references/)

New features:
- Cross-platform support for 8+ platforms (Claude Code, Copilot, Cursor, Windsurf, Cline, Codex CLI, Gemini CLI)
- scripts/install-template.sh: Auto-detect platform installer with --dry-run
- scripts/validate.py: Spec compliance checker for generated skills
- scripts/security_scan.py: Security scanner for hardcoded keys and dangerous patterns
- MIGRATION.md: v3.x to v4.0 migration guide
- 6 new reference files for progressive disclosure from lean SKILL.md

Key changes:
- SKILL.md: 4,116 → 272 lines with spec-compliant YAML frontmatter
- marketplace.json: Stripped to {name, plugins} only
- article-to-prototype-cskill/ → article-to-prototype/
- stock-analyzer-cskill/ → stock-analyzer/
- Export system integrates validation + security scanning
- README.md rewritten for all supported platforms
- Phase 5 pipeline outputs SKILL.md-first, spec-compliant skills

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-26 14:52:09 -03:00

1.2 KiB
Raw Blame History

SC-066: Meta-Skill Activates on Standard Trigger Phrases

Covers: Section 5.1 — Activation interface trigger phrases Type: Happy Path

Given

  • The meta-skill is installed and active in a Claude Code session

When

  • The user types one of the documented trigger phrases:
    • "Create a skill for file organization"
    • "Automate this workflow: daily report generation"
    • "Every day I copy CSV files manually, automate this"
    • "Create an agent for code formatting"
    • "Create a cross-platform skill for linting"
    • "Validate this skill: my-tool/"
    • "Export this skill for Cursor"

Then

  • Each trigger phrase activates the meta-skill
  • The meta-skill begins the appropriate flow (creation, validation, export, or migration)

Verification Method

Method: Manual test

Steps:

  1. Start a Claude Code session with the meta-skill installed
  2. Test each trigger phrase individually
  3. Verify the meta-skill activates and begins the correct flow

Expected evidence: Each trigger phrase results in the meta-skill activating. "Create a skill" triggers the 5-phase pipeline. "Validate this skill" triggers the validation flow. "Export this skill" triggers the export flow.