bac2b27bb8
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>
33 lines
1.2 KiB
Markdown
33 lines
1.2 KiB
Markdown
# SC-016: Validation Checks All Official Spec Rules
|
|
|
|
> Covers: FR-011, FR-012, NFR-003 — Validation MUST check every generated skill against official spec rules
|
|
> Type: Happy Path
|
|
|
|
## Given
|
|
- A fully valid skill directory `valid-skill/` exists with:
|
|
- `name: valid-skill` (matches directory)
|
|
- `description: "A valid test skill for verification"` (<=1024 chars)
|
|
- Valid YAML frontmatter structure
|
|
- SKILL.md body <500 lines
|
|
|
|
## When
|
|
- The validation function `validate_skill("valid-skill/")` is invoked
|
|
|
|
## Then
|
|
- The validation result `valid` is `True`
|
|
- The `errors` list is empty
|
|
- The `warnings` list may contain non-blocking suggestions
|
|
- All spec rules have been checked (name format, description length, frontmatter structure, directory name match)
|
|
|
|
## Verification Method
|
|
|
|
**Method**: Automated test
|
|
|
|
**Steps**:
|
|
1. Create a fully compliant skill directory `valid-skill/` with correct frontmatter
|
|
2. Call `validate_skill("valid-skill/")`
|
|
3. Assert `result.valid is True`
|
|
4. Assert `len(result.errors) == 0`
|
|
5. Verify the function checks at minimum: name format, description length, frontmatter structure, directory match
|
|
|
|
**Expected evidence**: `valid: True`, `errors: []`. Function returns a ValidationResult with all four required check categories evaluated.
|