<< All versions
Skill v1.0.1
currentLLM-judged scan95/100soul-brews-studio/arra-oracle-skills-cli/alpha-feature
+3 new
──Details
PublishedAugust 6, 2026 at 06:04 AM
Content Hashsha256:813c6b30feb89a56...
Git SHA044e8396bc9f
Bump Typepatch
──Files
Files (1 file, 2.2 KB)
SKILL.md2.2 KBactive
SKILL.md · 102 lines · 2.2 KB
version: "1.0.1" name: alpha-feature description: 'Full skill development pipeline — create, compile, test, commit, install. Use when user says "new skill", "create skill", "alpha-feature", or wants to build a skill end-to-end.' argument-hint: "<name> [description]" zombie: true origin: arra-symbiosis-skills metadata: internal: true
/alpha-feature — Create Skill + Install Locally
Create skill -> compile -> test -> commit -> push -> install. No release — use /release when ready.
Usage
/alpha-feature whats-next "Suggest next action from context"/alpha-feature my-skill # Interactive — ask for description
Steps
1. Parse Input
$ARGUMENTS[0]= skill name (kebab-case)- Rest = description (optional, ask if missing)
If no arguments, ask:
- "What should the skill be called?" (kebab-case)
- "What does it do?" (one sentence)
- "When should it trigger?" (user phrases)
2. Create Skill
Create skills/<name>/SKILL.md (public shelf; vault src/skills/ is for secret/archived skills):
markdown
---name: <name>description: <description>. Use when user says "<triggers>". Do NOT trigger for <anti-triggers>.argument-hint: "<hint>"---# /<name><Instructions based on user's description>ARGUMENTS: $ARGUMENTS
Follow best practices:
- Description 50+ words with explicit triggers
- Anti-triggers to avoid conflicts with existing skills
- Imperative form instructions
- Keep under 100 lines for simple skills
3. Compile + Test
bash
bun run compilebun test
If tests fail -> fix before continuing.
4. Commit + Push
bash
git add -Agit commit -m "feat: add /<name> skill — <short description>"git push origin main
5. Install Locally
bash
bun run dev -- install -g -y
6. Output
## New Skill: /<name>**Tests**: pass**Installed**: locally (restart session to activate)When ready to release: `/release`
Rules
- Always add anti-triggers based on existing skill conflicts
- Always run tests before committing
- Never create skills that duplicate existing ones — check skill list first
- Keep SKILL.md lean — under 100 lines for simple skills
- Do NOT bump version or create tags — that's
/release's job
ARGUMENTS: $ARGUMENTS