gh-issue-to-demand-signal SKILL.md skillB
gh-issue-to-demand-signal from varnan-tech/opendirectory is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add varnan-tech/opendirectory/gh-issue-to-demand-signal@git:20260916.a03d635Pins git:20260916.a03d635 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- varnan-tech/opendirectory
- Path
skills/gh-issue-to-demand-signal/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260916.a03d635, committed Sep 16, 2026
- First version recorded
- Apr 21, 2026
- Size
- 23,084 bytes
- Repository stars
- 699
- License
- MIT
Takes a competitor's public GitHub repo URL, fetches their open issues via the GitHub REST API, filters noise locally, clusters issues into 6 demand categories, computes a demand score per issue and per cluster, and outputs a ranked demand gap report with a GTM messaging brief. Use when asked to scan a competitor's GitHub issues, find what their users are begging for, turn GitHub complaints into product positioning, identify competitor feature gaps, or generate messaging from real user demand.…
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 Demand Signal Take a competitor's public GitHub repo. Fetch their open issues. Filter noise locally. Cluster into 6 demand categories. Score by real engagement. Output a ranked demand gap report and GTM messaging brief. --- **Critical rule:** Every issue title in the output must be verbatim from the GitHub API response. Every cluster theme name must be derived from actual issue titles in that cluster. If fewer than 10 issues remain after noise filtering, stop and tell the user -- the repo is too small for reliable clustering. No invented issue content anywhere. --- ## Common Mistakes | The agent will want to... | Why that's wrong | |---|---| | Send all 200 raw issues to the AI without filtering | Bot issues, PRs, and zero-engagement noise inflate cluster counts and waste context. Filter locally first. | | Use comment count as the primary demand signal | Comments include maintainer responses, off-topic discussion, and spam. reactions["+1"] is the cleanest buyer signal. | | Paraphrase issue titles when summarizing clusters | Paraphrasing loses the buyer's exact language, which is the entire point. Use verbatim issue titles. | …
Read the whole file at its exact version.
How to install
mdr add varnan-tech/opendirectory/gh-issue-to-demand-signal@sha256:68e6e790cae53abaThe line at the top of this page pins the label git:20260916.a03d635, 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_2jvbpd7xczf6vzmo)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Apr 21, 2026 and Sep 16, 2026, about one every 148 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.a03d635 latest | 2026-09-16 | a03d635 | 23,084 B | B | view · diff |
| git:20260421.259d463 | 2026-04-21 | 259d463 | 23,141 B | B | view |
Audit of the latest version
- fail: No instruction to read or print local credentials (matched: print("Add GITHUB_TOKEN to your .env)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (23084 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 base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
varnan-tech/opendirectory · 699 stars · license MIT · pushed 2026-10-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2jvbpd7xczf6vzmo GET https://markdownregistry.com/api/v1/resolve?ref=varnan-tech/opendirectory/gh-issue-to-demand-signal GET https://markdownregistry.com/api/v1/blob/68e6e790cae53aba91351517ec07f993ee3626d925e3152c5814f7cc15d22c6d
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.