admin-valentin/agent-skill-creator
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
agent-skill-creator/scenarios/SC-036-phase5-runs-validation.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 KiB
Raw Blame History

SC-036: Phase 5 Runs Validation After Generating All Files

Covers: FR-024 — Phase 5 MUST run validation after generating all files Type: Happy Path

Given

  • The meta-skill has completed Phases 1-4
  • Phase 5 has generated all files (SKILL.md, scripts, references, install.sh, README.md)

When

  • Phase 5 reaches the validation step (step h in the pipeline)

Then

  • The validation function is invoked automatically on the generated skill directory
  • The validation result is reported to the user
  • If validation passes, Phase 5 continues to the security scan
  • If validation fails, the user is informed of the specific errors

Verification Method

Method: Manual test

Steps:

  1. Run the meta-skill to completion
  2. Observe Phase 5 output for validation step
  3. Verify a validation report is shown (pass/fail with details)

Expected evidence: Phase 5 output includes a validation report section, such as:

Validation: PASSED
  - name format: OK
  - description length: OK
  - directory match: OK
  - line count: OK