jira-epic-outcome-view SKILL.md skillA
jira-epic-outcome-view 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-epic-outcome-view@v0.1.0Pins v0.1.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-epic-outcome-view/SKILL.md- Versions recorded
- 1
- Latest version
- v0.1.0, committed Sep 26, 2026
- Size
- 12,921 bytes
- Repository stars
- 28
- License
- Apache-2.0
Use this skill when someone wants to see what a Jira project's Epics have delivered beside what that work was meant to change -- "show me our Epics and their outcomes for PROJ", "which Epics are moving and what are they for", "what did we ship this quarter and why". Groups a project's work by Epic, counts delivery from the flow-metrics skill's own per-issue rows, and renders each Epic's recorded outcome or says plainly that none is recorded and asks the team for one. Read-only -- never…
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-epic-outcome-view One view, two halves. For each Epic in a Jira project: what its work has delivered, and what that work was meant to change. The point of putting them side by side is that neither half answers the question alone. A throughput count says a team is moving; it does not say whether the movement was worth it. An outcome statement says what was intended; it does not say whether anything happened. ## Output rendering <!-- agentbundle:output-rendering:start --> Lead with the useful outcome or next action. Use warm, non-blaming language and everyday words. Define an unfamiliar term in a few plain words before naming it; keep proper names and exact technical terms intact. During tool work, do not narrate routine calls. Send an update only for safety, a blocker, a needed decision, a material scope change, a long wait, or an active host requirement. When requesting input, ask only for what is needed now. Ask dependent questions one at a time; otherwise group related questions. Offer no more than three clear choices when choices help. …
Read the whole file at its exact version.
How to install
mdr add eugenelim/agent-ready-repo/jira-epic-outcome-view@sha256:8ca978421b227c5fThe line at the top of this page pins the label v0.1.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_3rekievw3lfb57yb)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 26, 2026.
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 (12921 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_3rekievw3lfb57yb GET https://markdownregistry.com/api/v1/resolve?ref=eugenelim/agent-ready-repo/jira-epic-outcome-view GET https://markdownregistry.com/api/v1/blob/8ca978421b227c5f0390777d5877438cc0d90b875d3db5bb9f103a5a3e4ab970
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.