Skills Concept
Skills are the core building blocks of the Skills MCP system. Each skill is a versioned bundle of knowledge that an LLM agent can discover and execute.
Structure
Every skill version must include these files:
| File | Purpose |
|---|---|
metadata.yaml | Name, tags, dependencies, visibility |
overview.md | What the skill does, when to use it |
workflow.md | Step-by-step execution instructions |
validation.md | How to verify the work is correct |
Optional additions:
| Path | Purpose |
|---|---|
scripts/ | Helper scripts (bash, Python, TS, Go, etc.) |
references/ | Supporting documentation or examples |
Versioning
Skills use directory-based versioning: skills/versions/<name>/0001/, 0002/, etc. The active version is a symlink at skills/<name>/ pointing to the current version directory.
Namespacing
All skills must be namespaced to avoid collisions:
| Prefix | Scope |
|---|---|
haakco- | Shared / org-wide |
cb- | CouriBee |
tl- | TrackLab |
mpow- | Mpowered |
Stack-specific suffixes are added as needed: haakco-laravel-auth, tl-web-deploy.
Dependencies
Skills can declare dependencies via requiredSkills in metadata.yaml:
name: tl-laravel-auth
requiredSkills:
- haakco-laravel-auth
The sync system resolves dependencies recursively and pulls them automatically.
Visibility
Three levels control who can access a skill:
| Level | Access |
|---|---|
public | Anyone |
workspace | Workspace members only |
private | Owner and explicit shares only |