Geekatron Jerry
geekatron-jerry is a Claude Code plugin for the Build phase that enforces behavior and workflow guardrails while accruing structured knowledge for multi-agent engineering work.
by geekatron · github.com/geekatron/jerry
Install geekatron-jerry when you want Claude Code to follow behavior guardrails, accrue project knowledge, and coordinate analyst/architect/researcher-style agents with tracked workflows.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install geekatron-jerry@geekatron/jerryBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:geekatron/jerry") and the paste-ready config with skillselion.get_install_config("plugin:geekatron/jerry").
What it does
geekatron-jerry is a Claude Code plugin from geekatron/jerry aimed at solo builders who outgrow ad-hoc prompts and need repeatable agent behavior. It packages guardrails for how Claude approaches work, plus knowledge accrual so decisions, findings, and task state compound instead of vanishing between threads. The catalog keywords point at multi-agent orchestration, structured processes, and role-shaped capabilities—useful when you are running several mental hats (research, architecture, implementation) through one agent session. It fits the build phase most directly as agent-tooling, but the methodology applies whenever you are solving open-ended engineering problems with tracking. With about 16 GitHub stars and one bundled plugin, it is a niche productivity layer—not a marketplace of unrelated skills, but a cohesive Jerry workflow system for Claude Code.
Highlights
- Behavior and workflow guardrails that persist across sessions
- Knowledge accrual and knowledge-management for structured work-tracking
- Multi-agent orchestration with specialized roles (analyst, architect, researcher)
- Engineering-oriented problem-solving and systems/process templates
- Single-plugin bundle from geekatron/jerry (pluginCount: 1)
Why builders use it
Solo builders lose context and repeat the same process mistakes because Claude sessions lack durable guardrails and a shared knowledge trail.
After installing Jerry, Claude follows structured workflows, specialized agent roles, and tracking so knowledge and decisions accumulate across your project.
At a glance
- Type - Plugin in AI Agents.
- Adoption - 0 installs, 16 stars, 0 votes.
FAQ
Who is geekatron-jerry for?
Solo and small-team builders using Claude Code who want structured multi-agent workflows, engineering guardrails, and persistent knowledge tracking.
When should I use geekatron-jerry?
Use it when sessions sprawl across research, architecture, and implementation and you need orchestration plus accrual instead of restarting context each time.
How do I add geekatron-jerry to my agent?
Install the geekatron/jerry Claude Code plugin from the repo bundle (1 plugin), enable it in Claude Code, and invoke Jerry workflows when starting structured agent work.
Comments
Share how you use geekatron-jerry, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.