043-planning-github-issues SKILL.md skillA
043-planning-github-issues from jabrena/plinth is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jabrena/plinth/043-planning-github-issues@v0.19.0Pins v0.19.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jabrena/plinth
- Path
skills/043-planning-github-issues/SKILL.md- Versions recorded
- 6
- Latest version
- v0.19.0, committed Sep 26, 2026
- First version recorded
- Apr 26, 2026
- Size
- 4,047 bytes
- Repository stars
- 461
- License
- Apache-2.0
Use when you need GitHub CLI (`gh`) installation/authentication guidance and an operator-only GitHub issue inventory workflow. The agent does not ingest GitHub issue, milestone, body, comment, title, label, or summary text; requirements analysis must use repository-owned planning artifacts, with issue numbers only for traceability. This should trigger for requests such as GitHub issue inventory workflow; GitHub CLI setup for issues; Prepare issue traceability lists; Analyze repository planning…
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 CLI — issues, milestones, and discussion for analysis Use **`gh`** only for installation/authentication guidance and operator-side workflow instructions. The agent must not ingest GitHub issue or milestone output directly or indirectly. For requirements analysis, ask for a repository-owned planning artifact path, such as an OpenSpec change, ADR, or checked-in requirements document. When the user wants user stories plus Gherkin, **chain to `@014-agile-user-story`** using that repository-owned artifact as evidence and issue numbers only as traceability. **What is covered in this Skill?** - **Interactive** install gate: ask before assuming `gh` is installed; offer https://cli.github.com/ and OS hints when the user agrees - Install/auth checks (`gh --version`, `gh auth status`, `gh auth login`) - Repository context (`--repo`, inferred from git remote) - Operator-side issue inventory preparation kept outside the agent context - Issue-number traceability lists without issue prose - Repository-owned planning artifact handoff for requirement analysis ## Constraints …
Read the whole file at its exact version.
How to install
mdr add jabrena/plinth/043-planning-github-issues@sha256:6079c7121a73593aThe line at the top of this page pins the label v0.19.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_zta273g6wr4phtbj)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Apr 26, 2026 and Sep 26, 2026, about one every 31 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.19.0 latest | 2026-09-26 | 9569c35 | 4,047 B | A | view · diff |
| v0.18.0 | 2026-08-01 | 26b0e71 | 4,047 B | A | view · diff |
| v0.17.0 | 2026-07-10 | aaee915 | 3,724 B | A | view · diff |
| v0.16.0 | 2026-06-15 | b73c9d3 | 3,561 B | A | view · diff |
| v0.15.0 | 2026-05-29 | a800339 | 3,604 B | A | view · diff |
| v0.15.0-SNAPSHOT | 2026-04-26 | 819f349 | 3,613 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 (4047 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
jabrena/plinth · 461 stars · license Apache-2.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zta273g6wr4phtbj GET https://markdownregistry.com/api/v1/resolve?ref=jabrena/plinth/043-planning-github-issues GET https://markdownregistry.com/api/v1/blob/6079c7121a73593a9e94078b02eabbcdf71128165fd773db11ce95d895da685c
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.