/feedback
Send feedback, ideas, or bug reports about Claudia. Opens a pre-filled GitHub Discussion with system context. Use when user says "feedback", "suggestion", "report a bug", "feature request", or "I have an idea".
$ npx -y skills add kbanc85/claudia --skill feedback --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/feedback
Context preview
The summary Claude sees to decide when to auto-load this skill.
Send feedback, ideas, or bug reports about Claudia. Opens a pre-filled GitHub Discussion with system context. Use when user says "feedback", "suggestion", "report a bug", "feature request", or "I have an idea".
SKILL.md
feedback.SKILL.mdname: feedback
description: Send feedback, ideas, or bug reports about Claudia. Opens a pre-filled GitHub Discussion with system context. Use when user says "feedback", "suggestion", "report a bug", "feature request", or "I have an idea".
effort-level: low
Claudia Feedback
Help users share feedback, ideas, bug reports, or feature requests about Claudia. Opens a GitHub Discussion with auto-populated system info so the user just writes their message.
Trigger Phrases
- "feedback", "give feedback", "send feedback"
- "I have a suggestion", "feature request", "idea for Claudia"
- "report a bug", "something's broken", "I found a bug"
- "how do I report an issue"
Process
Step 1: Ask What's On Their Mind
Ask the user what kind of feedback they want to share. Keep it casual:
- "What's on your mind? Bug, idea, or just general feedback?"
If they've already described it, skip this step.
Step 2: Gather System Context
Collect system info silently (don't show raw data to user). Run these:
# Version
cat package.json 2>/dev/null | grep '"version"' | head -1
# OS and Node
echo "$(uname -s) $(uname -m), Node $(node -v 2>/dev/null)"
# Memory daemon health
~/.claudia/daemon/venv/bin/python3 -m claudia_memory --preflight 2>&1 | grep "Result:" || echo "Daemon: not checked"
# Memory count
sqlite3 ~/.claudia/memory/claudia.db "SELECT COUNT(*) FROM memories WHERE invalidated_at IS NULL;" 2>/dev/null || echo "0"
Step 3: Categorize
Map their feedback to a GitHub Discussions category:
| Feedback Type | Category | |--------------|----------| | Bug report | Ideas (no Bugs category by default) | | Feature request / idea | Ideas | | General feedback | General | | Question | Q&A |
Step 4: Build the Discussion URL
Construct a pre-filled GitHub Discussion URL. The URL format:
https://github.com/kbanc85/claudia/discussions/new?category={CATEGORY}&title={TITLE}&body={BODY}The body should include: 1. The user's feedback (their words, not paraphrased) 2. A "System Info" section at the bottom with the collected context
**Body template:**
{user's feedback text}
---
**System Info** (auto-generated by Claudia)
- Version: {version}
- OS: {os}
- Node: {node_version}
- Memories: {count}
- Daemon: {healthy/not running}URL-encode the title and body for the query string.
Step 5: Open in Browser
Use the Bash tool to open the URL:
# macOS
open "{url}"
# Linux
xdg-open "{url}" 2>/dev/null || echo "Open this URL: {url}"
# Windows
start "{url}"Step 6: Confirm
Tell the user:
- "Opened a new discussion in your browser. Add any details and hit Submit."
- If the browser didn't open, show the URL directly so they can copy it.
Important
- **Never post feedback without the user's knowledge.** This opens a browser for them to review and submit.
- **Don't paraphrase their feedback.** Use their exact words in the body.
- **Keep system info minimal.** Version, OS, memory count. No sensitive data, no file paths, no personal info.
- **The user submits, not Claudia.** The browser opens a pre-filled form. The user reviews and clicks Submit.
GitHub Discussions URL
Repository: `kbanc85/claudia`
Direct link to create a discussion: `https://github.com/kbanc85/claudia/discussions/new`
Read more
name: feedback description: Send feedback, ideas, or bug reports about Claudia. Opens a pre-filled GitHub Discussion with system context. Use when user says "feedback", "suggestion", "report a bug", "feature request", or "I have an idea". effort-level: low
Claudia Feedback
Help users share feedback, ideas, bug reports, or feature requests about Claudia. Opens a GitHub Discussion with auto-populated system info so the user just writes their message.
Trigger Phrases
- "feedback", "give feedback", "send feedback"
- "I have a suggestion", "feature request", "idea for Claudia"
- "report a bug", "something's broken", "I found a bug"
- "how do I report an issue"
Process
Step 1: Ask What's On Their Mind
Ask the user what kind of feedback they want to share. Keep it casual:
- "What's on your mind? Bug, idea, or just general feedback?"
If they've already described it, skip this step.
Step 2: Gather System Context
Collect system info silently (don't show raw data to user). Run these:
# Version cat package.json 2>/dev/null | grep '"version"' | head -1 # OS and Node echo "$(uname -s) $(uname -m), Node $(node -v 2>/dev/null)" # Memory daemon health ~/.claudia/daemon/venv/bin/python3 -m claudia_memory --preflight 2>&1 | grep "Result:" || echo "Daemon: not checked" # Memory count sqlite3 ~/.claudia/memory/claudia.db "SELECT COUNT(*) FROM memories WHERE invalidated_at IS NULL;" 2>/dev/null || echo "0"
Step 3: Categorize
Map their feedback to a GitHub Discussions category:
| Feedback Type | Category | |--------------|----------| | Bug report | Ideas (no Bugs category by default) | | Feature request / idea | Ideas | | General feedback | General | | Question | Q&A |
Step 4: Build the Discussion URL
Construct a pre-filled GitHub Discussion URL. The URL format:
https://github.com/kbanc85/claudia/discussions/new?category={CATEGORY}&title={TITLE}&body={BODY}The body should include: 1. The user's feedback (their words, not paraphrased) 2. A "System Info" section at the bottom with the collected context
**Body template:**
{user's feedback text}
---
**System Info** (auto-generated by Claudia)
- Version: {version}
- OS: {os}
- Node: {node_version}
- Memories: {count}
- Daemon: {healthy/not running}URL-encode the title and body for the query string.
Step 5: Open in Browser
Use the Bash tool to open the URL:
# macOS
open "{url}"
# Linux
xdg-open "{url}" 2>/dev/null || echo "Open this URL: {url}"
# Windows
start "{url}"Step 6: Confirm
Tell the user:
- "Opened a new discussion in your browser. Add any details and hit Submit."
- If the browser didn't open, show the URL directly so they can copy it.
Important
- **Never post feedback without the user's knowledge.** This opens a browser for them to review and submit.
- **Don't paraphrase their feedback.** Use their exact words in the body.
- **Keep system info minimal.** Version, OS, memory count. No sensitive data, no file paths, no personal info.
- **The user submits, not Claudia.** The browser opens a pre-filled form. The user reviews and clicks Submit.
GitHub Discussions URL
Repository: `kbanc85/claudia`
Direct link to create a discussion: `https://github.com/kbanc85/claudia/discussions/new`
Terminal-based AI chief of staff. Remembers relationships, tracks commitments, helps you think strategically. Runs on Claude Code.
Repo: kbanc85/claudia
Other skills on claudia.
- /auto-research
Iteratively improve a local artifact (draft, document, page) by running a hill-climbing loop. The user names the artifact, the evaluator, and the budget. Claudia edits the artifact, scores it, keeps it if better or reverts if worse, repeats. Use when user says "iterate on this",
Open skill - /brain-monitor
Launch the Brain Monitor TUI, a real-time terminal dashboard for watching Claudia's memory system. Triggers on "brain monitor", "show dashboard", "memory dashboard", "terminal brain". See also: `brain` for a 3D graph view in the browser.
Open skill - /brain
Launch the Brain Visualizer, a real-time 3D view of memory and relationships. Triggers on "show your brain", "visualize memory", "open the brain", "memory graph". See also: `brain-monitor` for a terminal dashboard alternative.
Open skill - /build-team
Propose a personalized team of specialized agents based on the user's profile, goals, and how they actually work. Runs the proposal through an independent Checker, gates on the user's approval, and applies with rollback. Use when the user says "build my team", "set up my
Open skill - /capture-meeting
Process meeting notes or transcript to extract decisions, commitments, and insights. Use when user shares transcript or says "capture this meeting", "here are my notes from the call". See also: `meeting-prep` for pre-call briefings; `follow-up-draft` for post-meeting emails.
Open skill - /client-health
Health check across active client engagements showing status, deliverables, and concerns. Triggers on "how are my clients?", "client status", "client health check".
Open skill

