claudikins-kernel
v1.2.0Core planning and workflow infrastructure for the Claudikins ecosystem
By elb-prLicense: MIT128 GitHub starsUpdated 6 months ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 4 skill or MCP entries
- Source updated
- Apr 22, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install claudikins-kernel for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install claudikins-kernel@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/povvo/claudikins-kernelClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.
Plugin files
├── .claude-plugin/plugin.json├── skills/brain-jam-plan/SKILL.md├── skills/git-workflow/SKILL.md├── skills/shipping-methodology/SKILL.md└── skills/strict-enforcement/SKILL.md
Included Skills4
Use when running claudikins-kernel:outline, brainstorming implementation approaches, gathering requirements iteratively, structuring complex technical plans, or facing analysis paralysis with too many options — provides iterative human-in-the-loop planning with explicit checkpoints and trade-off presentation
Use when running claudikins-kernel:execute, decomposing plans into tasks, setting up two-stage review, deciding batch sizes, or handling stuck agents — enforces isolation, verification, and human checkpoints; prevents runaway parallelization and context death
Use when running claudikins-kernel:ship, preparing PRs, writing changelogs, deciding merge strategy, or handling CI failures — enforces GRFP-style iterative approval, code integrity validation, and human-gated merges
Use when running claudikins-kernel:verify, checking implementation quality, deciding pass/fail verdicts, or enforcing cross-command gates — requires actual evidence of code working, not just passing tests
Plugin manifests1
{
"name": "claudikins-kernel",
"version": "1.2.0",
"description": "Core planning and workflow infrastructure for the Claudikins ecosystem",
"author": {
"name": "elb-pr",
"email": "[email protected]"
},
"homepage": "https://github.com/elb-pr/claudikins-kernel",
"repository": "https://github.com/elb-pr/claudikins-kernel",
"license": "MIT",
"keywords": [
"claude-code",
"planning",
"workflow",
"agents",
"claudikins"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[claudikins-kernel on Agent Plugins Marketplace](https://pluginsmp.com/plugins/claudikins-kernel)