self-improve

Audit local Claude Code configuration directories and prune redundant auto-generated skills.

Updated May 5, 2026
One-click install
npx skills add https://github.com/iani-kuli/harness_bro --skill self-improve-iani-kuli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-improve
Source: https://github.com/iani-kuli/harness_bro/tree/main/.claude/skills/curated/self-improve
Command: npx skills add https://github.com/iani-kuli/harness_bro --skill self-improve-iani-kuli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the accumulation of technical debt and configuration clutter within your Claude Code environment by auditing your local setup and suggesting actionable improvements.

Core Features & Use Cases

  • Setup Audit: Analyzes your .claude/ directory to identify unused drafts, redundant recipes, and potential performance bottlenecks.
  • Workflow Optimization: Recommends the promotion of frequently used auto-captured tool sequences into curated, reusable skills.
  • Use Case: If you have accumulated multiple manual fixes for CUDA errors, this skill will suggest consolidating them into a single, automated debugging workflow to streamline your future development.

Quick Start

Run the self-improve skill to audit your current workspace configuration and provide recommendations for cleanup and optimization.

Frequently Asked Questions about self-improve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my Claude Code workspace configuration for unused drafts and redundant recipes?

Auditing your Claude Code workspace involves analyzing your local .claude/ directory to identify unused drafts, redundant recipes, and performance bottlenecks. This process provides actionable maintenance recommendations to prune redundant auto-generated skills.

What is the process to consolidate manual fixes into reusable automated workflows?

Consolidating manual fixes into automated workflows requires monitoring system state and tool trace logs to identify frequently executed patterns. This allows you to promote repeated sequences into structured, curated workflows for future development.

How do I optimize my development environment by removing configuration clutter?

Optimizing your development environment by removing configuration clutter requires auditing your local Claude Code setup. This action identifies accumulated technical debt and suggests actionable improvements to streamline your workspace.

Does the workspace audit require any specific dependencies to analyze local Claude Code directories?

The workspace audit requires no external dependencies to analyze local Claude Code directories. It independently inspects your local .claude/ directory configuration to provide maintenance recommendations without needing additional components.

When should I clean up redundant auto-generated skills in my Claude Code environment?

You should clean up redundant auto-generated skills when your Claude Code environment accumulates technical debt and configuration clutter. Running an audit identifies these unused drafts and redundant recipes to suggest actionable improvements.