agent-skill-creator/scenarios/SC-056-migrate-legacy-skill-flow.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.4 KiB

SC-056: Migrate Legacy Skill with -cskill Suffix and marketplace.json

Covers: FR-007, FR-005, Section 2.2 — Secondary flow: Migrate legacy skill Type: Happy Path

Given

  • A legacy skill directory my-tool-cskill/ exists with:
    • SKILL.md with name: my-tool-cskill
    • .claude-plugin/marketplace.json with non-standard fields (version, author, tags)
    • Scripts and references from v3.x

When

  • The user invokes: "Migrate this skill to the new standard"

Then

  • The directory is renamed from my-tool-cskill/ to my-tool/
  • The name field in SKILL.md is updated to my-tool
  • The .claude-plugin/marketplace.json is removed (simple skill) or stripped to official fields only
  • An install.sh is generated
  • A README.md with cross-platform instructions is generated
  • Validation passes on the migrated skill

Verification Method

Method: Manual test

Steps:

  1. Create my-tool-cskill/ with legacy structure
  2. Invoke: "Migrate this skill to the new standard"
  3. Verify my-tool-cskill/ no longer exists
  4. Verify my-tool/ exists with updated files
  5. Verify name: my-tool in SKILL.md
  6. Verify .claude-plugin/ is removed
  7. Verify install.sh and README.md exist
  8. Run validation on my-tool/

Expected evidence: Directory renamed. Frontmatter updated. marketplace.json removed. install.sh and README.md present. Validation passes.