am2rican5:self-improve
Run a self-improvement cycle that analyzes Claude Code usage patterns and applies targeted improvements to CLAUDE.md, hooks, and skills. Audits current setup, identifies gaps from usage data, and proposes grouped changes with rationale. Use when user says "improve my setup", "self-improve", "optimize my Claude config", "fix my workflow", or after running /insights and wanting to act on the results. Do NOT use for general Claude Code help, configuration questions, or manual editing of individual files.
What this skill does
# Self-Improve Workflow ## Critical Rules - NEVER apply changes without explicit user approval - NEVER add language-specific rules to global CLAUDE.md unless the user confirms their stack - NEVER remove existing rules without explaining why - Prefer editing existing files over creating new ones - Keep CLAUDE.md under 200 lines — link to separate files for detail - Every rule must be trigger-action format: WHEN X, DO Y ## Instructions ### Step 1: Load Report 1. IF `$ARGUMENTS` contains a file path, read that report file 2. OTHERWISE, check for an existing report at `~/.claude/usage-data/report.html` 3. IF no report exists, tell the user: "No usage report found. Run `/insights` first to generate one, then re-run `/self-improve`." and **stop**. Extract from the report: - Friction points and failure patterns - Interaction style analysis - What's working vs what's hindering - Specific suggestions from the report ### Step 2: Audit Current Setup Read these files to understand the current configuration: - `~/.claude/CLAUDE.md` (global rules) - `~/.claude/settings.json` (hooks, permissions, plugins) - Any project-level `.claude/CLAUDE.md` in the current working directory - All files in `~/.claude/hooks/` - All files in `~/.claude/skills/` Compare the current setup against the report findings. Identify gaps: what problems from the report are NOT addressed by existing rules, hooks, or skills? ### Step 3: Propose Improvements Present a numbered list of proposed changes, grouped by type: **CLAUDE.md Rules:** - New trigger-action rules that address identified friction - Rules to remove or update if they're stale or counterproductive - Keep rules language-agnostic unless working in a project with a specific stack **Hooks:** - New hooks to enforce behaviors that rules alone can't guarantee - Changes to existing hooks that aren't working **Skills:** - New skills to encode repeated multi-step workflows - Changes to existing skills **Workflow Changes:** - Prompt patterns or habits to adopt - Session management improvements For each proposed change, state: - **WHAT**: The exact change - **WHY**: Link to specific report finding - **CONTENT**: The exact text/code to write ### Step 4: Apply with Confirmation WAIT for user to approve, reject, or modify each proposed change. - Present changes one group at a time (CLAUDE.md, then hooks, then skills) - For each group, ask the user which items to apply - Apply only approved changes - After applying, summarize what was changed and what was skipped ## Examples ### Example 1: Post-insights improvement User says: "I just ran /insights, now improve my setup" Actions: 1. Read report from `~/.claude/usage-data/report.html` 2. Audit current CLAUDE.md, hooks, and skills 3. Present grouped proposals with rationale 4. Apply approved changes Result: Targeted config updates linked to actual usage patterns. ### Example 2: Using a specific report User says: "/self-improve ~/Downloads/report.html" Actions: 1. Read the specified report file 2. Same audit and proposal flow Result: Improvements based on the provided report. ## Troubleshooting ### No report found **Cause:** User hasn't run `/insights` yet. **Solution:** Tell the user to run `/insights` first, then re-run this skill. ### Report contains no actionable findings **Cause:** Usage data is too sparse or setup is already well-optimized. **Solution:** Inform the user that no changes are recommended and explain why.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.