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>
28 lines
1.2 KiB
Markdown
28 lines
1.2 KiB
Markdown
# SC-052: Generated Skills Activate Without Platform-Specific Configuration
|
|
|
|
> Covers: NFR-006 — Generated skills must not require any tool-specific configuration to activate; zero-config activation
|
|
> Type: Happy Path
|
|
|
|
## Given
|
|
- A skill has been generated and installed to `~/.claude/skills/log-analysis/`
|
|
- No additional configuration steps have been taken (no `.claude-plugin/`, no marketplace registration)
|
|
|
|
## When
|
|
- A user starts a new Claude Code session and uses a trigger phrase related to the skill
|
|
|
|
## Then
|
|
- The skill is discovered and activated based on its SKILL.md `description` field alone
|
|
- No manual configuration, plugin registration, or marketplace.json was required
|
|
- The skill description contains sufficient domain keywords for agent discovery
|
|
|
|
## Verification Method
|
|
|
|
**Method**: Manual test
|
|
|
|
**Steps**:
|
|
1. Install a generated skill to `~/.claude/skills/log-analysis/`
|
|
2. Start a new Claude Code session
|
|
3. Ask: "Help me analyze these server logs for error patterns"
|
|
4. Verify the skill is activated (agent references skill instructions)
|
|
|
|
**Expected evidence**: The skill activates based on the description matching the user's request. No additional setup steps were required. The agent follows the skill's SKILL.md instructions.
|