🔧 chore: fix skill naming and gitea actions compatibility (related to #2)
Some checks failed
CI/CD Pipeline / CI Pipeline (push) Failing after 7m12s
Some checks failed
CI/CD Pipeline / CI Pipeline (push) Failing after 7m12s
This commit is contained in:
109
.vibe/skills/skill-creator/SKILL.md
Normal file
109
.vibe/skills/skill-creator/SKILL.md
Normal file
@@ -0,0 +1,109 @@
|
||||
---
|
||||
name: skill-creator
|
||||
description: Creates and manages Mistral Vibe skills following the Agent Skills specification. Use when you need to create new skills, validate existing ones, or maintain skill consistency across projects.
|
||||
license: MIT
|
||||
metadata:
|
||||
author: DanceLessonsCoach Team
|
||||
version: "1.0.0"
|
||||
---
|
||||
|
||||
# Skill Creator
|
||||
|
||||
A skill for creating and managing Mistral Vibe skills that comply with the Agent Skills specification.
|
||||
|
||||
## Commands
|
||||
|
||||
### Create a new skill
|
||||
|
||||
```bash
|
||||
skill_creator create <skill_name>
|
||||
```
|
||||
|
||||
Creates a new skill scaffold with proper directory structure and SKILL.md file.
|
||||
|
||||
**Arguments:**
|
||||
- `skill_name`: Name of the skill to create (required)
|
||||
|
||||
### Validate a skill
|
||||
|
||||
```bash
|
||||
skill_creator validate <skill_path>
|
||||
```
|
||||
|
||||
Validates that a skill follows the Agent Skills specification.
|
||||
|
||||
**Arguments:**
|
||||
- `skill_path`: Path to the skill directory (required)
|
||||
|
||||
## Workflows
|
||||
|
||||
### Complete skill creation workflow
|
||||
|
||||
1. **Gather requirements**: Determine skill name, description, and purpose
|
||||
2. **Scaffold structure**: Create directory structure with SKILL.md
|
||||
3. **Generate templates**: Create optional directories (scripts/, references/, assets/)
|
||||
4. **Validate structure**: Ensure compliance with specification
|
||||
5. **Document skill**: Add comprehensive instructions to SKILL.md
|
||||
|
||||
## Usage Examples
|
||||
|
||||
### Creating a BDD testing skill
|
||||
|
||||
```bash
|
||||
# Create the skill
|
||||
skill_creator create bdd-testing
|
||||
|
||||
# Navigate to the skill directory
|
||||
cd .vibe/skills/bdd-testing
|
||||
|
||||
# Edit the SKILL.md file
|
||||
# Add your BDD-specific instructions and workflows
|
||||
```
|
||||
|
||||
### Validating an existing skill
|
||||
|
||||
```bash
|
||||
skill_creator validate .vibe/skills/skill-creator
|
||||
```
|
||||
|
||||
## Skill Structure
|
||||
|
||||
A properly structured skill should have:
|
||||
|
||||
```
|
||||
skill-name/
|
||||
├── SKILL.md # Required: metadata + instructions
|
||||
├── scripts/ # Optional: executable code
|
||||
├── references/ # Optional: documentation
|
||||
├── assets/ # Optional: templates, resources
|
||||
└── ... # Any additional files
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
Follow the [Skill Creation Best Practices](references/BEST_PRACTICES.md) for creating high-quality skills:
|
||||
|
||||
1. **Start from real expertise**: Base skills on actual project knowledge
|
||||
2. **Refine with execution**: Test and improve based on real usage
|
||||
3. **Spend context wisely**: Focus on what the agent wouldn't know
|
||||
4. **Design coherent units**: One skill = one class of problems
|
||||
5. **Use instruction patterns**: Gotchas, templates, checklists, validation loops
|
||||
6. **Calibrate control**: Match specificity to task fragility
|
||||
7. **Progressive disclosure**: Keep SKILL.md < 500 lines, move details to references/
|
||||
|
||||
See [BEST_PRACTICES.md](references/BEST_PRACTICES.md) for comprehensive guidelines.
|
||||
|
||||
## Advanced Features
|
||||
|
||||
For advanced skill management, see [ADVANCED_FEATURES.md](references/ADVANCED_FEATURES.md):
|
||||
|
||||
- **Skill Versioning**: Semantic versioning and lifecycle management
|
||||
- **Dependencies**: Manage skill dependencies and compatibility
|
||||
- **Composite Skills**: Combine multiple skills for complex workflows
|
||||
- **Testing & Validation**: Advanced validation levels and test automation
|
||||
- **Documentation Standards**: Maturity levels and completeness checklists
|
||||
- **Governance**: Ownership models and team collaboration
|
||||
- **Analytics**: Usage tracking and impact measurement
|
||||
- **Publication**: Release workflows and distribution channels
|
||||
|
||||
These advanced features transform skill_creator from a basic scaffolding tool to a comprehensive skill management platform.
|
||||
Reference in New Issue
Block a user