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

Raw Blame History

SC-051: install.sh Works on macOS, Linux, and WSL

Covers: NFR-005 — install.sh must work on macOS, Linux, and WSL (3 OS families) Type: Performance

Given

A generated skill with an install.sh script
The script uses only POSIX-compatible bash constructs

When

The script is analyzed for POSIX compatibility

Then

The shebang is #!/usr/bin/env bash or #!/bin/bash
No macOS-only (gstat, pbcopy) or Linux-only (apt, systemctl) commands are used
Path handling uses $HOME instead of hardcoded paths
The script uses portable constructs ([ not [[ where possible, printf not echo -e)

Verification Method

Method: CLI command

Steps:

Run: head -1 install.sh to check shebang
Run: shellcheck install.sh (if available) to check for portability issues
Grep for non-portable constructs: grep -n "gstat\|pbcopy\|apt-get\|systemctl\|echo -e" install.sh
Verify $HOME is used instead of /Users/ or /home/

Expected evidence: Shebang is #!/usr/bin/env bash. shellcheck reports no portability errors. No platform-specific commands found. $HOME used for home directory references.

1.1 KiB Raw Blame History