| id | skill-sample-bundle |
| name | Directory Skill Bundle Walkthrough |
| description | Demonstrates how to structure a multi-file skill bundle with references and helper scripts |
| version | 0.1.0 |
| author | brAInwav Development Team |
| category | documentation |
| tags | bundle, example, skills-automation |
| difficulty | beginner |
| estimatedTokens | 1200 |
| resources | ./REFERENCE.md, ./scripts/run-quality-check.sh, ./assets/bundle-checklist.txt |
Directory Skill Bundle Walkthrough
Use this sample to understand how a directory-based skill can reference additional material and scripts while remaining CI-compliant.
When to Use
- You need a skill that ships command helpers or detailed appendices.
- Multiple agents will maintain the skill and want a predictable structure.
- CI should guarantee that every referenced artifact is present.
How to Apply
- Copy this bundle into your target category and rename the folder.
- Update the YAML frontmatter and include every file in the
resources:list. - Link to
REFERENCE.mdfor deeper dives and describe when to run the script. - Keep helper scripts executable and documented directly in the skill body.
# Run the quick lint used in this example bundle
./scripts/run-quality-check.sh
Success Criteria
./scripts/skills-setup.sh checkreports zero missing or orphaned resources.- The primary guidance fits in
SKILL.md; supporting detail lives in references. - Helper scripts emit actionable output and document expected inputs/outputs.
Common Pitfalls
- Forgetting to add new files to the
resources:list (CI will block the change). - Allowing scripts to drift from the instructions in
SKILL.md. - Storing large binaries in
assets/instead of linking to durable storage.