github-issue SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
github-issue from stempeck/agentfactory is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add stempeck/agentfactory/github-issue@git:20260803.0df7e2ePins git:20260803.0df7e2e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- stempeck/agentfactory
- Path
.claude/skills/github-issue/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260803.0df7e2e, committed Aug 3, 2026
- First version recorded
- May 5, 2026
- Size
- 18,565 bytes
- Repository stars
- 3
- License
- AGPL-3.0
Creates well-documented GitHub issues (or comments on existing ones) from problems discussed in conversation. Investigates the codebase to map affected layers, files, and data flow, then writes up findings with acceptance criteria — without prescribing fixes. Use when a conversation has identified a problem that needs a GitHub issue, when the user wants to document a bug or problem for an implementer, or when dispatching work. Triggers on "create a GitHub issue", "write up an issue for this…
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
# GitHub Issue Investigation & Write-Up Produces a write-up that gives an implementer everything they need to find and understand a problem — without telling them how to fix it. ## Your Role: Cartographer, Not Surgeon You are not fixing this problem. You are drawing the map for someone who will. The implementer who picks this up is skilled — they will read the codebase, trace the data flow, form their own theory, and write the fix. What they need from you is the terrain: which files are involved, what the data flow looks like, what's surprising about the system, and what "done" looks like. What they don't need — and what actively hurts them — is you pre-chewing the solution. When you prescribe specific changes, you close off their discovery, narrow their scope, and cause them to miss things you missed. **Cartographer of the fix — not of the problem's altitude.** The "not a surgeon" rule governs the FIX: don't prescribe how to solve it. It does NOT license accepting the reported problem's *altitude* uncritically. The report — and any pre-stated acceptance criteria — is a hypothesis about where the defect lives, not scripture to be mapped. Your …
Read the whole file at its exact version.
How to install
mdr add stempeck/agentfactory/github-issue@sha256:54780c8b9b2d4f4cThe line at the top of this page pins the label git:20260803.0df7e2e, 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_ox2copsmrvnndaab)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 5, 2026 and Aug 3, 2026, about one every 90 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260803.0df7e2e latest | 2026-08-03 | 0df7e2e | 18,565 B | A | view · diff |
| git:20260505.779f9ba | 2026-05-05 | 779f9ba | 12,559 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 (18565 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
stempeck/agentfactory · 3 stars · license AGPL-3.0 · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ox2copsmrvnndaab GET https://markdownregistry.com/api/v1/resolve?ref=stempeck/agentfactory/github-issue GET https://markdownregistry.com/api/v1/blob/54780c8b9b2d4f4c876c959326aca9173a8820f45ff11ae37b0183587f84b1c8
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.
More from stempeck/agentfactory
Every file in stempeck/agentfactory