sgaunet /claude-plugins
Plugin Claude Code
Bundles 1 skill, 1 agent, 1 MCP server · 32 tokens together
Production-quality bash scripting with shellcheck compliance, robust error handling, and beautiful terminal UX via Charmbracelet gum. Skills: gum-beautify (TTY-safe interactive output). MCP: context7.
★ not rated 16
changed 21d ago A
tokens not measured
original MIT sgaunet /claude-plugins
Plugin Claude Code
Bundles 1 skill, 5 agents · 195 tokens together
Infrastructure as Code (Terraform, Ansible, CloudFormation), CI/CD pipelines (GitHub Actions, GitLab CI, Forgejo Actions via fgj), and database specialists (PostgreSQL, MySQL) for DevOps workflows. Skills: analyze-db-performance (PostgreSQL query and index analysis).
★ not rated 16
changed 21d ago A
tokens not measured
original MIT sgaunet /claude-plugins
Plugin Claude Code
Bundles 11 skills, 1 agent · 389 tokens together
Master Go 1.25+ development with modern patterns, advanced concurrency, performance optimization, and production-ready microservices. Skills: gen-forgejo-dir, gen-github-dir, gen-gitlab-ci, gen-goreleaser, gen-linter, gen-taskfiles, go-blackbox, go-bulma, go-structure, go-tdd, go-tool. MCP: context7.
★ not rated 16
changed 21d ago A
tokens not measured
original MIT sgaunet /claude-plugins
Plugin Claude Code
Bundles 18 skills, 7 agents · 705 tokens together
Code review, debugging, documentation, license compliance (AGPL/MIT/Apache), payment integration (Stripe/PayPal), frontend development (HTMX/Alpine.js), architecture diagrams (d2 via diagram-architect + /gen-diagram), and terminal demo GIFs (VHS via /gen-vhs-demo). Skills: analyze-and-create-issue, analyze-pr…
★ not rated 16
changed 21d ago A
tokens not measured
original MIT sgaunet /gitlab-mcp
MCP server Claude Code Codex Cursor +2
MCP server "docker-gitlab-mcp-server" as configured in sgaunet/gitlab-mcp. Runs in Docker (ghcr.io/sgaunet/gitlab-mcp:latest).
★ not rated 4 11d ago A
tokens not measured
original MIT At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: