alpha-feature

Name: alpha-feature
Author: Soul-Brews-Studio

109stars55forks

How to install alpha-feature?

soul-brews-studio/arra-oracle-skills-cli/alpha-feature

$npx -y skills add Soul-Brews-Studio/arra-oracle-skills-cli --skill alpha-feature

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# /alpha-feature — Create Skill + Install Locally
2
3	Create skill -> compile -> test -> commit -> push -> install. No release — use `/release` when ready.
4
5	## Usage
6
7	```
8	/alpha-feature whats-next "Suggest next action from context"
9	/alpha-feature my-skill # Interactive — ask for description
10	```
11
12	## Steps
13
14	### 1. Parse Input
15
16	- `$ARGUMENTS[0]` = skill name (kebab-case)
17	- Rest = description (optional, ask if missing)
18
19	If no arguments, ask:
20	- "What should the skill be called?" (kebab-case)
21	- "What does it do?" (one sentence)
22	- "When should it trigger?" (user phrases)
23
24	### 2. Create Skill
25
26	Create `skills/<name>/SKILL.md` (public shelf; vault src/skills/ is for secret/archived skills):
27
28	```markdown
29	---
30	name: <name>
31	description: <description>. Use when user says "<triggers>". Do NOT trigger for <anti-triggers>.
32	argument-hint: "<hint>"
33	---
34
35	# /<name>
36
37	<Instructions based on user's description>
38
39	ARGUMENTS: $ARGUMENTS
40	```
41
42	Follow best practices:
43	- Description 50+ words with explicit triggers
44	- Anti-triggers to avoid conflicts with existing skills
45	- Imperative form instructions
46	- Keep under 100 lines for simple skills
47
48	### 3. Compile + Test
49
50	```bash
51	bun run compile
52	bun test
53	```
54
55	If tests fail -> fix before continuing.
56
57	### 4. Commit + Push
58
59	```bash
60	git add -A
61	git commit -m "feat: add /<name> skill — <short description>"
62	git push origin main
63	```
64
65	### 5. Install Locally
66
67	```bash
68	bun run dev -- install -g -y
69	```
70
71	### 6. Output
72
73	```
74	## New Skill: /<name>
75
76	Tests: pass
77	Installed: locally (restart session to activate)
78
79	When ready to release: `/release`
80	```
81
82	## Rules
83
84	- Always add anti-triggers based on existing skill conflicts
85	- Always run tests before committing
86	- Never create skills that duplicate existing ones — check skill list first
87	- Keep SKILL.md lean — under 100 lines for simple skills
88	- Do NOT bump version or create tags — that's `/release`'s job
89
90	ARGUMENTS: $ARGUMENTS

People who liked this also viewed

6 picks

Type

alpha-feature

109stars55forks

View on GitHub

How to install alpha-feature?

soul-brews-studio/arra-oracle-skills-cli/alpha-feature

$npx -y skills add Soul-Brews-Studio/arra-oracle-skills-cli --skill alpha-feature

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# /alpha-feature — Create Skill + Install Locally
2
3	Create skill -> compile -> test -> commit -> push -> install. No release — use `/release` when ready.
4
5	## Usage
6
7	```
8	/alpha-feature whats-next "Suggest next action from context"
9	/alpha-feature my-skill # Interactive — ask for description
10	```
11
12	## Steps
13
14	### 1. Parse Input
15
16	- `$ARGUMENTS[0]` = skill name (kebab-case)
17	- Rest = description (optional, ask if missing)
18
19	If no arguments, ask:
20	- "What should the skill be called?" (kebab-case)
21	- "What does it do?" (one sentence)
22	- "When should it trigger?" (user phrases)
23
24	### 2. Create Skill
25
26	Create `skills/<name>/SKILL.md` (public shelf; vault src/skills/ is for secret/archived skills):
27
28	```markdown
29	---
30	name: <name>
31	description: <description>. Use when user says "<triggers>". Do NOT trigger for <anti-triggers>.
32	argument-hint: "<hint>"
33	---
34
35	# /<name>
36
37	<Instructions based on user's description>
38
39	ARGUMENTS: $ARGUMENTS
40	```
41
42	Follow best practices:
43	- Description 50+ words with explicit triggers
44	- Anti-triggers to avoid conflicts with existing skills
45	- Imperative form instructions
46	- Keep under 100 lines for simple skills
47
48	### 3. Compile + Test
49
50	```bash
51	bun run compile
52	bun test
53	```
54
55	If tests fail -> fix before continuing.
56
57	### 4. Commit + Push
58
59	```bash
60	git add -A
61	git commit -m "feat: add /<name> skill — <short description>"
62	git push origin main
63	```
64
65	### 5. Install Locally
66
67	```bash
68	bun run dev -- install -g -y
69	```
70
71	### 6. Output
72
73	```
74	## New Skill: /<name>
75
76	Tests: pass
77	Installed: locally (restart session to activate)
78
79	When ready to release: `/release`
80	```
81
82	## Rules
83
84	- Always add anti-triggers based on existing skill conflicts
85	- Always run tests before committing
86	- Never create skills that duplicate existing ones — check skill list first
87	- Keep SKILL.md lean — under 100 lines for simple skills
88	- Do NOT bump version or create tags — that's `/release`'s job
89
90	ARGUMENTS: $ARGUMENTS

People who liked this also viewed

6 picks

Type