jira-story-triage SKILL.md skillA
jira-story-triage from eugenelim/agent-ready-repo is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add eugenelim/agent-ready-repo/jira-story-triage@v2.0.0Pins v2.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- eugenelim/agent-ready-repo
- Path
packs/atlassian/.apm/skills/jira-story-triage/SKILL.md- Versions recorded
- 5
- Latest version
- v2.0.0, committed Aug 29, 2026
- First version recorded
- Jul 23, 2026
- Size
- 18,398 bytes
- Repository stars
- 28
- License
- Apache-2.0
Review Jira work items for readiness and improve weak stories — it explains why each item is not ready (which question failed and the specific gap), identifies unresolved human questions, drafts proposed rewrites and acceptance criteria, and writes to Jira only after you approve the exact payload; read-only until then. Triggers on "which stories are not ready", "which stories need more detail", "improve these weak stories", "make these tickets actionable", "draft better acceptance criteria…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Skill: jira-story-triage Review a Jira backlog, sprint, or JQL-scoped set of work items for readiness, explain why each weak item is not ready, and improve them. For every item that is not ready, the output says *why* — which question failed and the specific gap — not just a label. It also identifies unresolved human questions that must be answered before the story can be improved. When the user asks, the skill drafts the fix (acceptance criteria, a clearer outcome, a tighter scope) and writes it back to Jira **only after the user approves the exact drafted payload**. **Read-only by default.** The review and draft flow is read-only. The write flow is opt-in, per-item, and always shows the exact payload before touching Jira. For the read-only *team status* view — what the team can pick up next, what is blocked, unassigned, in progress, or a stand-up summary — use `jira-team-status`. This skill judges readiness in depth and fixes weak items. For applying approved changes to named issues, use the `jira` skill's `update-issue` with explicit per-issue confirmation. ## Output rendering <!-- agentbundle:output-rendering:start --> …
Read the whole file at its exact version.
How to install
mdr add eugenelim/agent-ready-repo/jira-story-triage@sha256:ddf816810f3f28b9The line at the top of this page pins the label v2.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_7edksyzeqzyeavzb)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 23, 2026 and Aug 29, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v2.0.0 latest | 2026-08-29 | fd59e28 | 18,398 B | A | view · diff |
| v2.0.0 | 2026-07-28 | 9270e84 | 15,843 B | A | view · diff |
| v1.1 | 2026-07-27 | 7ba66d5 | 14,506 B | A | view · diff |
| v1.1 | 2026-07-24 | e41b954 | 14,296 B | A | view · diff |
| v1.0 | 2026-07-23 | 51e8a83 | 10,994 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (18398 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
eugenelim/agent-ready-repo · 28 stars · license Apache-2.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7edksyzeqzyeavzb GET https://markdownregistry.com/api/v1/resolve?ref=eugenelim/agent-ready-repo/jira-story-triage GET https://markdownregistry.com/api/v1/blob/ddf816810f3f28b9d6e6f2f2b0b175676783330490f5be8401fd338f7c807c3c
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.