15 tagged issue-tracker, measured the same way as everything else here.
Browse within: claude-code-plugin 24beads 23superpowers 22mcp-server 11cad-as-code 10cad-examples 10forgecad 10parametric-cad 10kaneo 9self-hosted 9plugin 5
Dicklesworthstone/beads_viewer
Skill Claude CodeCodex
Beads Viewer - Graph-aware triage engine for Beads projects. Computes PageRank, betweenness, critical path, and cycles. Use --robot- flags for AI agents.
Skill Claude CodeCodex
Build or edit a manufacture-realistic .forge.js model in a project, then validate it with run, render, inspect, and export evidence.
Skill Claude CodeCodex
Manage the runloq issue tracker — create, list, update, close, search, and view the board. Use when someone says "add issue", "create a ticket", "what's open", "show board", "close X", "search issues", or when tracking work in progress. Works via the runloq CLI or runloq-mcp MCP server.
Skill Claude CodeCodex
Use this skill when the user needs TeamDynamix ITSM operations through MCP: ticket triage and updates, KB article maintenance, asset/CI relationships, service catalog lookups, project issue/risk workflows, or time entry queries. Always discover IDs first, use read-before-write patterns, and enforce write safety gates.
Skill Claude CodeCodex
Use this skill when the user needs to manage Beans work items in a Beans workspace—create, view, update, reopen, archive, query, or bulk-manage beans, edit .beans files/frontmatter, or manage parent/blocking relationships. Use it even when the user says tickets/issues/backlog instead of “beans.” Do not use it for…
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: