agent-skill-creator/scenarios/SC-015-compatibility-field-platform-specific.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.1 KiB

SC-015: Compatibility Field Included When Platform-Specific Features Used

Covers: FR-010 — Generated skills SHOULD include compatibility field when platform-specific features are used Type: Happy Path

Given

  • The meta-skill is invoked to create a skill that uses platform-specific features
  • Input: "Create a skill that uses Claude Code's allowed-tools feature to restrict tool access to only Bash and Read"

When

  • Phase 5 generates the SKILL.md

Then

  • The SKILL.md frontmatter includes a compatibility field
  • The compatibility value describes which platforms or features are required (<=500 chars)
  • The allowed-tools experimental field is also present in frontmatter

Verification Method

Method: Automated test

Steps:

  1. Run the meta-skill with the platform-specific input
  2. Parse the YAML frontmatter
  3. Assert compatibility key is present
  4. Assert len(compatibility) <= 500
  5. Assert the value references the platform-specific constraint

Expected evidence: Frontmatter contains compatibility: "Requires Claude Code for allowed-tools support" (or similar). Length is <=500 chars.