// Search and browse Jira Cloud issues via the Atlassian MCP. Run JQL queries, view backlogs, sprint scope, bug lists, stale issues, and any JQL-driven list. Use when the user asks for Jira backlog items, project issues, sprint issues, open bugs, issues by status, or wants to run a JQL query.
Create new Jira Cloud issues via the Atlassian MCP: bugs, tasks, stories, sub-tasks. Loads project defaults from a local config file. Use when the user asks to create a Jira ticket, file a bug, add a task, add a story, or log a new issue.
Update existing Jira Cloud issues via the Atlassian MCP: transition statuses, add comments, edit fields (priority, labels, fix version, summary), and link issues. Use when the user asks to move an issue to a different status, add a comment to a ticket, change a field on an existing issue, or link two issues together.
Security and structural validation for skills in the workspace. Scans all skills or a single named skill and returns a table showing Structure, Content Safety, Script Safety, Secrets, and Permissions results with a per-skill risk level. Use whenever someone asks to validate, audit, or security-check skills, or says things like "check all skills for issues", "is skill X safe?", "audit the workspace skills", "run a security scan on skills", "validate skills before committing", or "check skill health". Also trigger when a new skill has just been added and the user hasn't reviewed it yet.
Run a phased git workflow: create branch (optional), commit, push, and open a GitHub pull request. Reports success or failure per phase and surfaces the PR URL when the final phase succeeds. Use when the user wants to ship a feature branch end-to-end or wants a single scripted pipeline with phase status.
Copy or sync skills between the .claude/skills, .cursor/skills, and .github/skills folders in the current repository. Use this skill whenever the user wants to copy skills between tool folders, sync skill directories, mirror skills, keep skills in sync across tools, or says things like "copy skills to cursor", "sync github skills to claude", "mirror skills", "copy skills from .github to .claude", "propagate skills", or asks to copy/move skills from one AI tool folder to another.
Generate or convert any content into a Slack Block Kit JSON payload using markdown blocks, ready to paste into the Slack API or a webhook. Accepts freeform text, structured data (status updates, reports, meeting summaries), or existing standard markdown and handles Slack-specific quirks like the 12,000-character limit, image-to-link conversion, and flat header rendering. Use this skill whenever the user says "format this for Slack", "create a Slack message", "convert to Slack markdown", "generate a Slack notification", "make this Slack-ready", "write a Slack announcement", or mentions Slack messages, Slack Block Kit, Slack webhooks, or Slack markdown — even if they just paste content and say "send this to Slack" or "post this in our channel".
| name | jira-issue-searcher |
| description | Search and browse Jira Cloud issues via the Atlassian MCP. Run JQL queries, view backlogs, sprint scope, bug lists, stale issues, and any JQL-driven list. Use when the user asks for Jira backlog items, project issues, sprint issues, open bugs, issues by status, or wants to run a JQL query. |
Use the Atlassian (Jira) MCP tools already configured in your MCP client. This skill does not call the REST API directly.
If tools are missing, complete MCP authentication first.
Check whether config/jira-defaults.local.json exists in the skill directory.
site → default Atlassian siteprojectKey → default project keyboardName → informational label for output headingsdefaultFields → columns to include in result tablesdefaultOrderBy → default JQL ORDER BY clausemaxResultsPerPage → default page size (default 25 if absent)The user can override any default in their prompt (e.g. "use project XYZ").
From the user (or config), obtain:
site from config if setprojectKey from config if set; confirm if multiple sites accessiblecloudIdCall getAccessibleAtlassianResources to get the cloudId for the target site. Reuse it for all subsequent calls in this session — do not call again unless the user switches sites.
Call searchJiraIssuesUsingJql.
PROJ with the active project key.ORDER BY from config if the user did not specify one.defaultFields from config, plus any extra fields the user's question requires. Minimum: key, summary, issuetype, status.responseContentFormat: "markdown".maxResultsPerPage from config. Page through results if the user wants the full set.Return a markdown table with columns from defaultFields (or user-specified fields).
[PROJ-42](https://site.atlassian.net/browse/PROJ-42)Showing 25 of 142 issues. Say "next page" to continue.Optional deep fetch: if search results omit fields the user needs, use getJiraIssue for specific keys — avoid N+1 calls for large lists.
cloudId resolution returns multiple sites and no site is configured, present them and ask the user to pick one.