create-placeholder-issue SKILL.md skillA
create-placeholder-issue from tomzx/agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tomzx/agents/create-placeholder-issue@git:20261007.b35fc4bPins git:20261007.b35fc4b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tomzx/agents
- Path
skills/create-placeholder-issue/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261007.b35fc4b, committed Oct 7, 2026
- First version recorded
- Jul 4, 2026
- Size
- 8,747 bytes
- Repository stars
- 12
- License
- MIT
Create a placeholder GitHub issue for a pending SDLC feature (one created without an issue, with a p-prefixed directory) and promote it to issue-driven form by renaming its directory and rewriting FEAT- cross-references. Use when the user says /create-placeholder-issue, wants to promote a pending feature, wants to back an existing SDLC feature with a GitHub issue, or wants to convert a p-prefixed feature directory into an issue-numbered one. For starting top-down from a feature request, use…
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
# Create Placeholder Issue Creates a minimal placeholder GitHub issue for a **pending** SDLC feature, then promotes the feature to issue-driven form: renames the directory to the new issue number and rewrites every `FEAT-p<seq>` cross-reference to `FEAT-<issue>`. This is the promotion step defined by the Feature Directory Naming convention in `skills/sdlc/references/shared.md`. Use it for features created bottom-up (e.g. by `sync-sdlc` from code analysis) that have no GitHub issue yet. For top-down work where you start from a feature request, use `/create-issue`, which produces a full structured issue. ## Prerequisites - Apply the shared SDLC conventions in `skills/sdlc/references/shared.md`. - `gh` CLI authenticated with write access to create issues in the target repository. - A pending feature directory `p<seq>-<slug>` under `.sdlc/features/` (resolved via SDLC_DIR if set). ### Skill attribution (GitHub) Before creating the issue, read [`github-post-attribution/SKILL.md`](../github-post-attribution/SKILL.md) and append the **Created with** footer for `SKILL_DIR` = `create-placeholder-issue` to the issue body. ### Communication guidelines (outbound text) …
Read the whole file at its exact version.
How to install
mdr add tomzx/agents/create-placeholder-issue@sha256:c55938f0adebf372The line at the top of this page pins the label git:20261007.b35fc4b, 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_bn7uqpnezt72jpi4)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 4, 2026 and Oct 7, 2026, about one every 24 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.b35fc4b latest | 2026-10-07 | b35fc4b | 8,747 B | A | view · diff |
| git:20261004.00bb0c5 | 2026-10-04 | 00bb0c5 | 8,697 B | A | view · diff |
| git:20261002.777260f | 2026-10-02 | 777260f | 8,683 B | A | view · diff |
| git:20260930.e2e20d7 | 2026-09-30 | e2e20d7 | 8,681 B | A | view · diff |
| git:20260704.f3c9632 | 2026-07-04 | f3c9632 | 8,485 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 (8747 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
tomzx/agents · 12 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bn7uqpnezt72jpi4 GET https://markdownregistry.com/api/v1/resolve?ref=tomzx/agents/create-placeholder-issue GET https://markdownregistry.com/api/v1/blob/c55938f0adebf3720fe3acdb48a1fd74135861e90d1c25942ba66e5b97e96ffd
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.