Content Launch Planner
eunomia-bpf/eunomia.dev
Plan contribution-first cross-platform launches for eunomia.dev content, GitHub projects, papers, tutorials, demos, and public updates.
When the user wants to market an open source project authentically.
$ npx skills add sickn33/agentic-awesome-skills --skill open-source-marketing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills open-source-marketing --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/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/open-source-marketing .claude/skills/open-source-marketing && 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 "open-source-marketing" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/open-source-marketing into .claude/skills/open-source-marketing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "open-source-marketing", 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/sickn33/agentic-awesome-skills/tree/main/skills/open-source-marketingType 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 sickn33/agentic-awesome-skills --skill open-source-marketing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills open-source-marketing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/open-source-marketing .agents/skills/open-source-marketing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "open-source-marketing" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/open-source-marketing into .agents/skills/open-source-marketing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "open-source-marketing", 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 sickn33/agentic-awesome-skills --skill open-source-marketing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills open-source-marketing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/open-source-marketing .cursor/skills/open-source-marketing && 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 "open-source-marketing" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/open-source-marketing into .cursor/skills/open-source-marketing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "open-source-marketing", 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/sickn33/agentic-awesome-skills.git --path skills/open-source-marketing--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 sickn33/agentic-awesome-skills --skill open-source-marketing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills open-source-marketing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/open-source-marketing .gemini/skills/open-source-marketing && 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 "open-source-marketing" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/open-source-marketing into .gemini/skills/open-source-marketing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "open-source-marketing", 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 sickn33/agentic-awesome-skills open-source-marketingInstalls 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 sickn33/agentic-awesome-skills --skill open-source-marketing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/open-source-marketing .github/skills/open-source-marketing && 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 "open-source-marketing" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/open-source-marketing into .github/skills/open-source-marketing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "open-source-marketing", 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 sickn33/agentic-awesome-skills --skill open-source-marketing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sickn33/agentic-awesome-skills open-source-marketing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/open-source-marketing .opencode/skills/open-source-marketing && 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 "open-source-marketing" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/open-source-marketing into .opencode/skills/open-source-marketing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "open-source-marketing", 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.
open-source-marketingWhen the user wants to market an open source project authentically.
Open Source Marketing is an agent skill from sickn33/agentic-awesome-skills. When the user wants to market an open source project authentically. Trigger phrases include "open source marketing," "OSS marketing," "GitHub marketing," "promote my library," "grow stars," "launch open source," "open source growth," or "contributor marketing."
Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).
It sits in Marketing & SEO, covering Product launch strategy. It works with GitHub. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.
Read from SKILL.md and the folder at commit b84d35a. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comconventionalcommits.orgAlso links to:
octolens.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Open Source Marketing loads about 3.2k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 1,035 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.
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.
The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 1,035 words, ~3,169 tokens.
.claude/skills/open-source-marketing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Use this skill when you need when the user wants to market an open source project authentically. Trigger phrases include "open source marketing," "OSS marketing," "GitHub marketing," "promote my library," "grow stars," "launch open source," "open source growth," or "contributor marketing.".
This skill helps you market open source projects without being cringe. Covers GitHub optimization, community building, contributor experience, launch strategies, and sustainable growth.
Load your audience context first. Read .agents/developer-audience-context.md to understand:
If the context file doesn't exist, run the developer-audience-context skill first.
| Works | Doesn't Work |
|---|---|
| Building in public | Spamming "check out my project" |
| Solving real problems | Building solutions seeking problems |
| Genuine community engagement | Transactional follows/unfollows |
| Great docs and DX | "The code is self-documenting" |
| Celebrating contributors | Taking sole credit |
| Consistent presence | Launch and disappear |
Growth = (Real value) × (Discoverability) × (First-use experience)If any factor is zero, growth is zero.
Your README is your landing page. Optimize it.
Structure:
# Project Name
[One-line description that explains what it does]
[Badges: build status, version, license, downloads]
[Screenshot or GIF showing it in action]
## Why [Project Name]?
- ✅ [Benefit 1 - specific, not fluffy]
- ✅ [Benefit 2]
- ✅ [Benefit 3]
## Quick Start
\`\`\`bash
npm install project-name
\`\`\`
\`\`\`javascript
// 5 lines that show immediate value
\`\`\`
## Installation
[Detailed installation for all platforms]
## Usage
[Core usage patterns with examples]
## Documentation
[Link to full docs]
## Contributing
We love contributions! See [CONTRIBUTING.md](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/open-source-marketing/CONTRIBUTING.md).
## License
[License type] - see [LICENSE](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/open-source-marketing/LICENSE)| Element | Why It Matters |
|---|---|
| Clear name | Memorable, searchable, spellable |
| One-liner | "A [type] for [audience] that [does what]" |
| Badges | Social proof, health signals |
| Visual | GIF > Screenshot > Nothing |
| Quick start | <5 lines to first value |
| Why this? | Differentiation from alternatives |
| Installation | All platforms, copy-paste |
| Examples | Real use cases, not contrived |
| Docs link | More detail available |
| Contributing | Community welcome |
| Element | Best Practice |
|---|---|
| Description | 100 chars max, keyword-rich |
| Topics | 5-10 relevant tags for discoverability |
| Website | Link to docs or landing page |
| Releases | Semantic versioning, changelogs |
| Issues | Templates for bugs/features |
| Discussions | Enable for community Q&A |
| Sponsors | Enable if you want funding |
Bug report template:
---
name: Bug Report
about: Report a bug to help us improve
---
## Bug Description
[Clear description]
## Steps to Reproduce
1.
2.
3.
## Expected Behavior
[What should happen]
## Actual Behavior
[What actually happens]
## Environment
- OS:
- Node version:
- Package version:
## Additional Context
[Screenshots, logs, etc.]Feature request template:
---
name: Feature Request
about: Suggest an idea for this project
---
## Problem
[What problem does this solve?]
## Proposed Solution
[How would you like it to work?]
## Alternatives Considered
[Other approaches you've thought about]
## Additional Context
[Examples, mockups, etc.]| Platform | Best For | Setup Effort |
|---|---|---|
| GitHub Discussions | Q&A, announcements | Low |
| Discord | Real-time chat, community feel | Medium |
| Slack | Enterprise communities | Medium |
| Forum (Discourse) | Async, searchable discussions | High |
Start with GitHub Discussions. Add Discord when you have 50+ active users.
| Principle | Implementation |
|---|---|
| Be responsive | Respond to issues within 48 hours (even if just "looking into it") |
| Celebrate contributions | Thank every contributor publicly |
| Be transparent | Share roadmap, explain decisions |
| Set expectations | Clear SLA for maintainer response |
| Welcome newcomers | "good first issue" labels, mentorship |
User → Star → Issue → PR → Regular Contributor → MaintainerOptimize each transition:
| Transition | How to Improve |
|---|---|
| User → Star | Great README, visible value |
| Star → Issue | Clear issue templates, welcoming tone |
| Issue → PR | "good first issue" labels, CONTRIBUTING.md |
| PR → Regular | Quick review, encouraging feedback |
| Regular → Maintainer | Trust, shared ownership |
# Contributing to [Project]
First off, thanks for considering contributing! ❤️
## Quick Start
1. Fork the repo
2. Clone your fork
3. Install dependencies: `npm install`
4. Create a branch: `git checkout -b my-feature`
5. Make your changes
6. Run tests: `npm test`
7. Commit: `git commit -m "Add my feature"`
8. Push: `git push origin my-feature`
9. Open a Pull Request
## Development Setup
[Detailed setup instructions]
## Code Style
- We use [Prettier/ESLint config]
- Run `npm run lint` before committing
- [Other conventions]
## Commit Messages
We follow [Conventional Commits](https://conventionalcommits.org/):
- `feat: add new feature`
- `fix: resolve bug`
- `docs: update readme`
- `chore: update dependencies`
## Pull Request Process
1. Update docs if needed
2. Add tests for new features
3. Ensure CI passes
4. Get one approval
## Good First Issues
Look for issues labeled `good first issue` — these are great starting points!
## Questions?
Open a Discussion or reach out on Discord.Create genuinely approachable issues:
| Good | Not Good |
|---|---|
| "Add TypeScript types for X function" | "Refactor the entire codebase" |
| "Fix typo in README" | "Performance optimization" |
| "Add test for Y method" | "Debug intermittent CI failure" |
| "Update dependency Z" | "Implement feature from RFC" |
For each good first issue:
| Task | Done? |
|---|---|
| README polished | ☐ |
| Quick start works | ☐ |
| Docs exist | ☐ |
| 3+ examples/demos | ☐ |
| Tests passing | ☐ |
| License chosen | ☐ |
| CONTRIBUTING.md | ☐ |
| Issue templates | ☐ |
| Social preview image | ☐ |
| 5-10 GitHub topics | ☐ |
Timeline:
| Time | Action |
|---|---|
| Day before | Final README review, prep all posts |
| Launch morning | HN post (best: 6-8am PT, Tuesday-Thursday) |
| +1 hour | Twitter thread |
| +2 hours | Reddit post to relevant subreddits |
| Throughout day | Respond to all comments/questions |
| End of day | Thank everyone, share metrics |
Hacker News:
Reddit:
Twitter/X:
Dev.to / Hashnode:
| Week | Focus |
|---|---|
| Week 1 | Respond to all feedback, fix bugs |
| Week 2 | Blog post: "What I learned from launch" |
| Week 3 | Start regular updates, ship new feature |
| Month 1 | Community building, contributor docs |
| Ongoing | Consistent presence, regular releases |
| Tactic | Effort | Impact | Timeline |
|---|---|---|---|
| SEO-optimized docs | Medium | High | 3-6 months |
| Integration tutorials | Medium | High | 1-2 months |
| Conference talks | High | Medium | 3-6 months |
| Comparison content | Low | Medium | 1-2 months |
| Guest blog posts | Medium | Medium | 1-2 months |
| Newsletter features | Low | Low-Medium | 2-4 weeks |
| Twitter presence | Medium | Medium | Ongoing |
| Content Type | Purpose |
|---|---|
| "Why we built X" | Launch story, motivation |
| "X vs Y vs Z" | Capture comparison searches |
| "Migrating from Y to X" | Convert competitor users |
| "X + [Popular Tool]" | Capture integration searches |
| "How We Use X at [Company]" | Social proof, real use case |
| "X Performance Benchmarks" | Technical credibility |
| Risk | Mitigation |
|---|---|
| Overwhelming issues | Set response SLA expectations |
| Feature demands | Public roadmap, RFC process |
| Solo maintenance | Actively recruit co-maintainers |
| Always-on pressure | Scheduled "office hours" vs. 24/7 |
| Negative feedback | Code of conduct, moderation |
| Vanity Metric | Value Metric |
|---|---|
| Stars | Active issues + PRs |
| Forks | Returned contributors |
| Downloads | Weekly active users |
| Twitter followers | Community engagement |
| Metric | Where to Find It |
|---|---|
| Stars over time | GitHub Insights, Star History |
| Clones | GitHub Traffic |
| Referrers | GitHub Traffic |
| npm downloads | npm-stat.com |
| Community size | Discord/Slack member count |
| Contributor count | GitHub Insights |
| Issue response time | Manual tracking |
| Tool | Use Case |
|---|---|
| Octolens | Monitor mentions of your project across GitHub, HN, Reddit, Twitter, and Stack Overflow. Track competitor projects. Find contributors asking questions. |
| Star History | Track star growth over time |
| npm-stat | Download statistics |
| GitHub Traffic | Views, clones, referrers |
| Shield.io | Dynamic badges |
| All Contributors | Recognize all contributors |
| Probot | Automate GitHub workflows |
developer-audience-context — Know who your users arecommunity-building — Build Discord/Slack communitydevrel-content — Create supporting contentdeveloper-advocacy — Conference talks, podcastshacker-news-strategy — Launch and engage on HN© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in skills/open-source-marketing of sickn33/agentic-awesome-skills.
Open the folder on GitHubat commit b84d35a
We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.
Open Source Marketing 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 |
|---|---|---|---|---|---|---|
| Open Source Marketing this skillsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Content Launch Plannereunomia-bpf/eunomia.dev | 236 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Daily HuntMagicCube/agentara | 516 | — | ~1.3k | Automated safety check: Pass | None | |
| News Aggregator Skillsundial-org/awesome-openclaw-skills | 663 | — | ~1.3k | Automated safety check: Pass | None | |
| Gingiris Growth Playbooksdavepoon/buildwithclaude | 3.6k | — | ~458 | Automated safety check: Pass | MIT | |
| Dx RoasterVarnan-Tech/opendirectory | 674 | — | ~2.5k | Automated safety check: Pass | MIT |
eunomia-bpf/eunomia.dev
Plan contribution-first cross-platform launches for eunomia.dev content, GitHub projects, papers, tutorials, demos, and public updates.
MagicCube/agentara
Daily tech product and open-source discovery digest. An agent skill from MagicCube/agentara.
sundial-org/awesome-openclaw-skills
Comprehensive news aggregator that fetches, filters, and deeply analyzes real-time content from 8 major sources: Hacker News, GitHub Trending, Product Hunt, 36Kr, Tencent News, WallStreetCN, V2EX…
davepoon/buildwithclaude
Open-source growth playbooks for AI products, B2B SaaS, and developer tools.
Varnan-Tech/opendirectory
Brutally honest developer-experience audit for a GitHub repo.
NVIDIA/NemoClaw
Remove bracketed NemoClaw tags from GitHub issue and PR titles.
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
sickn33/agentic-awesome-skills
Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.
sickn33/agentic-awesome-skills
Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.
sickn33/agentic-awesome-skills
Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.
sickn33/agentic-awesome-skills
Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.
sickn33/agentic-awesome-skills
Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.
Works with
Categories
When the user wants to market an open source project authentically. Open Source Marketing is an agent skill from sickn33/agentic-awesome-skills. When the user wants to market an open source project authentically.
Open Source Marketing fits situations like: wants to market an open source project authentically; phrases include open source marketing; GitHub marketing; promote my library.
Run `npx skills add sickn33/agentic-awesome-skills --skill open-source-marketing -a claude-code`. Or copy the skill folder (skills/open-source-marketing in sickn33/agentic-awesome-skills) into .claude/skills/open-source-marketing in your project. Claude Code loads it when a task matches its description.
Run `npx skills add sickn33/agentic-awesome-skills --skill open-source-marketing -a codex`. Or copy the skill folder (skills/open-source-marketing in sickn33/agentic-awesome-skills) into .agents/skills/open-source-marketing in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill open-source-marketing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/open-source-marketing, .gemini/skills/open-source-marketing, .github/skills/open-source-marketing and .opencode/skills/open-source-marketing in your project.
SKILL.md names no scripts, command-line tools or credentials: Open Source Marketing is instructions for the agent only. Our summary lists: Node.js.
SKILL.md names 3 domains. In commands or code: github.com and conventionalcommits.org; the agent is likely to contact these when it follows the instructions. As links in the text: octolens.com. This is read from the text; nothing was executed.
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.
Open Source Marketing is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Open Source Marketing: Content Launch Planner (eunomia-bpf/eunomia.dev, 236 stars), Daily Hunt (MagicCube/agentara, 516 stars), News Aggregator Skill (sundial-org/awesome-openclaw-skills, 663 stars) and Gingiris Growth Playbooks (davepoon/buildwithclaude, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.
Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.