← Search

GitHub issues for unmet spec requirements
Developer tools 🧪 Install ran in our test sandbox · Nov 18, 2026 📌 Pinned version: commit 82701c2
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: an agent with GitHub issue tooling…

GitHub issues for unmet spec requirements

Turn unimplemented spec requirements into GitHub issues — requirement extraction, codebase verification, duplicate avoidance, feature_request.yml templates

At a glance
What
Turn unimplemented spec requirements into GitHub issues — requirement extraction, codebase verification, duplicate avoidance, feature_request.yml templates
Cost
Free
Needs
an agent with GitHub issue tooling (search_issues/create_issue or equivalent) and write access to the repository; nothing else — the skill is a process, no paid accounts required for public repos
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

GitHub issues for unmet spec requirements is a free Muse skill from the github awesome-copilot collection that turns unimplemented requirements in a specification file into GitHub issues. It analyzes the spec to extract all requirements, checks each one's implementation status against the codebase, including the spec directory and related code patterns, and searches existing issues to avoid duplicates.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 82701c2

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: an agent with GitHub issue tooling (search_issues/create_issue or equivalent) and write access to the repository; nothing else — the skill is a process, no paid accounts required for public repos Install "GitHub issues for unmet spec requirements" for me. It gives the agent the github/awesome-copilot skill for turning unimplemented spec requirements into GitHub issues: analyze the specification file, verify each requirement's implementation status against the codebase, search existing issues to avoid duplicates, and create one issue per unmet requirement with requirement ID, description, implementation guidance and acceptance criteria using the feature_request.yml template. MIT-licensed. Repository: https://raw.githubusercontent.com/github/awesome-copilot/82701c24b99488536ca399ff4789a458b7a05db7/skills/create-github-issues-for-unmet-specification-requirements/SKILL.md Pinned version: install the code at commit 82701c24b99488536ca399ff4789a458b7a05db7 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "create-github-issues-for-unmet-specification-requirements". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at the specification file to analyze; confirm which repo to create issues in). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 82701c2 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 18, 2026
👁 Observed during the install test · Nov 18, 2026 : registry.npmjs.org
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
82701c2 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 18, 2026 · Observed during the install test: registry.npmjs.org
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.