From jira-tools
CARS project-specific configuration for the carscommerce.atlassian.net org. Activated automatically by /jira-create when the user is working in the CARS project. Provides work hierarchy, issue type names, team field setup, and UUID resolution instructions specific to carscommerce.
npx claudepluginhub mbensch/mb-ai-tools --plugin jira-toolsThis skill uses the workspace's default tool permissions.
This skill is activated by `/jira-create` when the authenticated user's Atlassian site is `carscommerce.atlassian.net` and the user selects the CARS project. It provides the custom field IDs and value formats specific to this org.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Provides patterns for autonomous Claude Code loops: sequential pipelines, agentic REPLs, PR cycles, de-sloppify cleanups, and RFC-driven multi-agent DAGs. For continuous dev workflows without intervention.
Applies NestJS patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production TypeScript backends with project structure and bootstrap examples.
This skill is activated by /jira-create when the authenticated user's Atlassian site is carscommerce.atlassian.net and the user selects the CARS project. It provides the custom field IDs and value formats specific to this org.
The CARS project uses the following hierarchy from highest to lowest:
Objective
└── Initiative
└── Epic
└── Story / Bug / Task
└── Sub-Task
| Level | Jira issue type name | Skill |
|---|---|---|
| Objective | Objective | create-jira-objective |
| Initiative | Initiative | create-jira-initiative |
| Epic | Epic | create-jira-epic |
| Story | Story | create-jira-story |
| Bug | Bug | create-jira-bug |
| Task | Task | manage-jira (generic) |
| Sub-Task | Sub-task | manage-jira (generic) |
When creating a ticket, use the exact issue type name from the "Jira issue type name" column above in atlassian___createJiraIssue.
| Field | Custom field ID | Value format |
|---|---|---|
| Team | customfield_11100 | Plain string UUID |
| Sprint | customfield_10007 | Plain integer ID |
| Story Points | customfield_10004 | Numeric value |
Every ticket created in the CARS project must have a team assigned to appear on the board. Immediately after the ticket is created by a create-jira-* skill, follow the team assignment steps below.
To find the UUID for a given team, fetch an existing ticket that already belongs to that team:
atlassian___getJiraIssue(cloudId, issueIdOrKey: "CARS-<existing-ticket>")
Look at the customfield_11100 field in the response. The value is the team UUID (a plain string, not wrapped in an object).
After creating the ticket, set the team via atlassian___editJiraIssue:
atlassian___editJiraIssue(
cloudId,
issueIdOrKey: "CARS-<new-ticket>",
fields: {"customfield_11100": "<team-uuid>"}
)
Pass the UUID as a plain string. Do not wrap it in {"id": "..."} -- that returns a 400 error.
customfield_11100.
To find the sprint ID, view an existing ticket in the target sprint and read customfield_10007. It contains an array of sprint objects -- use the id from the active sprint object.
atlassian___editJiraIssue(
cloudId,
issueIdOrKey: "CARS-<new-ticket>",
fields: {"customfield_10007": <sprint-id-integer>}
)
Pass the sprint ID as a plain integer. Do not wrap it in {"id": ...}.
atlassian___editJiraIssue(
cloudId,
issueIdOrKey: "CARS-<new-ticket>",
fields: {"customfield_10004": <points>}
)