claudikins-tool-executor

!Claudikins Marketplace

<p align="center"> <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-blue.svg" alt="License: MIT"></a> <img src="https://img.shields.io/badge/Plugins-5-green.svg" alt="5 Plugins"> <img src="https://img.shields.io/badge/Maintained-Yes-brightgreen.svg" alt="Maintained"> </p>

Claudikins Marketplace

A complete toolkit for Claude Code.

<details> <summary><strong>Table of Contents</strong></summary>

• •Quick Install
• •Plugin Ecosystem
• •Prerequisites
• •Getting Started
• •Plugins
• •Kernel
• •Tool Executor
• •GRFP
• •klaus
• •ACM
• •Recommended Combinations
• •License

</details>

Quick Install

1. Run /plugins in Claude Code
2. Select Marketplaces > Add Marketplace
3. Enter elb-pr/claudikins-marketplace
4. Select which plugins you want to install

Plugin Ecosystem

%%{init: {'flowchart': {'curve': 'linear'}}}%%
flowchart TB
    subgraph core[" "]
        kernel["kernel<br/>(workflow)"]
    end

    toolexec["tool-executor<br/>(infrastructure)"]
    grfp["grfp<br/>(documentation)"]
    klaus["klaus<br/>(debugging)"]
    acm["acm<br/>(context)"]

    kernel -.->|recommended| toolexec
    kernel -.->|recommended| klaus
    toolexec -->|enhances| grfp
    toolexec <-->|synergy| acm

    acm -.->|enhances| kernel
    acm -.->|enhances| toolexec
    acm -.->|enhances| grfp
    acm -.->|enhances| klaus

    style kernel fill:#e74c3c,stroke:#c0392b,color:#fff
    style toolexec fill:#2c3e50,stroke:#1a252f,color:#fff
    style grfp fill:#9b59b6,stroke:#7b39a6,color:#fff
    style klaus fill:#e91e63,stroke:#c2185b,color:#fff
    style acm fill:#e65100,stroke:#bf360c,color:#fff

kernel is the recommended starting point - it orchestrates the full development workflow. tool-executor provides MCP infrastructure that enhances grfp's Gemini integration. acm preserves context across all plugins. klaus pairs well with kernel for debugging sessions.

Prerequisites

Claude Code is required for all plugins (latest version recommended).

Getting Started

Choose your path based on what you want to accomplish.

Everything

For: Users who want the full toolkit.

Install: Select all plugins from the marketplace.

What you get: All 5 plugins - kernel (workflow), tool-executor (MCP infrastructure), grfp (documentation), klaus (debugging), and acm (context preservation).

Full Development Workflow

For: Users who want structured planning, execution, and shipping.

Install: claudikins-kernel, claudikins-tool-executor, claudikins-automatic-context-manager

What you get: 4-command pipeline (plan, execute, verify, ship), MCP tool access without context bloat, and automatic context preservation for long sessions.

Documentation Focus

For: Users who want high-quality READMEs.

Install: claudikins-grfp, claudikins-tool-executor

What you get: 5-phase README pipeline (deep-dive, crystal-ball, brain-jam, think-tank, pen-wielding) with Gemini-powered research and creative brainstorming.

Debugging Sessions

For: Users tackling hard bugs.

Install: claudikins-klaus, claudikins-automatic-context-manager

What you get: 8-phase systematic debugging methodology, plus context preservation for long debugging sessions.

Plugins

Kernel

!claudikins-kernel

Repository: claudikins-kernel

Four commands that enforce quality through gates:

• •/claudikins:kernel-plan - Iterative requirements gathering, parallel research agents, multiple approaches with trade-offs, section-by-section drafting
• •/claudikins:kernel-execute - Tasks run in isolated git branches with fresh context. Two-stage review: spec compliance first, code quality second
• •/claudikins:kernel-verify - Runs your code and watches it work. The catastrophiser agent observes actual output, not just test results
• •/claudikins:kernel-ship - Documentation updates via GRFP methodology, commit message drafting, PR creation with human approval at every stage

Cross-command gates prevent skipping steps. State persists to JSON for session resume. File hashes ensure you ship what you verified.

Works best with: tool-executor (MCP access), klaus (debugging), acm (context preservation). Kernel is recommended for all plugins.

Tool Executor

!claudikins-tool-executor

Repository: claudikins-tool-executor

MCP tools eat context. A typical setup with 5-6 servers burns 25% of your context window just listing available tools.

Tool Executor wraps multiple MCP servers behind three tools:

• •search_tools - Semantic search across all registered servers
• •get_tool_schema - Fetch full schema only when needed
• •execute_code - Sandboxed TypeScript runtime with access to MCP clients and a persistent workspace API

Context usage drops to 0.5%. Large responses auto-save to workspace. You get the tools without the bloat.

Works best with: kernel (workflow orchestration), grfp (Gemini access), acm (synergy - context efficiency meets preservation).

GRFP

!claudikins-grfp

Repository: claudikins-grfp

Five phases. Two AIs. One README that reads like a human wrote it.

1. Deep-dive - Extract facts from the codebase: tech stack, entry points, dependencies, friction points
2. Crystal-ball - Identify what the project could become: performance opportunities, feature gaps, technical debt
3. Brain-jam - Multi-turn conversation with Gemini to find the right angle and voice
4. Think-tank - Gemini deep research on exemplar READMEs, pattern extraction, anti-pattern identification
5. Pen-wielding - Section-by-section writing with anti-slop filtering and style enforcement

Claude handles analysis and writing. Gemini runs deep research and creative brainstorming. The pipeline enforces quality at every stage.

Works best with: tool-executor (strongly recommended for Gemini MCP access). Can run standalone but benefits significantly from tool-executor.

klaus

!claudikins-klaus

Repository: claudikins-klaus

For when you are truly, catastrophically doomed.

klaus is a dramatically irritated debugging persona with Eastern European flair. He fixes your code while narrating an imaginary Pong championship match against you. Every bug you create scores him a point. Every fix you accept scores you one.

The persona is absurd. The methodology is rigorous:

8 systematic phases covering hypothesis formation, evidence gathering, isolation testing, and root cause analysis. klaus applies extreme rigour while lamenting your life choices and celebrating his Pong dominance.

Works best with: kernel (debugging companion for kernel workflows), acm (preserves progress in long sessions). Recommended for kernel users.

ACM

!claudikins-automatic-context-manager

Repository: claudikins-automatic-context-manager

Context fills up. Work gets lost. Sessions end mid-task.

ACM monitors context usage and triggers at a configurable threshold (default 60%). When triggered, it generates a structured handoff summary:

• •Current task state
• •Decisions made and why
• •Files modified
• •Next steps to continue

New session loads the summary and picks up where you left off. Configurable threshold, snooze duration, and summary length. Works alongside other plugins without conflict.

Works best with: All plugins - ACM enhances everything by preserving context across sessions. Particularly strong synergy with tool-executor.

<details> <summary><strong>Recommended Combinations</strong></summary>

Full workflow coverage: kernel + tool-executor + acm

Kernel handles the development lifecycle. Tool-executor keeps MCP tools from eating context. ACM saves your work when context fills.

Documentation focus: grfp + tool-executor

GRFP uses Gemini for deep research. Tool-executor provides the MCP access.

Debugging sessions: klaus + acm

klaus for the hard problems. ACM to preserve progress when the session runs long.

</details>

License

MIT