PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
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.
MITAuto-check passed
Install GitHub Discussion To Devrel Content
$ npx skills add Varnan-Tech/opendirectory --skill github-discussion-to-devrel-content -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Varnan-Tech/opendirectory github-discussion-to-devrel-content --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Varnan-Tech/opendirectory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/github-discussion-to-devrel-content .claude/skills/github-discussion-to-devrel-content && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "github-discussion-to-devrel-content" agent skill from https://github.com/Varnan-Tech/opendirectory/tree/main/skills/github-discussion-to-devrel-content into .claude/skills/github-discussion-to-devrel-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-discussion-to-devrel-content", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Varnan-Tech/opendirectory/tree/main/skills/github-discussion-to-devrel-contentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Varnan-Tech/opendirectory --skill github-discussion-to-devrel-content -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Varnan-Tech/opendirectory github-discussion-to-devrel-content --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Varnan-Tech/opendirectory.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/github-discussion-to-devrel-content .agents/skills/github-discussion-to-devrel-content && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "github-discussion-to-devrel-content" agent skill from https://github.com/Varnan-Tech/opendirectory/tree/main/skills/github-discussion-to-devrel-content into .agents/skills/github-discussion-to-devrel-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-discussion-to-devrel-content", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Varnan-Tech/opendirectory --skill github-discussion-to-devrel-content -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Varnan-Tech/opendirectory github-discussion-to-devrel-content --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Varnan-Tech/opendirectory.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/github-discussion-to-devrel-content .cursor/skills/github-discussion-to-devrel-content && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "github-discussion-to-devrel-content" agent skill from https://github.com/Varnan-Tech/opendirectory/tree/main/skills/github-discussion-to-devrel-content into .cursor/skills/github-discussion-to-devrel-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-discussion-to-devrel-content", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Varnan-Tech/opendirectory.git --path skills/github-discussion-to-devrel-content--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Varnan-Tech/opendirectory --skill github-discussion-to-devrel-content -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Varnan-Tech/opendirectory github-discussion-to-devrel-content --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Varnan-Tech/opendirectory.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/github-discussion-to-devrel-content .gemini/skills/github-discussion-to-devrel-content && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "github-discussion-to-devrel-content" agent skill from https://github.com/Varnan-Tech/opendirectory/tree/main/skills/github-discussion-to-devrel-content into .gemini/skills/github-discussion-to-devrel-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-discussion-to-devrel-content", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Varnan-Tech/opendirectory github-discussion-to-devrel-contentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Varnan-Tech/opendirectory --skill github-discussion-to-devrel-content -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Varnan-Tech/opendirectory.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/github-discussion-to-devrel-content .github/skills/github-discussion-to-devrel-content && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "github-discussion-to-devrel-content" agent skill from https://github.com/Varnan-Tech/opendirectory/tree/main/skills/github-discussion-to-devrel-content into .github/skills/github-discussion-to-devrel-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-discussion-to-devrel-content", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Varnan-Tech/opendirectory --skill github-discussion-to-devrel-content -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Varnan-Tech/opendirectory github-discussion-to-devrel-content --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Varnan-Tech/opendirectory.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/github-discussion-to-devrel-content .opencode/skills/github-discussion-to-devrel-content && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "github-discussion-to-devrel-content" agent skill from https://github.com/Varnan-Tech/opendirectory/tree/main/skills/github-discussion-to-devrel-content into .opencode/skills/github-discussion-to-devrel-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-discussion-to-devrel-content", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
github-discussion-to-devrel-content- GitHub stars
- 674
- Token cost
- ~1.6k tokens
- SKILL.md length
- 793 words
- Files
- 8 (incl. scripts, references)
- Skills in repo
- 61
- Repo updated
- First seen
- Licence
- MIT
At a glance
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.
- Works in 7 steps: Load and Validate Input → Cluster Discussions by Theme → Classify Each Cluster → …
- SKILL.md covers Step 1 — Load and Validate Input, Step 2 — Cluster Discussions…, Step 3 — Classify Each Cluster and Step 4 — Score Each Cluster, plus 3 more sections
- Runs Python scripts from its folder; calls python
What it does
GitHub Discussion To Devrel Content is an agent skill from Varnan-Tech/opendirectory. 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.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts and reference files (for example `README.md`, `evals/evals.json` and `references/output-format.md`). Compatibility notes: ["claude-code","gemini-cli","github-copilot"]
It works with GitHub. The repository describes itself as: AI Agent Skills built for Founders who hate Marketing. The licence is MIT.
Example prompts
- “/github-discussion-to-devrel-content”
Requirements
- Python 3
- Compatibility (from SKILL.md): ["claude-code","gemini-cli","github-copilot"]
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 62e437a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
["claude-code","gemini-cli","github-copilot"]
From compatibility in the SKILL.md frontmatter.
Context cost
GitHub Discussion To Devrel Content loads about 1.6k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 57 tokens; SKILL.md has 793 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from Varnan-Tech/opendirectory at commit 62e437a, republished under its MIT licence (© Varnan-Tech). 793 words, ~1,616 tokens.
Download SKILL.mdSave it as
.claude/skills/github-discussion-to-devrel-content/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- github-discussion-to-devrel-content
- description
- 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.
- compatibility
- ["claude-code","gemini-cli","github-copilot"]
- author
- ajaycodesitbetter
- version
- 1.0.0
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
Check if
discussions_raw.jsonexists 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.jsonThen stop and wait.
Read
discussions_raw.json. Parse themetablock and thediscussionsarray.Check the
low_signalfield:- 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 - Do NOT proceed to analysis if
low_signalis true.
- If
Announce: "Analyzing [meta.total_qualifying] discussions from [meta.repo] (mode: [meta.mode])."
Step 2 — Cluster Discussions by Theme
Read all discussions. Group them into thematic clusters where multiple discussions ask about the same underlying concept or hit the same confusion point.
Rules for clustering:
- A cluster must contain at least 2 discussions to count as a pattern. Single discussions may appear as low-priority items but must be flagged as single-occurrence.
- Do not force discussions into clusters. If a discussion is genuinely unique, leave it as a standalone item.
- Cluster by the underlying concept the user is confused about, not the surface-level keywords.
- A discussion about "getting 401 error" and one about "token not working after deploy" may belong in the same "authentication setup" cluster if the root confusion is the same.
For each cluster, record:
- A short
cluster_label(3–6 words) - The list of
discussion_numbersin the cluster - A
representative_quote— the most clearly-worded expression of the confusion from any thread in the cluster. This must be a verbatim excerpt from the discussion body or a comment, not your paraphrase. - The
primary_source_url— URL of the most-engaged discussion in the cluster
- A short
Step 3 — Classify Each Cluster
For each cluster, assign one of:
docs_gap— The community is asking a question that should be answered in the product documentation. The question has a factual answer.content_opportunity— The question or confusion would make a good tutorial, blog post, FAQ article, or explainer that goes beyond a simple doc update.both— It qualifies as both. Output it in both sections.
Classification rules:
- If the question is "how do I configure X?" →
docs_gap - If the question is "what is the best approach for X in scenario Y?" →
content_opportunity - If the question is asked by 4+ users with no accepted answer → likely
docs_gap - If the discussion spawned a long debate or multiple approaches → likely
content_opportunity
Show full SKILL.md (313 more words)Show less
Step 4 — Score Each Cluster
Read references/scoring-guide.md for the full formula. Summary:
priority_score = (
(frequency_score × 0.35) +
(engagement_score × 0.30) +
(recency_score × 0.15) +
(unanswered_bonus × 0.10) +
(clarity_score × 0.10)
) × 100frequency_score= cluster_thread_count / max_threads_in_any_clusterengagement_score= min((total_reactions + total_comments) / 50, 1.0)recency_score= 1.0 if any thread updated within 7 days, 0.5 if within 30 days, 0.2 if within 90 days, 0.0 otherwiseunanswered_bonus= 1.0 if majority of cluster threads haveis_answered: false, else 0.0clarity_score= your assessment of how clearly the community articulated the confusion (0.0 low, 0.5 moderate, 1.0 high)
Round all scores to the nearest integer. Do not output decimal priority scores.
Step 5 — Generate Output
Read references/output-format.md for the exact Markdown structure.
Output up to 7 items per section, ranked by priority_score descending.
Critical output rules:
- Every item must include
source_url— no exceptions. - Every item must include
evidence_quote— verbatim text from the thread, not a paraphrase. - Do not output a generic "Suggested Action". You must do the work:
- For Docs Gaps: Write the actual Draft FAQ / Doc Update as a Markdown snippet that the founder can copy-paste to solve the confusion. Base it on the accepted answer or consensus in the thread.
- For Content Opportunities: Write the Recommended Angle & Outline. Define the exact angle to take and a 3-4 point outline to address the confusion.
- If the majority of threads in a cluster are unanswered, you MUST include the
**⚠️ URGENT: Unresolved Community Pain**badge before the evidence quote. - Do not use the words: delve, testament, comprehensive, leverage, seamless, in conclusion, it is worth noting.
- Do not claim any content performance outcome (SEO ranking, engagement rate, etc.).
- If a section has fewer than 3 items, note: "Only [N] pattern(s) found for this section. Consider broadening filters."
Step 6 — Output the Run Summary Header
At the top of the report, before any sections, output:
## Run Summary
- **Repo:** [meta.repo]
- **Analysis date:** [today's date]
- **Discussions analyzed:** [meta.total_qualifying]
- **Days of history:** [meta.days_back]
- **Clusters found:** [total clusters]
- **Mode:** [meta.mode]Step 7 — Save Output
Write the full Markdown report to devrel-backlog.md in the working directory.
Announce: "Done. Backlog written to devrel-backlog.md — [N] docs gaps and [N] content opportunities identified."
© Varnan-Tech, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 7 other files (scripts, references) in skills/github-discussion-to-devrel-content of Varnan-Tech/opendirectory.
- SKILL.md
- .env.example
- README.md
- cover.jpeg
- evals/evals.json
- references/output-format.md
- references/scoring-guide.md
- scripts/fetch_discussions.py
Open the folder on GitHubat commit 62e437a
Compare with similar skills
GitHub Discussion To Devrel Content next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| GitHub Discussion To Devrel Content this skillVarnan-Tech/opendirectory | 674 | — | ~1.6k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Diagnosing Superpowers Sessionsobra/superpowers | 296k | 3 repos | ~1.7k | Automated safety check: Pass | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 83k | 5 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Update V8 Versionopeninterpreter/openinterpreter | 69k | 2 repos | ~845 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Diagnosing Superpowers Sessions
obra/superpowers
Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
Update V8 Version
openinterpreter/openinterpreter
Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
More from Varnan-Tech/opendirectory
All 61 skills in this repoPodcast Transcript Fetcher
Varnan-Tech/opendirectory
A skill your agent uses when fetching, searching, or analyzing transcripts from Lenny's Podcast, Dwarkesh Podcast, Cheeky Pint, 20VC, or A16z Podcast.
Graphic Ebook
Varnan-Tech/opendirectory
Creates professionally designed B2B SaaS e-books in HTML + CSS, exported as print-ready PDF.
Where Your Customer Lives
Varnan-Tech/opendirectory
Given a product utility and ICP, researches the internet to find the specific channels.
Docs From Code
Varnan-Tech/opendirectory
Generates and updates README.md and API reference docs by reading your codebase's functions, routes, types, schemas, and architecture.
Graphic Chart
Varnan-Tech/opendirectory
Generates data visualization charts (bar, line, area, pie, doughnut, scatter, radar, treemap) as PNG using Apache ECharts v6.
Graphic Gif
Varnan-Tech/opendirectory
Creates animated looping GIFs from CSS animations (default) or AI image-to-video.
Related
Works with
Questions about GitHub Discussion To Devrel Content
What does GitHub Discussion To Devrel Content 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. GitHub Discussion To Devrel Content is an agent skill from Varnan-Tech/opendirectory. 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 GitHub Discussion To Devrel Content in Claude Code?
Run `npx skills add Varnan-Tech/opendirectory --skill github-discussion-to-devrel-content -a claude-code`. Or copy the skill folder (skills/github-discussion-to-devrel-content in Varnan-Tech/opendirectory) into .claude/skills/github-discussion-to-devrel-content in your project. Claude Code loads it when a task matches its description.
How do I install GitHub Discussion To Devrel Content in Codex?
Run `npx skills add Varnan-Tech/opendirectory --skill github-discussion-to-devrel-content -a codex`. Or copy the skill folder (skills/github-discussion-to-devrel-content in Varnan-Tech/opendirectory) into .agents/skills/github-discussion-to-devrel-content in your project. Codex loads it when a task matches its description.
Can I use GitHub Discussion To Devrel Content in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Varnan-Tech/opendirectory --skill github-discussion-to-devrel-content -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-discussion-to-devrel-content, .gemini/skills/github-discussion-to-devrel-content, .github/skills/github-discussion-to-devrel-content and .opencode/skills/github-discussion-to-devrel-content in your project.
What does GitHub Discussion To Devrel Content need to run?
Going by SKILL.md and its folder, GitHub Discussion To Devrel Content needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3. Compatibility (from SKILL.md): ["claude-code","gemini-cli","github-copilot"].
Does GitHub Discussion To Devrel Content access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is GitHub Discussion To Devrel Content safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does GitHub Discussion To Devrel Content use?
GitHub Discussion To Devrel Content is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does GitHub Discussion To Devrel Content use?
About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.3k tokens, read only when the agent opens those files.
What are the alternatives to GitHub Discussion To Devrel Content?
Skills that share tags, products or a category with GitHub Discussion To Devrel Content: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Diagnosing Superpowers Sessions (obra/superpowers, 296k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars) and Greploop (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains GitHub Discussion To Devrel Content?
Varnan-Tech (a GitHub organization) maintains it in Varnan-Tech/opendirectory, which has 674 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on August 16, 2026.
Source: Varnan-Tech/opendirectory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.