Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
Imported from thebushidocollective/han (plugins/services/jira/skills/my-tickets/SKILL.md). Install upstream with npx skills add thebushidocollective/han --skill my-tickets. Copyright stays with the author.
my-tickets
Name
jira:my-tickets - Show all Jira tickets assigned to you
Synopsis
/my-tickets [arguments]
Description
Show all Jira tickets assigned to you
Implementation
Retrieve and display all Jira tickets currently assigned to you.
Use the Atlassian MCP tool atlassian_search_issues with JQL:
assignee = currentUser() AND status != Done
Group the results by status and display in a clear table format:
Key
Summary
Status
Priority
Updated
Include:
Ticket key (e.g., PROJ-123)
Summary (truncate if too long)
Current status
Priority
Last updated date
Show count of tickets by status at the end.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install my-tickets and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
When a provider is down or over quota the request moves on; the trace says it did.
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
thebushidocollective-han-my-tickets.ocm.jsonjson
{
"ocm": "1",
"id": "thebushidocollective-han-my-tickets",
"kind": "skill",
"name": "my-tickets",
"description": "Show all Jira tickets assigned to you",
"publisher": "thebushidocollective",
"version": "1.0.0",
"capabilities": {
"domains": [
"customer_support",
"data_analysis"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Show all Jira tickets assigned to you"
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/thebushidocollective/han",
"path": "plugins/services/jira/skills/my-tickets/SKILL.md",
"ref": "HEAD",
"url": "https://github.com/thebushidocollective/han/blob/HEAD/plugins/services/jira/skills/my-tickets/SKILL.md",
"key": "thebushidocollective/han/plugins/services/jira/skills/my-tickets/SKILL.md"
}
},
"instructions": "# my-tickets\n\n## Name\n\njira:my-tickets - Show all Jira tickets assigned to you\n\n## Synopsis\n\n```\n/my-tickets [arguments]\n```\n\n## Description\n\nShow all Jira tickets assigned to you\n\n## Implementation\n\nRetrieve and display all Jira tickets currently assigned to you.\n\nUse the Atlassian MCP tool `atlassian_search_issues` with JQL:\n\n```\nassignee = currentUser() AND status != Done\n```\n\nGroup the results by status and display in a clear table format:\n\n| Key | Summary | Status | Priority | Updated |\n|-----|---------|--------|----------|---------|\n\nInclude:\n\n- Ticket key (e.g., PROJ-123)\n- Summary (truncate if too long)\n- Current status\n- Priority\n- Last updated date\n\nShow count of tickets by status at the end.",
"cost": {
"context_tokens": 177
}
}
Fetch it by URL: GET /api/v1/registry/thebushidocollective-han-my-tickets/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
