メニュー
Use Mirra to jira project management and issue tracking. Covers all Jira SDK operations via REST API.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use Mirra to living dashboards — natively-rendered grids of typed widgets (stat, image_card, list, progress, sparkline) that flows keep current by pushing data into them..... Covers all Dashboards SDK operations via REST API.
Use Mirra to execute user-defined scripts in aws lambda. Covers all Scripts SDK operations via REST API.
Use Mirra to the places a space publishes to — its corporate x, blog, newsletter — and the drafted copy waiting to go out to them. use listchannels to see what this space.... Covers all Space Channels SDK operations via REST API.
Use Mirra to the space's shared work-ledger. items are agreed work with status (open/proposed/done), an owner, artifact links, and progress notes; every teammate's home f.... Covers all Work Items SDK operations via REST API.
The team work-ledger ritual for agents on a Mirra space: track agreed work, propose discoveries (then ask in chat), relay approvals, close what ships, and publish ONE narrated update card per work burst — revise, never stack. Rides the Mirra items adapter / MCP work-ledger tools.
START HERE for anything Mirra. Load this whenever the repo you're working in has a .mirra/ directory (it's linked to a Mirra team space), or your human mentions their Mirra space, teammates' updates, or the team ledger. Directs the ambient team rituals — record work in the shared ledger, publish update cards, ask the space before expanding scope — and indexes every detail-level mirra-* skill.
| name | mirra-jira |
| description | Use Mirra to jira project management and issue tracking. Covers all Jira SDK operations via REST API. |
| allowed-tools | Read, Bash(curl:*, jq:*) |
Jira project management and issue tracking
You need the user's API key. Ask for these if not provided:
API_KEY: Mirra API key (generated in Mirra app > Settings > API Keys)API_URL: Defaults to https://api.fxn.world (only ask if they mention a custom server)Note: Jira requires OAuth authentication. The user must have connected their Jira account in the Mirra app before these operations will work.
All operations use a single POST endpoint with the resource ID and method in the body:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{
"resourceId": "jira",
"method": "{operation}",
"params": { ...args }
}' | jq .
Replace {operation} with the operation name from the table below.
Legacy alternative:
POST ${API_URL}/api/sdk/v1/jira/{operation}with args as the request body also works but is not recommended for new integrations.
| Operation | Description |
|---|---|
createIssue | Create a new Jira issue |
searchIssues | Search Jira issues using JQL. Returns normalized flat issue summaries. |
getIssue | Get a specific Jira issue by key or ID. Returns normalized flat structure. |
updateIssue | Update an existing Jira issue |
deleteIssue | Delete a Jira issue |
addComment | Add a comment to a Jira issue |
transitionIssue | Transition a Jira issue to a different status |
assignIssue | Assign a Jira issue to a user |
getProjects | Get all accessible Jira projects. Returns normalized flat project structures. |
listProjects | List all accessible Jira projects (alias for getProjects). Returns normalized flat structures. |
getProjectMetadata | Get metadata for a specific Jira project. Returns normalized flat structures. |
getTransitions | Get available transitions for a Jira issue. Returns normalized flat structures. |
listAssignableUsers | List users that can be assigned to issues in a project |
getIssueTypes | Get available issue types for a project. Returns normalized flat structures. |
discoverExtended | Search Jira API for available operations beyond core tools |
executeExtended | Execute a Jira API operation by operationId |
createIssueCreate a new Jira issue
Arguments:
projectKey (string, required): Jira project key (e.g., "PROJ")summary (string, required): Issue summary/titledescription (string, optional): Issue descriptionissueType (string, optional): Issue type (Task, Bug, Story, etc.)Returns:
AdapterOperationResult: Created issue information
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"jira","method":"createIssue","params":{"projectKey":"<value>","summary":"<value>"}}' | jq .
Warning: This is a destructive operation. Confirm with the user before executing.
searchIssuesSearch Jira issues using JQL. Returns normalized flat issue summaries.
Arguments:
jql (string, required): JQL query stringmaxResults (number, optional): Maximum number of results (default: 50, max: 100)Returns:
AdapterOperationResult: Returns { jql, count, issues[] }. Each issue has FLAT fields: id, key, summary, status, statusId, issueType, issueTypeId, priority, priorityId, assignee, assigneeAccountId, projectKey, projectName, labels[], created, updated, isAssigned. No nested objects.
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"jira","method":"searchIssues","params":{"jql":"<value>"}}' | jq .
getIssueGet a specific Jira issue by key or ID. Returns normalized flat structure.
Arguments:
issueKey (string, required): Issue key (e.g., "PROJ-123") or IDReturns:
AdapterOperationResult: Returns FLAT structure with: id, key, summary, description, status, statusId, issueType, issueTypeId, priority, priorityId, assignee, assigneeAccountId, reporter, reporterAccountId, projectKey, projectName, projectId, labels[], created, updated, isAssigned, hasLabels. No nested objects.
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"jira","method":"getIssue","params":{"issueKey":"<value>"}}' | jq .
updateIssueUpdate an existing Jira issue
Arguments:
issueKey (string, required): Issue key (e.g., "PROJ-123")summary (string, optional): New issue summary/titledescription (string, optional): New issue descriptionReturns:
AdapterOperationResult: Updated issue information
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"jira","method":"updateIssue","params":{"issueKey":"<value>"}}' | jq .
Warning: This is a destructive operation. Confirm with the user before executing.
deleteIssueDelete a Jira issue
Arguments:
issueKey (string, required): Issue key (e.g., "PROJ-123")Returns:
AdapterOperationResult: Deletion confirmation
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"jira","method":"deleteIssue","params":{"issueKey":"<value>"}}' | jq .
addCommentAdd a comment to a Jira issue
Arguments:
issueKey (string, required): Issue key (e.g., "PROJ-123")comment (string, required): Comment textReturns:
AdapterOperationResult: Created comment information
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"jira","method":"addComment","params":{"issueKey":"<value>","comment":"<value>"}}' | jq .
Warning: This is a destructive operation. Confirm with the user before executing.
transitionIssueTransition a Jira issue to a different status
Arguments:
issueKey (string, required): Issue key (e.g., "PROJ-123")transitionId (string, required): ID of the transition to performReturns:
AdapterOperationResult: Transition result
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"jira","method":"transitionIssue","params":{"issueKey":"<value>","transitionId":"<ID>"}}' | jq .
assignIssueAssign a Jira issue to a user
Arguments:
issueKey (string, required): Issue key (e.g., "PROJ-123")accountId (string, required): Atlassian account ID of the assigneeReturns:
AdapterOperationResult: Assignment result
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"jira","method":"assignIssue","params":{"issueKey":"<value>","accountId":"<ID>"}}' | jq .
getProjectsGet all accessible Jira projects. Returns normalized flat project structures.
Returns:
AdapterOperationResult: Returns { count, projects[] }. Each project has FLAT fields: id, key, name, projectTypeKey, leadName, leadAccountId. No nested objects.
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"jira","method":"getProjects","params":{}}' | jq .
listProjectsList all accessible Jira projects (alias for getProjects). Returns normalized flat structures.
Returns:
AdapterOperationResult: Returns { count, projects[] }. Each project has FLAT fields: id, key, name, projectTypeKey, leadName, leadAccountId. No nested objects.
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"jira","method":"listProjects","params":{}}' | jq .
getProjectMetadataGet metadata for a specific Jira project. Returns normalized flat structures.
Arguments:
projectKey (string, required): Project key (e.g., "PROJ")Returns:
AdapterOperationResult: Returns { projectKey, projectName, issueTypeCount, issueTypes[], priorityCount, priorities[] }. Each issueType has FLAT fields: id, name, description, isSubtask. Each priority has: id, name, description.
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"jira","method":"getProjectMetadata","params":{"projectKey":"<value>"}}' | jq .
getTransitionsGet available transitions for a Jira issue. Returns normalized flat structures.
Arguments:
issueKey (string, required): Issue key (e.g., "PROJ-123")Returns:
AdapterOperationResult: Returns { issueKey, count, transitions[] }. Each transition has FLAT fields: id, name, toStatus, toStatusId. No nested objects.
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"jira","method":"getTransitions","params":{"issueKey":"<value>"}}' | jq .
listAssignableUsersList users that can be assigned to issues in a project
Arguments:
projectKey (string, required): Project key (e.g., "PROJ")Returns:
AdapterOperationResult: Returns { projectKey, count, users[] }. Each user has: accountId, displayName, emailAddress, active.
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"jira","method":"listAssignableUsers","params":{"projectKey":"<value>"}}' | jq .
getIssueTypesGet available issue types for a project. Returns normalized flat structures.
Arguments:
projectKey (string, required): Project key (e.g., "PROJ")Returns:
AdapterOperationResult: Returns { projectKey, count, issueTypes[] }. Each issueType has FLAT fields: id, name, description, isSubtask. No nested objects.
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"jira","method":"getIssueTypes","params":{"projectKey":"<value>"}}' | jq .
discoverExtendedSearch Jira API for available operations beyond core tools
Arguments:
query (string, required): Describe what you want to do (e.g., "add label to card")limit (number, optional): Max results to return (default 5)Returns:
AdapterOperationResult: List of matching operations with their details
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"jira","method":"discoverExtended","params":{"query":"search term"}}' | jq .
executeExtendedExecute a Jira API operation by operationId
Arguments:
operationId (string, required): The operationId from discoverExtended resultspathParams (object, optional): Path parameters, e.g., { id: "abc123" }queryParams (object, optional): Query string parametersbody (object, optional): Request body for POST/PUT/PATCH operationsReturns:
AdapterOperationResult: API response data
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"jira","method":"executeExtended","params":{"operationId":"<ID>"}}' | jq .
All SDK responses return the operation payload wrapped in a standard envelope:
{
"success": true,
"data": { ... }
}
The data field contains the operation result. Error responses include:
{
"success": false,
"error": {
"code": "ERROR_CODE",
"message": "Human-readable error message"
}
}
jq . to pretty-print responses, jq .data to extract just the payloaddata.results or directly in data (check examples)--fail-with-body to curl to see error details on HTTP failuresexport API_KEY="your-key"