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>
29 lines
889 B
Markdown
29 lines
889 B
Markdown
# SC-064: Security Scan Detects eval() Calls
|
|
|
|
> Covers: FR-013, NFR-004 — Security scan catches OWASP top patterns including eval()
|
|
> Type: Happy Path
|
|
|
|
## Given
|
|
- A generated skill directory `risky-skill/` contains `scripts/processor.py` with:
|
|
```python
|
|
user_code = input("Enter expression: ")
|
|
result = eval(user_code)
|
|
```
|
|
|
|
## When
|
|
- The security scan is run on `risky-skill/`
|
|
|
|
## Then
|
|
- The security scan identifies the `eval()` call as a risk
|
|
- The `security` list contains a finding about dangerous `eval()` usage
|
|
|
|
## Verification Method
|
|
|
|
**Method**: Automated test
|
|
|
|
**Steps**:
|
|
1. Create `risky-skill/scripts/processor.py` with `eval()` call on user input
|
|
2. Run the security scan
|
|
3. Assert security findings reference `eval()` or "code injection"
|
|
|
|
**Expected evidence**: Security finding like `"Dangerous eval() call in scripts/processor.py: potential code injection risk"`.
|