github-discussion-to-devrel-content

​

Install

npx "@opendirectory.dev/skills" install github-discussion-to-devrel-content --target claude

npx skills add Varnan-Tech/opendirectory --skill github-discussion-to-devrel-content

/plugin marketplace add Varnan-Tech/opendirectory
/plugin install opendirectory-gtm-skills@opendirectory-marketplace

​

What It Does

• Scans your own repo’s Discussions (not competitors’ — that’s gh-issue-to-demand-signal)
• Clusters recurring confusion by underlying concept, not surface keywords
• Ranks each cluster by frequency, engagement, recency, and unanswered rate
• Drafts the actual FAQ / doc fix as a Markdown snippet you can paste into your docs
• Generates a specific content angle and outline for each content opportunity
• Flags unanswered community pain as ⚠️ URGENT so you know what’s bleeding
• Refuses to fabricate patterns when data is thin (low-signal guard built in)

​

What It Does NOT Do

• Does not mine competitor repos — use gh-issue-to-demand-signal for outbound GTM signals
• Does not write full-length blog posts or published docs pages — use noise2blog to expand a draft into a finished asset
• Does not post to LinkedIn, Twitter, or any platform
• Does not predict SEO, engagement, or content performance outcomes
• Does not access private repositories

​

Requirements

​

Setup

cp .env.example .env
# Edit .env and add your GITHUB_TOKEN

​

How to Use

​

Step 1 — Fetch Discussions

# Basic usage (last 90 days, all categories, min 3 comments)
python scripts/fetch_discussions.py --repo owner/repo

# Filter to Q&A category only
python scripts/fetch_discussions.py --repo owner/repo --category "Q&A"

# Docs gaps only, last 60 days
python scripts/fetch_discussions.py --repo owner/repo --days-back 60 --mode docs

# Content opportunities only
python scripts/fetch_discussions.py --repo owner/repo --mode content

# Full GitHub URL also accepted
python scripts/fetch_discussions.py --repo https://github.com/owner/repo

​

Step 2 — Run the Skill

"Run the github-discussion-to-devrel-content skill and produce the DevRel backlog."

"Analyze discussions_raw.json and generate devrel-backlog.md"

​

CLI Options

​

Output

• Priority score (0–100, relative ranking within this run)
• Frequency and engagement metrics
• A verbatim evidence quote from the thread
• A direct link to the source discussion
• A ready-to-paste Draft FAQ / Doc Update as a Markdown snippet
• ⚠️ URGENT badge if the community pain is unresolved

• A working content title and type (blog post, tutorial, FAQ entry, Twitter thread, video script)
• Why this matters for the founder
• A verbatim evidence quote and source link
• A Recommended Angle and 3–4 point outline tied to the community confusion

Note on scores: Priority scores are relative rankings within this analysis run, not absolute quality measures. A score of 84 ranks higher than a score of 71 in this dataset. Scores are not comparable across different repos or different run configurations.

​

Project Structure

github-discussion-to-devrel-content/
├── SKILL.md
├── README.md
├── .env.example
├── scripts/
│   └── fetch_discussions.py
├── evals/
│   └── evals.json
└── references/
    ├── output-format.md
    └── scoring-guide.md

​

License