Agent Reach
Ootto-AI/claude-content-skills
MUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g.
Plan contribution-first cross-platform launches for eunomia.dev content, GitHub projects, papers, tutorials, demos, and public updates.
Install Content Launch Planner
$ npx skills add eunomia-bpf/eunomia.dev --skill content-launch-planner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install eunomia-bpf/eunomia.dev content-launch-planner --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/eunomia-bpf/eunomia.dev.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/content-launch-planner .claude/skills/content-launch-planner && 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 "content-launch-planner" agent skill from https://github.com/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/content-launch-planner into .claude/skills/content-launch-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-launch-planner", 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/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/content-launch-plannerType 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 eunomia-bpf/eunomia.dev --skill content-launch-planner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install eunomia-bpf/eunomia.dev content-launch-planner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eunomia-bpf/eunomia.dev.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/content-launch-planner .agents/skills/content-launch-planner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "content-launch-planner" agent skill from https://github.com/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/content-launch-planner into .agents/skills/content-launch-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-launch-planner", 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 eunomia-bpf/eunomia.dev --skill content-launch-planner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install eunomia-bpf/eunomia.dev content-launch-planner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eunomia-bpf/eunomia.dev.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/content-launch-planner .cursor/skills/content-launch-planner && 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 "content-launch-planner" agent skill from https://github.com/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/content-launch-planner into .cursor/skills/content-launch-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-launch-planner", 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/eunomia-bpf/eunomia.dev.git --path .agents/skills/content-launch-planner--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 eunomia-bpf/eunomia.dev --skill content-launch-planner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install eunomia-bpf/eunomia.dev content-launch-planner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eunomia-bpf/eunomia.dev.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/content-launch-planner .gemini/skills/content-launch-planner && 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 "content-launch-planner" agent skill from https://github.com/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/content-launch-planner into .gemini/skills/content-launch-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-launch-planner", 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 eunomia-bpf/eunomia.dev content-launch-plannerInstalls 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 eunomia-bpf/eunomia.dev --skill content-launch-planner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/eunomia-bpf/eunomia.dev.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/content-launch-planner .github/skills/content-launch-planner && 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 "content-launch-planner" agent skill from https://github.com/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/content-launch-planner into .github/skills/content-launch-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-launch-planner", 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 eunomia-bpf/eunomia.dev --skill content-launch-planner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install eunomia-bpf/eunomia.dev content-launch-planner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eunomia-bpf/eunomia.dev.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/content-launch-planner .opencode/skills/content-launch-planner && 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 "content-launch-planner" agent skill from https://github.com/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/content-launch-planner into .opencode/skills/content-launch-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-launch-planner", 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
content-launch-planner- GitHub stars
- 236
- Token cost
- ~1.9k tokens
- SKILL.md length
- 937 words
- Files
- 9 (incl. references)
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plan contribution-first cross-platform launches for eunomia.dev content, GitHub projects, papers, tutorials, demos, and public updates.
- Works in 10 steps: Build a strategic source brief first:… → Check for duplicates and current… → Classify the launch tier and reader… → …
- Asked where/when/whether to publish
- SKILL.md covers References, Workflow, Boundaries and Publisher Handoff
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Content Launch Planner is an agent skill from eunomia-bpf/eunomia.dev. Plan contribution-first cross-platform launches for eunomia.dev content, GitHub projects, papers, tutorials, demos, and public updates. Use when asked where/when/whether to publish, whether to do all-platform posting, whether others already posted, how to adapt one artifact into a platform matrix, how to prepare Product Hunt or community launches, or how to coordinate Zhihu/Juejin/X/LinkedIn/Xiaohongshu/Reddit/Hacker News/Lobsters/Medium/DEV publisher skills without posting yet.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `agents/openai.yaml`, `references/external-patterns.md` and `references/launch-assets.md`).
It sits in Marketing & SEO, covering Product launch strategy. It works with GitHub, Xiaohongshu, LinkedIn and Reddit. The repository describes itself as: https://github.com/eunomia-bpf homepage, documents and blogs. The licence is MIT.
When your agent uses it
- Asked where/when/whether to publish
- Whether to do all-platform posting
- Whether others already posted
- How to adapt one artifact into a platform matrix
Example prompts
- “/content-launch-planner”
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
- Build a strategic source brief first: user pain, search/community intent,
- Check for duplicates and current discussion before recommending a community
- Classify the launch tier and reader intent: contribution-first technical
- For long-form blog/tutorial/paper explainers, default to faithful
- Select platforms by fit, not by desire to be everywhere. All-platform plans
- Prepare a per-platform brief: target reader, surface, angle, hook, proof,
- Before browser/editor work, route platform-specific copy drafts to
- For long-form posts on every platform, finish the platform-specific artifact
- Hand off execution to the matching publisher skill with the required browser
- Include a follow-up plan for comments, private messages, GitHub issues,
What it can do on your machine
Read from SKILL.md and the folder at commit 999fe11. 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
No scripts in the folder and no shell commands in SKILL.md.
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.
Context cost
Content Launch Planner loads about 1.9k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 127 tokens; SKILL.md has 937 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from eunomia-bpf/eunomia.dev at commit 999fe11, republished under its MIT licence (© eunomia-bpf). 937 words, ~1,941 tokens.
Download SKILL.mdSave it as
.claude/skills/content-launch-planner/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- content-launch-planner
- description
- Plan contribution-first cross-platform launches for eunomia.dev content, GitHub projects, papers, tutorials, demos, and public updates. Use when asked where/when/whether to publish, whether to do all-platform posting, whether others already posted, how to adapt one artifact into a platform matrix, how to prepare Product Hunt or community launches, or how to coordinate Zhihu/Juejin/X/LinkedIn/Xiaohongshu/Reddit/Hacker News/Lobsters/Medium/DEV publisher skills without posting yet.
Content Launch Planner
Plan the upstream publishing decision before any platform-specific drafting or browser work. This skill decides whether to publish, which platforms fit, what each platform should say, what assets are missing, and which publisher skill should execute each item.
References
Load references according to the task:
- Always load
references/source-and-research.md,references/platform-matrix.md,references/quality-gates.md, andreferences/output-template.md. - Load
references/launch-assets.mdfor project, release, demo, paper, tutorial, or multi-post campaign planning. - Load
references/producthunt.mdonly when Product Hunt is proposed, visible in the browser, or plausibly useful for a tryable product/tool artifact. - Load
references/external-patterns.mdwhen updating this skill or explaining which external skill patterns were absorbed.
Workflow
- Build a strategic source brief first: user pain, search/community intent, current alternatives, unique public evidence, brand pillar, reader outcome, and only then repository evidence, GitHub links, drafts, papers, screenshots, and published/not-published ledgers.
- Check for duplicates and current discussion before recommending a community submission or another post about the same artifact.
- Classify the launch tier and reader intent: contribution-first technical education, project/tool launch, paper/research discussion, tutorial, release note, or follow-up.
- For long-form blog/tutorial/paper explainers, default to faithful syndication: Medium/DEV use the existing English source and Zhihu/Juejin use the existing Chinese source. Preserve the selected source title exactly and keep the body substantively unchanged. Do not rewrite, shorten, expand, reorder, split, localize, or add platform-native openings, examples, or conclusions. Only mechanical rendering fixes and platform metadata are allowed. If the source needs a content fix, update the source first and then syndicate that corrected version. If no suitable source exists in the target language, stop and get explicit translation or rewrite authorization. Visible canonical/source links are optional on every platform.
- Select platforms by fit, not by desire to be everywhere. All-platform plans may recommend "skip" for weak surfaces. For an already published long-form source, X and LinkedIn default to the source link plus one or two sentences that state the core problem, tension, or result. Do not plan a separate interpretation, article summary, thread, carousel, or professional story arc unless the user explicitly asks for one.
- Prepare a per-platform brief: target reader, surface, angle, hook, proof, link, media, CTA, risks, and follow-up.
- Before browser/editor work, route platform-specific copy drafts to
draft/media/YYYY-MM-DD/<source-slug>/<platform>.md, using the local date. For long-form syndication that preserves the article body, the draft may reference the canonical source file instead of duplicating it, but it must record the exact source title, links, tags/categories, media, and QA state. Short posts, comments, and replies should include the full paste-ready copy. Do not create standalone figure-inventory, platform-hook, or publish-QA notes. Put paste-ready copy and required upload metadata in the final platform artifact; record only real cross-run exceptions in the datedrun-log.mdor reusable platform lessons in the matching publisher skill. - For long-form posts on every platform, finish the platform-specific artifact
locally before touching the platform editor whenever possible. Generate a
temporary or
draft/media/YYYY-MM-DD/<source-slug>/upload/import artifact with the exact source title, duplicate body H1 removed, image URLs or uploaded images, necessary table/code/formula rendering fallbacks, tags/categories, and links already present in the source. Use the platform editor for import/upload, settings, and QA, not for writing or structural repair. - Hand off execution to the matching publisher skill with the required browser QA state. Do not paste into a platform or publish from this skill unless the user explicitly asks to move from planning into execution.
- Include a follow-up plan for comments, private messages, GitHub issues, corrections, and retrospective notes.
Show full SKILL.md (362 more words)Show less
Boundaries
- Keep public content 80% contribution and 20% promotion. Project mentions are evidence, implementation artifacts, or next steps after useful explanation.
- Do not make substantive changes to syndicated long-form posts. Preserve the source title, opening, section order, claims, examples, and conclusion. Limit platform changes to front matter, duplicate H1 removal, heading-level conversion, image upload/URL repair, code/table/formula rendering, and platform metadata. Add body text or links only when the user explicitly asks or after making the same change in the source article.
- Do not force visible canonical links on any platform. If a platform provides a dedicated canonical field, treat it as a hygiene setting when convenient; do not edit the article body just to add or repair a canonical/source link.
- Preserve the maintainer posture: consulting, research, and helping solve hard technical problems, not selling a product.
- Do not include private strategy, customer claims, fundraising, pricing, partner/customer details, unreleased roadmaps, or unverifiable numbers.
- Social and media platforms are browser-first. Do not use hidden platform APIs, internal endpoints, background requests, or automatic posting tools. Medium and DEV publishing must use the normal web editor/import UI and visible submit buttons, not publish APIs.
- Approval/stop posture follows CLAUDE.md's Precedence Rule and Publishing section (standing authorization to publish once requested; stop only for a genuine external blocker or an explicit planning/draft/preview-only ask).
Publisher Handoff
Use the platform-specific publisher skill after the plan is accepted:
zhihu-publisherfor Zhihu articles, answers, ideas, and AI Works.juejin-publisherfor Juejin developer articles and practical notes.x-publisherfor default link shares with a one- or two-sentence hook; threads, replies, quotes, and articles only when explicitly useful.linkedin-publisherfor default link shares with a one- or two-sentence hook; articles, carousels, longer commentary, and comments only when explicitly useful.xiaohongshu-publisherfor Xiaohongshu visual notes, carousel outlines, title/cover adaptation, and Chinese short-form technical explainers.reddit-publisherfor subreddit submissions and comments.hackernews-publisherfor HN titles, Show HN, Ask HN, and comments.lobsters-publisherfor Lobsters stories, tags, and comments.medium-publisherfor Medium long-form syndication or essays.devto-publisherfor DEV tutorials, series, and comments.
If no publisher skill exists for a recommended channel, output the plan only and say what a future publisher skill would need to handle.
© eunomia-bpf, 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 8 other files (references) in .agents/skills/content-launch-planner of eunomia-bpf/eunomia.dev.
- SKILL.md
- agents/openai.yaml
- references/external-patterns.md
- references/launch-assets.md
- references/output-template.md
- references/platform-matrix.md
- references/producthunt.md
- references/quality-gates.md
- references/source-and-research.md
Open the folder on GitHubat commit 999fe11
Compare with similar skills
Content Launch Planner 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 |
|---|---|---|---|---|---|---|
| Content Launch Planner this skilleunomia-bpf/eunomia.dev | 236 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Agent ReachOotto-AI/claude-content-skills | 122 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Page Play Builderaaron-he-zhu/aaron-marketing-skills | 2.9k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| Competitor Launch Monitorunifapi-agent/agents | 589 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Parasite SEOkostja94/marketing-skills | 1k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Launch Distributionamplitude/builder-skills | 160 | — | ~2.8k | Automated safety check: Pass | None |
Similar skills
Page Play Builder
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "build programmatic SEO pages", "generate pages at scale", "rank on a high-authority third-party site", "borrow domain authority", "build a vs /…
Competitor Launch Monitor
unifapi-agent/agents
When the user wants to track a named competitor's launch or announcement and the public reaction to it across X, LinkedIn, YouTube, Reddit, and news.
Parasite SEO
kostja94/marketing-skills
When the user wants to choose or execute third-party platform SEO (high-authority sites for rankings or backlinks).
Launch Distribution
amplitude/builder-skills
Plan and execute multi-channel distribution for product launches across X/Twitter, Reddit, LinkedIn, Hacker News, and other platforms.
Dropspace
LeoYeAI/openclaw-master-skills
Create and publish social media launches via the Dropspace API.
More from eunomia-bpf/eunomia.dev
All 18 skills in this repoEunomia Community Radar
eunomia-bpf/eunomia.dev
Monitor approved eBPF, Linux, observability, and AI-infrastructure communities through watchlist-opted-in read-only Slack archives plus ordinary visible browser UI, turn the strongest daily…
Eunomia Research Report
eunomia-bpf/eunomia.dev
Research, write, validate, and publish source-grounded Eunomia Daily Reports for technical readers.
Juejin Publisher
eunomia-bpf/eunomia.dev
Prepare or publish eunomia.dev Markdown articles on Juejin. An agent skill from eunomia-bpf/eunomia.dev.
Devto Publisher
eunomia-bpf/eunomia.dev
Prepare or publish eunomia.dev Markdown articles on DEV Community through faithful long-form syndication.
Eunomia Social Radar
eunomia-bpf/eunomia.dev
Monitor the continuing public performance and conversation around Eunomia blogs, reports, projects, and platform posts.
Hackernews Publisher
eunomia-bpf/eunomia.dev
Prepare or publish Hacker News submissions and follow-up drafts for eunomia.dev content, GitHub projects, papers, demos, and Show HN style launches.
Related
Works with
Categories
Questions about Content Launch Planner
What does Content Launch Planner do?
Plan contribution-first cross-platform launches for eunomia.dev content, GitHub projects, papers, tutorials, demos, and public updates. dev.dev content, GitHub projects, papers, tutorials, demos, and public updates.
When should I use Content Launch Planner?
Content Launch Planner fits situations like: asked where/when/whether to publish; whether to do all-platform posting; whether others already posted; how to adapt one artifact into a platform matrix.
How do I install Content Launch Planner in Claude Code?
Run `npx skills add eunomia-bpf/eunomia.dev --skill content-launch-planner -a claude-code`. Or copy the skill folder (.agents/skills/content-launch-planner in eunomia-bpf/eunomia.dev) into .claude/skills/content-launch-planner in your project. Claude Code loads it when a task matches its description.
How do I install Content Launch Planner in Codex?
Run `npx skills add eunomia-bpf/eunomia.dev --skill content-launch-planner -a codex`. Or copy the skill folder (.agents/skills/content-launch-planner in eunomia-bpf/eunomia.dev) into .agents/skills/content-launch-planner in your project. Codex loads it when a task matches its description.
Can I use Content Launch Planner 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 eunomia-bpf/eunomia.dev --skill content-launch-planner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/content-launch-planner, .gemini/skills/content-launch-planner, .github/skills/content-launch-planner and .opencode/skills/content-launch-planner in your project.
What does Content Launch Planner need to run?
SKILL.md names no scripts, command-line tools or credentials: Content Launch Planner is instructions for the agent only.
Does Content Launch Planner 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 Content Launch Planner 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. Review the folder before installing.
What licence does Content Launch Planner use?
Content Launch Planner 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 Content Launch Planner use?
About 1.9k tokens (SKILL.md is roughly 7.8k 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 8.6k tokens, read only when the agent opens those files.
What are the alternatives to Content Launch Planner?
Skills that share tags, products or a category with Content Launch Planner: Agent Reach (Ootto-AI/claude-content-skills, 122 stars), Page Play Builder (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Competitor Launch Monitor (unifapi-agent/agents, 589 stars) and Parasite SEO (kostja94/marketing-skills, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Content Launch Planner?
eunomia-bpf (a GitHub organization) maintains it in eunomia-bpf/eunomia.dev, which has 236 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 9, 2026.
Source: eunomia-bpf/eunomia.dev on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.