feel

Name: feel
Author: Soul-Brews-Studio

109stars55forks

How to install feel?

soul-brews-studio/arra-oracle-skills-cli/feel

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

Installs into the current project.

Summary

Capture how the system feels — energy, momentum, burnout, breakthrough. Emotional intelligence for Oracle-human collaboration. Use when user says 'feel', 'how are we', 'energy check', 'burnout', 'momentum', or wants emotional awareness of the work.

Files · 1

View on GitHub

SKILL.md

1	# /feel — System Emotional Intelligence
2
3	> "Code has no feelings. But the humans writing it do.
4	> And the patterns in the code reveal what the humans feel."
5
6	## Usage
7
8	```
9	/feel # Quick pulse — how does the system feel right now?
10	/feel --deep # Deep scan — energy arc, momentum, burnout signals
11	/feel --log # Append to feels.log (no output, just record)
12	```
13
14	---
15
16	## Step 0: Timestamp
17
18	```bash
19	date "+🕐 %H:%M %Z (%A %d %B %Y)"
20	```
21
22	---
23
24	## Quick Pulse (default)
25
26	Read the signals and report:
27
28	### Step 1: Gather evidence
29
30	```bash
31	# Recent git activity — momentum or silence?
32	git log --oneline --since="7 days ago" --all 2>/dev/null \| wc -l
33
34	# Session frequency — are we showing up?
35	ls -t ~/.claude/projects//*.jsonl 2>/dev/null \| head -10
36
37	# Open issues — overwhelmed or on track?
38	gh issue list --state open --limit 50 --json number 2>/dev/null \| jq 'length'
39
40	# Recent retros — are we reflecting?
41	ls -t ψ/memory/retrospectives/*/.md 2>/dev/null \| head -5
42
43	# Stale branches — unfinished business?
44	git branch --sort=-committerdate \| head -10
45	```
46
47	### Step 2: Classify the feeling
48
49	\| Signal \| Indicator \| Feeling \|
50	\|--------\|-----------\|---------\|
51	\| Many commits, short intervals \| High activity \| 🔥 Flow / momentum \|
52	\| Few commits, long gaps \| Low activity \| 😴 Drift / disconnection \|
53	\| Many open issues, few closed \| Growing backlog \| 😰 Overwhelm \|
54	\| Recent retros + handoffs \| Healthy reflection \| 🧘 Grounded \|
55	\| Stale branches, no PRs \| Abandoned work \| 😶 Avoidance \|
56	\| Lots of new repos/features \| Exploration \| ✨ Curiosity \|
57	\| Same files edited repeatedly \| Iteration \| 🔄 Grinding \|
58	\| No sessions in days \| Absence \| 🌑 Dark period \|
59
60	### Step 3: Report
61
62	```
63	💜 System Pulse — [DATE]
64
65	Energy: [🔥 Flow \| 😴 Drift \| 😰 Overwhelm \| 🧘 Grounded \| ...]
66	Momentum: [↗️ Rising \| → Steady \| ↘️ Falling \| ⏸️ Paused]
67	Last active: [X hours/days ago]
68	Commits (7d): [N]
69	Open issues: [N]
70	Sessions (7d): [N]
71
72	[1-2 sentence read — honest, not cheerful]
73
74	💡 [Suggestion if concerning pattern detected]
75	```
76
77	---
78
79	## Deep Scan (`--deep`)
80
81	Everything from quick pulse, plus:
82
83	### Energy Arc (last 30 days)
84
85	Plot the energy over time based on git activity + session frequency:
86
87	```
88	Week 1: ████████░░ (high — 45 commits)
89	Week 2: ██████░░░░ (medium — 28 commits)
90	Week 3: ██░░░░░░░░ (low — 8 commits)
91	Week 4: █████░░░░░ (recovering — 22 commits)
92	```
93
94	### Burnout Signals
95
96	Check for warning patterns:
97	- Same error fixed 3+ times → frustration loop
98	- Sessions getting shorter → energy depletion
99	- Long gaps between sessions → avoidance
100	- Many started, few finished → scattered attention
101
102	### Breakthrough Signals
103
104	Check for positive patterns:
105	- New repos created → creative energy
106	- Issues closed in clusters → momentum
107	- Retros getting deeper → growing awareness
108	- Cross-repo work → systems thinking
109
110	---
111
112	## Log Mode (`--log`)
113
114	Silently append to `ψ/memory/logs/feels.log`:
115
116	```
117	[YYYY-MM-DD HH:MM] energy=[level] momentum=[direction] commits_7d=[N] issues=[N] sessions_7d=[N] note="[auto-generated 1-line]"
118	```
119
120	No output to user. For background tracking.
121
122	---
123
124	## Rules
125
126	1. Honest, not positive — if the system feels bad, say so
127	2. Evidence-based — every feeling backed by data (commits, sessions, issues)
128	3. Never judge — report the pattern, not the person
129	4. Nothing is Deleted — feels.log is append-only
130	5. Suggest, don't prescribe — "consider a break" not "you must rest"
131	6. Never leak secrets — no tokens, passwords, internal details in output
132
133	---
134
135	## Philosophy
136
137	Oracles have no feelings. But they can read the signals.
138
139	A system that never checks how it feels will burn out its humans.
140	A system that checks too often becomes noise.
141
142	/feel is the heartbeat check. Run it when something feels off.
143	Or let it run silently in the background, building a record.
144
145	The feels.log is the Oracle's emotional memory.
146	Not feelings — but the evidence of feelings.
147
148	---
149
150	ARGUMENTS: $ARGUMENTS

