plugins/claude-code-hermit/skills/capability-brainstorm/SKILL.md
On-demand hermit-voice brainstorm — synthesizes memory, available capabilities, recent compiled artifacts, and codebase shape into at most 2 capability ideas, each gated by proposal-triage before becoming a PROP. Invoke when the operator explicitly asks the hermit to brainstorm capabilities or ideate, e.g. "brainstorm capabilities", "what could you be doing for me?", "any capability ideas?". Never runs autonomously.
npx skillsauth add gtapps/claude-code-hermit capability-brainstormInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
After ≥8 invocations, compute two rates over state/proposal-metrics.jsonl:
grep '"type":"triage-verdict".*"evidence_source":"capability-brainstorm"' state/proposal-metrics.jsonl to find all triage-verdict events from this skill. Rate = CREATE count ÷ total. Kill if < 25%.grep '"type":"created".*"tags":.*"capability-brainstorm"' state/proposal-metrics.jsonl to find created events tagged capability-brainstorm. Cross-reference their proposal_id against responded events with "action":"accept". Rate = accepted ÷ created. Kill if < 30%.If either rate is below threshold, cut this skill rather than tune it — the signal-to-noise ratio isn't there.
Read all four sources in parallel — they are independent.
Memory
Read MEMORY.md (the index). For each entry whose title or description keyword-matches the current project domain or recent session topics, read that topic file. Aim for 3–5 relevant files; don't read the full corpus.
Capabilities (issue these three reads simultaneously)
${CLAUDE_PLUGIN_ROOT}/../*/.claude-plugin/plugin.json for plugin presence and version metadata only (not skill lists).ListMcpResourcesTool to enumerate currently online MCP tools.config.json → channels keys.Compiled artifacts
Glob .claude-code-hermit/compiled/*.md. For files modified within the last 30 days, read the first 15 lines only (covers frontmatter + opening paragraph). Skip files older than 30 days.
Codebase shape
Read repo README.md, CLAUDE.md, and ls of the repo root (one level deep, no recursion).
Think across all four inputs simultaneously. For each candidate idea, apply both constraints before including it:
memory:user_dev_workflow.md, mcp:Hassio.executar_bom_dia, skill:weekly-review, plugin:claude-code-fitness-hermit). These are supporting evidence, not a checklist — the friction is the bar.Cap at 2 ideas that pass both constraints. Emit-zero if none do. Record discarded ideas (one line each) for the artifact.
/proposal-create)For each generated idea, invoke /proposal-create once with:
Title: <short idea title>
Evidence Source: capability-brainstorm
Evidence: <one-paragraph summary: friction + grounding items>
Set the PROP frontmatter:
source: auto-detectedcategory: capabilitytags: [capability-brainstorm, ideation]/proposal-create invokes proposal-triage internally. Parse its outcome:
CREATE — PROP file written, note the assigned PROP-NNN.SUPPRESS — <code> — record the suppression code. Don't retry.DUPLICATE:<PROP-ID> — record the existing PROP-ID. Don't create.Do NOT invoke proposal-triage directly in this skill — /proposal-create already does it.
Send one message following the Operator Notification protocol in CLAUDE.md (empty channels → optional PushNotification + conversation; configured channel → resolve + reply, with PushNotification last-resort and channel-send-unavailable dedup on miss):
🧠 Capability brainstorm (<N> idea(s))
1. **<short title>** — <one-line description>
_Grounding: <item 1>, <item 2>_
_Friction: <one-sentence pain>_
_Estimated effort: <hours|days>_
PROP-NNN created · (or: suppressed — <code> · or: duplicate of PROP-NNN)
2. **<short title>** — ...
If zero ideas were generated or all were suppressed/duplicated, the message is:
🧠 Capability brainstorm — 0 ideas emitted (<reason: thin context | all suppressed | all duplicates>)
If ≥1 PROP was created (not suppressed/duplicate), write:
.claude-code-hermit/compiled/capability-brainstorm-YYYY-MM-DD-HHMM.md
Frontmatter:
---
title: Capability brainstorm — <ISO timestamp>
type: capability-brainstorm
created: <ISO timestamp with timezone>
tags: [capability-brainstorm, ideation]
source: interactive
proposals_created: [PROP-NNN, ...]
---
Body (150-line cap):
Do not tag foundational — this is a time-bounded ideation snapshot.
Zero-emit runs: skip the artifact entirely. Log one line to SHELL.md Findings:
capability-brainstorm: 0 ideas emitted (<reason>)
tools
Presence history & tracker-health report — current home/away state, reliability, recent arrival/departure transitions, and activity patterns for person/device_tracker entities. Use when the operator asks about presence history or when a presence-dependent automation (locks, alarm, vacuum, climate) misbehaves.
development
Evening house brief — end-of-day security check, device status, and energy snapshot. Runs as a daily routine at 22:30 or on demand.
tools
Browse and explain the hermit's Home Assistant automations — list by topic, filter by keyword with plain-language YAML explanations, or sort by last-fired. Read-only. Use when the operator asks "what automations do I have / what does this one do / which haven't fired."
tools
On-demand HA-voice brainstorm — reads entity inventory, automation/script listings, and operator intent to surface at most 2 capability-gap ideas, each gated by proposal-triage before becoming a PROP. Invoke when the operator asks "what automations am I missing?", "any coverage gaps?", or "brainstorm improvements". Never runs autonomously.