Plinde Claude Plugins
plinde-claude-plugins is a Claude Code plugin for the Build phase that bundles eleven workflow-automation plugins spanning docs, security scanning, GitHub, Kubernetes, and terminal control.
by plinde · github.com/plinde/claude-plugins
Install plinde’s eleven-plugin Claude Code collection when you want workflow automation, document conversion, security scans, and terminal or Kubernetes helpers in one repo.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install plinde-claude-plugins@plinde/claude-pluginsBuilt 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:plinde/claude-plugins") and the paste-ready config with skillselion.get_install_config("plugin:plinde/claude-plugins").
What it does
plinde-claude-plugins is a multi-plugin Claude Code repository—eleven plugins—built for workflow automation and enhanced functionality across the solo-builder journey. Keywords point to serious glue work: GitHub CLI integration, Kubernetes and Helm contexts, container security with Trivy, Kyverno policy flavor, artifact hub navigation, and Pandoc-driven document pipelines from Markdown to PDF, DOCX, and slides. Builders also get opinionated patterns for multiperspective debates, structured reviews, naming and schema discipline, and tmux or Hammerspoon-driven local control on macOS. It fits indie operators who want Claude Code to orchestrate repos, docs, and infra checks without installing a dozen separate marketplaces. Expect intermediate familiarity with shells, GitHub auth, and optionally clusters. Not a single-purpose Angular or mobile pack; it is a automation-centric plugin drawer you enable selectively per project phase.
Highlights
- Eleven Claude Code plugins in one repository focused on workflow automation and enhanced agent behavior
- Security and compliance oriented tooling keywords: Trivy scanning, Kyverno, CVE lookup, and policy-style checks
- Document and presentation pipeline support via Pandoc, PDF, DOCX, Markdown, and HTML conversion patterns
- Debate and multi-perspective subagent patterns for structured decision-making and Socratic review flows
- Terminal and desktop ergonomics: tmux multiplexer, macOS Hammerspoon/Lua hotkeys, and session timing hooks
Why builders use it
Solo builders waste time context-switching between security scanners, doc converters, GitHub CLI, and terminal multiplexers instead of driving them from one agent session.
You register one marketplace repo and enable targeted plugins so Claude Code can automate reviews, conversions, cluster checks, and structured debates from shared hooks.
At a glance
- Type - Plugin in Automation.
- Adoption - 0 installs, 6 stars, 0 votes.
FAQ
Who is plinde-claude-plugins for?
Developers and indie operators who run Claude Code daily and want bundled automation for docs, security, GitHub, and dev environments.
When should I use plinde-claude-plugins?
Use it when you are standardizing agent-side workflows—release checks, document export, policy scans, or multiperspective reviews—across build, ship, and operate work.
How do I add plinde-claude-plugins to my agent?
Add the plinde/claude-plugins repository as a Claude Code plugin marketplace source, then enable individual plugins (security, pandoc, tmux, etc.) matching your stack and credentials.
Comments
Share how you use plinde-claude-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.