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.
jira-task-format - Skill - OpenSmartRoute
Skillv1.0.0
jira-task-format
Use when writing or formatting Jira task titles and descriptions for the App Planner agent, or any time app-plan features are being turned into Jira tickets.
Instruction file imported from joergibobman-blip/MCP-Test (.github/instructions/jira-task-format.instructions.md). Copyright stays with the author.
Jira Task Formatting
Keep it to a flat list of 5-8 Tasks — no epics or subtasks, this is a planning demo.
Title: <Area>: <short action>, e.g. Auth: add email/password login. Max ~8 words.
Description: two short parts:
Goal: one sentence on what this task delivers.
Acceptance Criteria: 2-3 bullet points, concrete and testable.
Order tasks roughly by dependency (setup/foundation first, polish last).
No labels or priority needed unless the user explicitly asks for them.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/joergibobman-blip-mcp-test-jira-task-format-instructions/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "joergibobman-blip-mcp-test-jira-task-format-instructions",
"kind": "skill",
"name": "jira-task-format",
"description": "Use when writing or formatting Jira task titles and descriptions for the App Planner agent, or any time app-plan features are being turned into Jira tickets.",
"publisher": "joergibobman-blip",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Use when writing or formatting Jira task titles and descriptions for the App Planner agent, or any time app-plan features are being turned into Jira tickets."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/joergibobman-blip/MCP-Test",
"path": ".github/instructions/jira-task-format.instructions.md",
"ref": "50d012730e4835c0862ee1a26f071b405f2cf42c",
"url": "https://github.com/joergibobman-blip/MCP-Test/blob/50d012730e4835c0862ee1a26f071b405f2cf42c/.github/instructions/jira-task-format.instructions.md",
"key": "joergibobman-blip/MCP-Test/.github/instructions/jira-task-format.instructions.md"
}
},
"instructions": "# Jira Task Formatting\r\n\r\n- Keep it to a flat list of **5-8 Tasks** — no epics or subtasks, this is a planning demo.\r\n- **Title**: `<Area>: <short action>`, e.g. `Auth: add email/password login`. Max ~8 words.\r\n- **Description**: two short parts:\r\n - `Goal:` one sentence on what this task delivers.\r\n - `Acceptance Criteria:` 2-3 bullet points, concrete and testable.\r\n- Order tasks roughly by dependency (setup/foundation first, polish last).\r\n- No labels or priority needed unless the user explicitly asks for them.",
"cost": {
"context_tokens": 130
}
}
Fetch it by URL: GET /api/v1/registry/joergibobman-blip-mcp-test-jira-task-format-instructions/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.
