By thoeltig
Comprehensive management of Claude Code features including skills, slash commands, hooks, MCPs, subagents, and prompts. Create, analyze, and improve Claude Code capabilities with official documentation guidance.
Creates, analyzes, updates, and improves Claude Code agent skills including YAML frontmatter, allowed-tools field, progressive disclosure, and skill authoring workflows. Use when user asks how skills work, what agent skills are, explaining skill concepts, understanding SKILL.md structure, describing .md files organization, skill authoring process, asked to create a new skill, evaluate existing skills for improvements, optimize skills for AI/Claude effectiveness, suggest converting current logic into a skill, update outdated skill information, or when user mentions skill validation, best practices, supporting files, skill security, API integration, or technical architecture.
Creates, analyzes, updates, and improves Claude Code hooks including configuration, scripts, and security validation. Use when user asks how hooks work, explaining hook concepts, understanding hook types and event lifecycle, describing hook configuration, creating new hooks, analyzing existing hooks for improvements, validating hook security, debugging hook activation, updating hook configurations, or when user mentions "hook", "PreToolUse", "PostToolUse", "SessionStart", or other hook event types. Handles both command hooks and prompt-based hooks across all 9 event types.
Creates, analyzes, updates, and evaluates Model Context Protocol (MCP) servers including architecture assessment, security validation, and connection configuration. Use when user asks if current context or logic should be MCP, requests MCP creation/improvement/update, mentions MCP is outdated, or asks how MCPs work, what MCPs are, explaining MCP concepts, understanding MCP architecture, protocol specification, server implementation, client integration, or connecting MCP servers to Claude Code.
Creates, packs, bundles, and manages Claude Code plugins with manifest generation, directory structure, marketplace configuration. Use when user asks how plugins work, what plugins are, explaining plugin structure, understanding plugin.json manifest, describing plugin bundling process, creating plugins, bundling skills/commands/hooks/MCPs, generating plugin.json, setting up marketplaces, or distributing team-shared functionality.
Creates, analyzes, updates, and optimizes prompts using Claude 4.5 best practices, guardrails, context management, and prompt engineering patterns. Use when user asks how to write effective prompts, explaining prompt engineering techniques, understanding Claude 4.5 best practices, describing prompt patterns and structures, creating new prompts, evaluating existing prompts for improvements, determining if current logic should be extracted to prompts, identifying outdated prompt techniques, optimizing context usage, implementing guardrails, or when user mentions "prompt engineering", "hallucinations", "context optimization", "prompt caching", "chain-of-thought", or asks if logic should become a prompt.
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.
A Claude Code marketplace that cuts token costs, preserves context across sessions, and extends Claude with intelligent project exploration, workflow automation, and development standards.
Add this marketplace to your Claude Code configuration:
# Add the marketplace (replace with actual installation command)
/marketplace add https://github.com/thoeltig/claude-code-toolkit
Then install any plugin:
/plugin install <plugin-name>@claude-code-toolkit
| Plugin | Description | Version |
|---|---|---|
| smart-compact | Remove duplicate file reads and script outputs from transcripts to reduce token waste, lower hallucination risk, and preserve context priority when resuming sessions | 2.2.3.0 |
| project-intel | Lightweight reconnaissance system that provides semantic direction before code exploration with persistent knowledge across sessions | 1.6.0.0 |
| read-efficient | Machine-efficient file reading tool that converts files to compact JSON and removes redundant whitespace, saving 30-70% tokens across 10+ formats | 1.1.1.0 |
| fetch-full-content | Download full page content from URLs to markdown for complete information retrieval without summarization (⚠️ trusted sources only) | 1.2.1.0 |
| session-protocol | Save your active tasks between sessions and never loss context again | 1.2.0.0 |
| changelog | Create, update, and maintain CHANGELOG.md files following Keep a Changelog and Common Changelog standards | 1.1.0.0 |
| documentation | Create and maintain high-quality project documentation with quality validation, style guides, and inclusive language standards | 1.0.0.0 |
| claude-code-capabilities | Comprehensive management of Claude Code features including skills, commands, hooks, prompts, subagents, and MCPs | 1.8.0.0 |
| cross-platform-notification | Send native system notifications for Claude Code hook events across Windows, macOS, and Linux | 1.0.0.0 |
During development you naturally read the same file to keep important context "fresh" (higher priority) or execute the same bash script with the same output multiple times. These fill the conversation with outdated content which the LLM needs to process everytime a new message is added. Also when resuming a session Claude Code reconstructs the entire conversation from the transcript including all file reads which waste tokens without adding new information.
This plugin automatically deduplicates as your session ends, removing redundant reads using intelligent forward-chaining:
The cleaned transcript benefits every future resume—lower cost, reduced hallucination risk from context bloat.
Install: /plugin install smart-compact@claude-code-toolkit
Lightweight reconnaissance system that provides semantic direction before expensive code exploration. Query first to get a ranked list of relevant files - saves exploration tokens and reduces context pollution.
npx claudepluginhub thoeltig/claude-code-toolkit --plugin claude-code-capabilitiesBenchmarking framework to analyse tokenization per file format.
Download and cache full page content from URLs for complete information retrieval without summarization loss. Removes only simple hidden content but has NO prompt injection detection or guard. Should only be used on official and trusted sources like documentations.
Lightweight reconnaissance system that provides direction before exploration. Query for relevant files before reading them - avoid expensive blind exploration and context pollution.
Batch file I/O for Claude Code — read N files and run M edits per call, cutting tool calls and context overhead by ~50–60%.
Remove duplicate file reads and script outputs from Claude Code transcripts to reduce token waste and lower hallucination risk when resuming sessions.
Core skills: ecosystem guide, skill creator, research patterns, session reflection, and plugin development. Includes UserPromptSubmit hook for forced skill evaluation.
Commands for loading context and priming Claude for specific tasks
Commands for syncing CLAUDE.md, permissions allowlist, and refreshing context. Hooks for marketplace-to-plugin sync.
Non-technical progress summaries for Claude Code work (hides diffs/log noise).
Skill and agent authoring tools: generate, audit, and improve Claude Code skills, commands, and agents
Curate auto-memory, promote learnings to CLAUDE.md and rules, extract proven patterns into reusable skills.