gh-issue-to-demand-signal

gh-issue-to-demand-signal is a skill for Claude Code from Varnan-Tech/opendirectory. It costs 154 tokens per session (6,038 once invoked), scanned A, original, MIT.

A demand-analysis report built from the open issues in a competitor’s public GitHub repository, where GitHub is a platform for hosting and discussing software code.

In plain words
What is it for?
Use it to study a competitor’s public repository, identify recurring user requests, and create a report for product or go-to-market messaging. It stops when too few issues remain for reliable grouping.
Why use it?
It filters noisy issues, groups the remaining requests into demand categories, and ranks them using engagement signals. This helps reveal unmet needs without manually reading every issue.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Gemini CLI.

Part of the opendirectory plugin — 58 skills shipped together

Good fit Use it to study a competitor’s public repository, identify recurring user requests, and create a report for product or go-to-market messaging. It stops when too few issues remain for reliable grouping.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/varnan-tech/opendirectory/gh-issue-to-demand-signal
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Varnan-Tech/opendirectory --skill gh-issue-to-demand-signal
Clone the repo
git clone --depth 1 https://github.com/Varnan-Tech/opendirectory

Made for: Claude Code.

Or install opendirectory, the plugin that ships this one along with the rest of its 58 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for gh-issue-to-demand-signal

README.md
[![agentmods](https://agentmods.dev/badge/skills/varnan-tech/opendirectory/gh-issue-to-demand-signal/github.svg)](https://agentmods.dev/skills/varnan-tech/opendirectory/gh-issue-to-demand-signal)
Your own site
<a href="https://agentmods.dev/skills/varnan-tech/opendirectory/gh-issue-to-demand-signal"><img src="https://agentmods.dev/badge/skills/varnan-tech/opendirectory/gh-issue-to-demand-signal/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for gh-issue-to-demand-signal

Your own site · 80×15
<a href="https://agentmods.dev/skills/varnan-tech/opendirectory/gh-issue-to-demand-signal"><img src="https://agentmods.dev/badge/skills/varnan-tech/opendirectory/gh-issue-to-demand-signal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 154 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,038 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 4 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Privilege Escalation · line 112
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • high Tool Misuse · line 635
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • medium Excessive Agency · line 26
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Data Exfiltration · line 100
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00154 $0.06038
Opus 5 $0.00077 $0.03019
Sonnet 5 $0.00031 $0.01208
Haiku 4.5 $0.00015 $0.00604

Measured 12d ago against content hash 66822041ae8c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

gh-issue-to-demand-signal scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

import json, urllib.request, os, sys
skills/gh-issue-to-demand-signal/SKILL.md · 639 lines

How it starts

The opening of the file, as written. The whole thing — 639 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.
Continue past Step 4 if fewer than 10 issues remain after filtering Under 10 issues means the repo is too small or the wrong URL was given. Clustering on sparse data produces meaningless categories.
Include pull requests in the analysis The GitHub Issues endpoint returns PRs too. Filter by checking that the pull_request key is absent on the issue object.
Mark an issue as ignored demand without checking all 3 criteria All three must be true: reactions >= 10, age >= 180 days, no planned/in-progress/roadmap label. Missing one criterion disqualifies the issue.

Step 1: Setup Check

echo "GITHUB_TOKEN: ${GITHUB_TOKEN:-not set, unauthenticated rate limit applies (60 req/hr)}"

If GITHUB_TOKEN is not set: Continue. Tell the user: "GITHUB_TOKEN is not set. Unauthenticated rate limit is 60 requests/hour -- enough for 2 fetches before hitting the limit. For repeated use, add a token at github.com/settings/tokens (no scopes needed for public repos)."

Read the full file on GitHub · 639 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 639 lines · 154 tokens per session scan A 66822041ae8c

Subscribe to this mod's changes

gh-issue-to-demand-signal is a skill published in the GitHub repository Varnan-Tech/opendirectory (639 stars, last pushed 26d ago), licensed MIT. It adds 154 tokens to every session and 6,038 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

content-style

Writing Reddit-native content that sounds human, avoids AI tells, and delivers value through structure and specificity. Applies to workshop posts, definitive model guides, research megathreads, and community FYI/update posts.

AtlasOmnia/donna-starter · 37 tokens

coding-worktree-recovery

Use this skill when coding-agent work is interrupted, an agent exits without a clean commit, multiple controllers target the same checkout, or the checkout produces inconsistent file/Git behavior.

AtlasOmnia/donna-starter · 56 tokens

macos-storage-management

Safely reclaim local Mac storage without mistaking cloud placeholders for resident data, losing File Provider content, or flattening metadata onto an incompatible external filesystem.

AtlasOmnia/donna-starter · 22 tokens

hermes-mnemosyne

Mnemosyne is Hermes' primary local-first memory engine — SQLite with vector + FTS5 hybrid search, 19+ tools, auto-consolidation, and a standalone CLI. It's a pip-installed plugin (not a built-in toolset) discovered via $HERMESHOME/plugins/mnemosyne/.

AtlasOmnia/donna-starter · 30 tokens

skill-auditor

Audit any Hermes skill file and assign a quality grade based on clarity, completeness, tool guidance, and shareability. Returns specific fix suggestions ranked by impact.

AtlasOmnia/donna-starter · 64 tokens

marketplace-purchase-vetting

Use this when the user asks whether a local listing is a scam, "too good to be true," worth looking at, or a good deal. Also use this when he asks you to find options — search/discover candidates, then vet the best ones. The goal is not a generic buying guide; it is a practical risk read with clear next steps.

AtlasOmnia/donna-starter · 72 tokens