Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub espalier-redoubt/claudikins-marketplace --plugin claudikins-klausCore planning and workflow infrastructure for the Claudikins ecosystem
Configurable MCP wrapper that consolidates your tools into just 3, using semantic search for on-demand discovery and sandboxed TypeScript execution. Ships with 7 example servers (96 tools) - reduces context consumption by 97% (48k tokens down to 1.1k).
Configurable MCP wrapper that consolidates your tools into just 3, using semantic search for on-demand discovery and sandboxed TypeScript execution. Ships with 7 example servers (96 tools) - reduces context consumption by 97% (48k tokens down to 1.1k).
Claudikins Automatic Context Manager - seamless context handoff for Claude Code
Claudikins Automatic Context Manager - seamless context handoff for Claude Code
Systematic debugging and root cause analysis framework - four-phase investigation process ensuring understanding before fixes
Opt-in productivity coaching for Claude Code. Use for explicit PUA/try-harder requests, user frustration after repeated failures, requests to retry or change approach, passive/low-quality work complaints, completion checks, evidence requests, test/verification reminders, and Ding-style workplace process cues. Normal calm first-attempt requests are left alone.
Debug issues systematically with root cause analysis and execution tracing
Ask Claude Code to help you debug an issue
Debugging, explanation, and code review skills for when things go sideways.
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.