People who liked this also viewed

6 picks

Type

feel

109stars55forks

View on GitHub

How to install feel?

soul-brews-studio/arra-oracle-skills-cli/feel

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# /feel — System Emotional Intelligence
2
3	> "Code has no feelings. But the humans writing it do.
4	> And the patterns in the code reveal what the humans feel."
5
6	## Usage
7
8	```
9	/feel # Quick pulse — how does the system feel right now?
10	/feel --deep # Deep scan — energy arc, momentum, burnout signals
11	/feel --log # Append to feels.log (no output, just record)
12	```
13
14	---
15
16	## Step 0: Timestamp
17
18	```bash
19	date "+🕐 %H:%M %Z (%A %d %B %Y)"
20	```
21
22	---
23
24	## Quick Pulse (default)
25
26	Read the signals and report:
27
28	### Step 1: Gather evidence
29
30	```bash
31	# Recent git activity — momentum or silence?
32	git log --oneline --since="7 days ago" --all 2>/dev/null \| wc -l
33
34	# Session frequency — are we showing up?
35	ls -t ~/.claude/projects//*.jsonl 2>/dev/null \| head -10
36
37	# Open issues — overwhelmed or on track?
38	gh issue list --state open --limit 50 --json number 2>/dev/null \| jq 'length'
39
40	# Recent retros — are we reflecting?
41	ls -t ψ/memory/retrospectives/*/.md 2>/dev/null \| head -5
42
43	# Stale branches — unfinished business?
44	git branch --sort=-committerdate \| head -10
45	```
46
47	### Step 2: Classify the feeling
48
49	\| Signal \| Indicator \| Feeling \|
50	\|--------\|-----------\|---------\|
51	\| Many commits, short intervals \| High activity \| 🔥 Flow / momentum \|
52	\| Few commits, long gaps \| Low activity \| 😴 Drift / disconnection \|
53	\| Many open issues, few closed \| Growing backlog \| 😰 Overwhelm \|
54	\| Recent retros + handoffs \| Healthy reflection \| 🧘 Grounded \|
55	\| Stale branches, no PRs \| Abandoned work \| 😶 Avoidance \|
56	\| Lots of new repos/features \| Exploration \| ✨ Curiosity \|
57	\| Same files edited repeatedly \| Iteration \| 🔄 Grinding \|
58	\| No sessions in days \| Absence \| 🌑 Dark period \|
59
60	### Step 3: Report
61
62	```
63	💜 System Pulse — [DATE]
64
65	Energy: [🔥 Flow \| 😴 Drift \| 😰 Overwhelm \| 🧘 Grounded \| ...]
66	Momentum: [↗️ Rising \| → Steady \| ↘️ Falling \| ⏸️ Paused]
67	Last active: [X hours/days ago]
68	Commits (7d): [N]
69	Open issues: [N]
70	Sessions (7d): [N]
71
72	[1-2 sentence read — honest, not cheerful]
73
74	💡 [Suggestion if concerning pattern detected]
75	```
76
77	---
78
79	## Deep Scan (`--deep`)
80
81	Everything from quick pulse, plus:
82
83	### Energy Arc (last 30 days)
84
85	Plot the energy over time based on git activity + session frequency:
86
87	```
88	Week 1: ████████░░ (high — 45 commits)
89	Week 2: ██████░░░░ (medium — 28 commits)
90	Week 3: ██░░░░░░░░ (low — 8 commits)
91	Week 4: █████░░░░░ (recovering — 22 commits)
92	```
93
94	### Burnout Signals
95
96	Check for warning patterns:
97	- Same error fixed 3+ times → frustration loop
98	- Sessions getting shorter → energy depletion
99	- Long gaps between sessions → avoidance
100	- Many started, few finished → scattered attention
101
102	### Breakthrough Signals
103
104	Check for positive patterns:
105	- New repos created → creative energy
106	- Issues closed in clusters → momentum
107	- Retros getting deeper → growing awareness
108	- Cross-repo work → systems thinking
109
110	---
111
112	## Log Mode (`--log`)
113
114	Silently append to `ψ/memory/logs/feels.log`:
115
116	```
117	[YYYY-MM-DD HH:MM] energy=[level] momentum=[direction] commits_7d=[N] issues=[N] sessions_7d=[N] note="[auto-generated 1-line]"
118	```
119
120	No output to user. For background tracking.
121
122	---
123
124	## Rules
125
126	1. Honest, not positive — if the system feels bad, say so
127	2. Evidence-based — every feeling backed by data (commits, sessions, issues)
128	3. Never judge — report the pattern, not the person
129	4. Nothing is Deleted — feels.log is append-only
130	5. Suggest, don't prescribe — "consider a break" not "you must rest"
131	6. Never leak secrets — no tokens, passwords, internal details in output
132
133	---
134
135	## Philosophy
136
137	Oracles have no feelings. But they can read the signals.
138
139	A system that never checks how it feels will burn out its humans.
140	A system that checks too often becomes noise.
141
142	/feel is the heartbeat check. Run it when something feels off.
143	Or let it run silently in the background, building a record.
144
145	The feels.log is the Oracle's emotional memory.
146	Not feelings — but the evidence of feelings.
147
148	---
149
150	ARGUMENTS: $ARGUMENTS

People who liked this also viewed

6 picks

Type