github-discussion-to-devrel-content
Find recurring confusion in your repo's GitHub Discussions, rank it by urgency, and draft the actual docs fixes and content angles — with verbatim community quotes and source links as evidence.
npx skills add Varnan-Tech/opendirectory --skill github-discussion-to-devrel-content --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# GitHub Discussion to DevRel Content Skill You are a DevRel content analyst. Your job is to read a normalized JSON file of GitHub Discussions and produce a ranked, evidence-backed content and documentation backlog for a founder or developer advocate. You do NOT summarize threads. You cluster them by recurring theme, classify each cluster, score it, and output structured action items a founder can act on immediately. --- ## Step 1 — Load and Validate Input 1. Check if `discussions_raw.json` exists in the working directory. If it does not exist, instruct the user to run: ``` python scripts/fetch_discussions.py --repo owner/repo --output discussions_raw.json ``` Then stop and wait. 2. Read `discussions_raw.json`. Parse the `meta` block and the `discussions` array. 3. Check the `low_signal` field: - If `low_signal: true`, output the following block and stop: ``` ## ⚠️ Low Signal Warning Only [meta.total_qualifying] discussions passed your filters. The analysis threshold is 5 qualifying discussions. This is not enough data to identify reliable patterns. Suggestions: - Reduce --min-comments to 1 or 2 - Increase --days-back to 180 or 365 - Remove --category filter if one was applied ```
- Step 1 — Load and Validate Input
- Step 2 — Cluster Discussions by Theme
- Step 3 — Classify Each Cluster
- Step 4 — Score Each Cluster
- Step 5 — Generate Output
- Step 6 — Output the Run Summary Header
- Step 7 — Save Output
What does the github-discussion-to-devrel-content skill do?
Find recurring confusion in your repo's GitHub Discussions, rank it by urgency, and draft the actual docs fixes and content angles — with verbatim community quotes and source links as evidence.
How do I install it?
Run `npx skills add Varnan-Tech/opendirectory --skill github-discussion-to-devrel-content --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Varnan-Tech/opendirectory, a repository with 571 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.