22 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 22 plugins that match these filters.
cc-arsenal-marketplacemgiovani/cc-arsenal2
magnus-agent-skillsmagnus919/agent-skills2
agent-toolkitsoftaworks/agent-toolkit2
claude-code-skillsalirezarezvani/claude-skills1Submit the repo with .claude-plugin/marketplace.json and we list every plugin.
Submit marketplace9 project management skills with 15 Python tools: pm-skills fork-orchestrator with agentic delivery loop (deterministic 8-lane router, Jira MCP snapshot bridge to Kanban flow metrics + Monte Carlo forecasts, delegation-governance gate, /cs-pm + /cs-grill-pm + /cs-pm-loop), senior PM, scrum master, Jira expert, Confluence expert, Atlassian admin, template creator, meeting analyzer, team communications. Bundled Atlassian Remote MCP.
Collection of agent skills: Gemini API CLI, PostgreSQL, MySQL, MSSQL, Imagen, Azure DevOps, Apple Container, Telegram, Atlassian (Jira + Confluence), Google Workspace (Gmail, Calendar, Chat, Docs, Drive, Sheets, Slides), NotebookLM, Jules, Manus, Deep Research, Outline, ElevenLabs, Google TTS, Grok Build, WhatsApp (pywhats).
Complete toolkit: all 52 skills covering development, documentation, git, github, jira, code review, testing, refactoring, CI/CD, image generation, framework documentation injection, product specs, multi-agent orchestration, open-source launch prep, skill creation and improvement, and more
Claude Code skill and hooks that record your work in Jira, Linear, GitHub Issues, Trello or Vikunja
productivityInteract with Atlassian Jira from the terminal: search issues with JQL, view details, create issues, add comments, count matches with fast approximate-count, list projects, discover valid transitions, and change status. Includes a full JQL language reference (functions, operators, history predicates, date expressions, saved filters, performance tuning) plus REST auth/pagination guidance. Use when the user mentions Jira, a ticket key (e.g. PROJ-123), asks about issues, bugs, tasks, projects, or sprint work, or needs to write, debug, or optimize JQL queries. Do not use for GitHub or GitLab issue tracking, Jira site administration, or generic ticketing systems.
Use when asked to fix, build, refactor, review, verify, or release software and the work is non-trivial — including delivering a change request through planning, gates, implementation, review, verified PR, and authorized release; continuing work started elsewhere with no packet via evidence-based position assessment; or operating tracked work items in Linear, Jira, or Notion via their tooling skills. neckbeard routes the change through framing, discovery, design, implementation, review, verification, and learning — choosing the smallest *safe* intervention, proving it at the real delivery boundary, and leaving an inspectable evidence ledger. For issue-to-PR work, conditionally loads a 9-phase journey with gates and lifecycle integration. Composes specialist catalog skills rather than replacing them. Not a persona or LOC-minimizer. Do not use this skill for unrelated requests; route to the nearest named specialist.
Defect management: severity vs priority classification, bug tracker workflows on Jira, Linear, GitHub Issues and Azure DevOps, and fix confirmation. Agents (ci-defect-filer, defect-fix-verifier) turn CI failures into deduplicated tracker bugs and re-run a defect's reproduction once a fix is claimed. Distinct from qa-bug-repro, which covers reproduction, report authoring, and the weekly defect review.
operations-resilienceWork with Red Hat Developer Hub: route plugin development and overlay management, run local plugin testing with rhdh-local, and manage RHDH Jira projects across acli, GraphQL, and REST.
Turn a spec or a Jira issue into test cases in your team's format. Approve one plan, get one Excel or CSV file your TMS imports, the gaps found in the spec, and a Postman collection for APIs.
Jira CLI integration: raw jira-cli commands, JQL filtering, and scripting
Advise on USING Jira well, not operating it: make the structural call
Install, configure, secure, and troubleshoot the mcp-atlassian MCP server (sooperset/mcp-atlassian) that connects an agent to Jira/Confluence
Jira suite — drive Atlassian Jira from the terminal with `jira` (ankitpokhrel/jira-cli, v1.7.0) against ANY Jira (Cloud or on-premise/Data Center). Covers the full command surface (issue / epic / sprint / board / project / release), the non-interactive automation contract (`--no-input` + `--plain`/`--raw`/`--csv` for agent-safe, parseable runs), JQL filtering and the date/negation idioms, GitHub- and Jira-flavored markdown → Atlassian Document Format (ADF) conversion and its lossy edges, authentication for every backend (Cloud API token, on-prem basic, PAT/bearer, mTLS), and live-discovery of instance-specific values (project keys, issue types, statuses, priorities, resolutions, link types, custom field IDs) instead of hardcoding them. Instance-agnostic — no account-specific content.
developer-toolsInteractive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', or wants to prepare for daily meeting. Conducts interview (yesterday, today, blockers, discussion topics) and optionally pulls activity from GitHub/git/Jira if available and approved by user.
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.
Generates a scrum-tool-agnostic onboarding backlog (Jira, GitHub, or Azure DevOps) that takes a team from zero to publishing consumer + provider contract tests on PactFlow
Run Jira and Confluence from a conversation, including reviewed Jira or Jira Align refresh with capability-scoped write-back.
integrationsComprehensive Jira integration with auto-detection of issue keys. Two specialized skills: jira-communication for API operations and jira-syntax for wiki markup validation and templates.
Enforce natural German technical register in Jira tickets, internal docs and team chat. Catches English→German anglicisms (brechen, gefangen, triggern, failen) and substitutes canonical verbs (werfen, abfangen, auslösen, fehlschlagen). Accepts Denglisch loanwords. Skips commit messages.
Round-1 IT QA peer-review runbook: lifecycle, checklist, severity vocabulary, structured Jira comment template, edge cases, anti-patterns. Triggers on QA-status tickets, 'ready for QA' comments, and explicit IT QA / peer review / quality gate requests. Generic; defers to team-specific overrides.
