What problem does it solve? When a Claude Code skill breaks mid-session, there is no structured way to log the failure. This Skill files a DOCS Jira Task labeled claude-skill-bug through the Atlassian MCP connection, so broken skills get tracked without opening a browser or leaving the terminal. ## Core Features & Use Cases - API-only ticket creation: Creates a Jira Task in the DOCS project via createJiraIssue with the claude-skill-bug label, no browser or clipboard involved. - Structured bug reports: Builds a description with skill name, environment details (Claude Code version, OS, shell), expected vs actual behavior, and a redacted transcript snippet. - Assignee resolution: Looks up the broken skill's owner from its frontmatter via lookupJiraAccountId, falling back to the current user, so tickets reach someone. - Use Case: A skill produces wrong output mid-session. You say "file a bug for jira-start", confirm the details, and receive a ticket URL like https://mariadbcorp.atlassian.net/browse/DOCS-1234. ## Quick Start Tell the AI "report a skill bug for <skill-name>" and confirm the expected versus actual behavior when asked.