jira-issue-refine SKILL.md skillA
jira-issue-refine from yarlson/yarstack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yarlson/yarstack/jira-issue-refine@git:20261017.2f2e03bPins git:20261017.2f2e03b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yarlson/yarstack
- Path
plugins/yarstack/skills/jira-issue-refine/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261017.2f2e03b, committed Oct 17, 2026
- First version recorded
- Aug 9, 2026
- Size
- 7,252 bytes
- Repository stars
- 3
- License
- MIT
Refine one draft or existing Jira issue into a clear, evidence-backed, bounded delivery contract without implementing it. Use when creating or revising an issue before engineering handoff, especially when behavior, repository ownership, acceptance evidence, dependencies, risk, environment needs, or scope remain unclear.
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
# Jira Issue Refinement Turn one issue into a concise contract that an engineer or coding agent can implement and verify without guessing. Preserve confirmed intent, resolve discoverable facts, and expose decisions that still require a person. ## Establish the issue boundary 1. Read the complete draft or existing issue, including structured fields, comments, links, attachments, parent or child issues, and user-supplied context when available. 2. Identify the affected actor or system, current behavior, required outcome, business or operational reason, and requested issue type. 3. Separate confirmed requirements from observations, assumptions, implementation suggestions, and unrelated follow-up ideas. Do not silently promote an engineering suggestion into required behavior. 4. Preserve the author's confirmed intent and terminology. Change meaning only when evidence or an explicit user decision requires it. 5. Keep Jira access read-only unless the user explicitly authorizes creating or updating an issue. Do not implement the requested product or engineering change under this skill. ## Assess what the issue still needs Check each concern only to the depth material to delivery: …
Read the whole file at its exact version.
How to install
mdr add yarlson/yarstack/jira-issue-refine@sha256:b94960ba9b56ecafThe line at the top of this page pins the label git:20261017.2f2e03b, 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_nocolwsps4izt2rf)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Aug 9, 2026 and Oct 17, 2026, about one every 69 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.2f2e03b latest | 2026-10-17 | 2f2e03b | 7,252 B | A | view · diff |
| git:20260809.11a3ed6 | 2026-08-09 | 11a3ed6 | 7,460 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 (7252 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
yarlson/yarstack · 3 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nocolwsps4izt2rf GET https://markdownregistry.com/api/v1/resolve?ref=yarlson/yarstack/jira-issue-refine GET https://markdownregistry.com/api/v1/blob/b94960ba9b56ecaf6ad1433b066e1bbd959193a8fe54f20651e4aca4d1e0bf34
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.