admin-valentin/agent-skill-creator
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
agent-skill-creator/scenarios/SC-014-metadata-author-version.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,003 B
Raw Blame History

SC-014: Generated Skills Include Metadata with Author and Version

Covers: FR-009 — Generated skills MUST include metadata field with author and version Type: Happy Path

Given

  • The meta-skill is invoked to create a skill
  • Input: "Create a skill for database migration management"

When

  • Phase 5 generates the SKILL.md

Then

  • The SKILL.md frontmatter includes a metadata mapping
  • The metadata contains an author field with a non-empty string
  • The metadata contains a version field (e.g., 1.0.0)

Verification Method

Method: Automated test

Steps:

  1. Run the meta-skill to generate the skill
  2. Parse the YAML frontmatter of the generated SKILL.md
  3. Assert metadata key is present and is a dict
  4. Assert metadata.author is a non-empty string
  5. Assert metadata.version is a non-empty string matching semver pattern ^\d+\.\d+\.\d+

Expected evidence: Frontmatter contains:

metadata:
  author: "Some Author"
  version: "1.0.0"