Bibi
JimmyLv/BibiGPT-v1
BibiGPT CLI for summarizing videos, audio, and podcasts directly in the terminal.
When the user wants to do developer advocacy activities including conference talks, live coding, podcasts, and building in public.
$ npx skills add sickn33/agentic-awesome-skills --skill developer-advocacy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills developer-advocacy --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/developer-advocacy .claude/skills/developer-advocacy && 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 "developer-advocacy" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-advocacy into .claude/skills/developer-advocacy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-advocacy", 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/developer-advocacyType 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 developer-advocacy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills developer-advocacy --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/developer-advocacy .agents/skills/developer-advocacy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "developer-advocacy" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-advocacy into .agents/skills/developer-advocacy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-advocacy", 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 developer-advocacy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills developer-advocacy --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/developer-advocacy .cursor/skills/developer-advocacy && 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 "developer-advocacy" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-advocacy into .cursor/skills/developer-advocacy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-advocacy", 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/developer-advocacy--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 developer-advocacy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills developer-advocacy --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/developer-advocacy .gemini/skills/developer-advocacy && 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 "developer-advocacy" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-advocacy into .gemini/skills/developer-advocacy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-advocacy", 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 developer-advocacyInstalls 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 developer-advocacy -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/developer-advocacy .github/skills/developer-advocacy && 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 "developer-advocacy" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-advocacy into .github/skills/developer-advocacy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-advocacy", 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 developer-advocacy -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 developer-advocacy --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/developer-advocacy .opencode/skills/developer-advocacy && 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 "developer-advocacy" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-advocacy into .opencode/skills/developer-advocacy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-advocacy", 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.
developer-advocacyWhen the user wants to do developer advocacy activities including conference talks, live coding, podcasts, and building in public.
Developer Advocacy is an agent skill from sickn33/agentic-awesome-skills. When the user wants to do developer advocacy activities including conference talks, live coding, podcasts, and building in public.
Its SKILL.md is about 3.3k 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 Media & Creative, covering Podcasting. 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 680176d. 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.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
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.
Developer Advocacy loads about 3.3k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 1,198 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 680176d, republished under its MIT licence (© sickn33). 1,198 words, ~3,261 tokens.
.claude/skills/developer-advocacy/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 do developer advocacy activities including conference talks, live coding, podcasts, and building in public. Trigger phrases include "developer advocacy," "devrel," "conference talk," "CFP," "call for papers," "live coding," "podcast," "building in public,"...
This skill helps you with developer advocacy activities: conference talks, live coding demos, podcast appearances, and building in public. Covers talk proposals, demo prep, social presence, and measuring impact.
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.
| Conference Type | Best For | Examples |
|---|---|---|
| Large industry | Brand awareness, reach | KubeCon, AWS re:Invent, React Summit |
| Regional | Local community, accessible | Local meetups, city tech conferences |
| Niche | Targeted audience, expertise | GraphQL Conf, RustConf |
| Company-hosted | Ecosystem presence | Vercel Ship, GitHub Universe |
| Unconferences | Community connection | BarCamps, DevOpsDays |
The winning formula:
Specific Problem + Unique Angle + Clear Takeaways = Accepted TalkCFP Template:
# Title
[Action verb] + [specific outcome] + [with/using what]
Example: "Building Real-Time Features with Edge Functions and WebSockets"
# Abstract (100-200 words)
[Hook: Problem or curiosity gap]
[What you'll cover]
[What attendees will learn/be able to do]
# Description (detailed, for reviewers)
[Problem context]
[Why this approach]
[Talk structure]
[Your credibility to give this talk]
# Outline
- [Time] Introduction / Problem statement
- [Time] Section 1
- [Time] Section 2
- [Time] Section 3
- [Time] Live demo / walkthrough
- [Time] Key takeaways / Q&A
# Audience
[Who this is for]
[Prerequisite knowledge]
[What they'll learn]
# Bio
[Your relevant experience]
[Why you're qualified]| Pattern | Example |
|---|---|
| How I X | "How I Reduced Deploy Time by 80%" |
| X in Y Minutes | "Kubernetes Security in 15 Minutes" |
| The X of Y | "The Psychology of Error Messages" |
| Beyond X | "Beyond Console.log: Modern Debugging" |
| X for Y | "GraphQL for REST Developers" |
| Lessons from X | "Lessons from 1000 Production Outages" |
| Type | Length | Best For |
|---|---|---|
| Lightning | 5-10 min | Single concept, quick demo |
| Standard | 25-45 min | Technical deep-dive |
| Keynote | 45-60 min | Big picture, inspiring |
| Workshop | 2-4 hours | Hands-on learning |
| Panel | 30-60 min | Discussion, multiple perspectives |
| Phase | Tasks |
|---|---|
| 2 months before | Outline, start slides, test demos |
| 1 month before | Draft complete, first practice run |
| 2 weeks before | Slides polished, demos solid, practice 3x |
| 1 week before | Record yourself, get feedback, finalize |
| Day before | Test all tech, backup slides, rest |
| Day of | Arrive early, test A/V, hydrate |
| Risk | Mitigation |
|---|---|
| Internet fails | Pre-record backup, local server |
| Typo freezes you | Practice typing same code 20x |
| Error you can't fix | Have working checkpoints to jump to |
| Runs over time | Time yourself, cut ruthlessly |
| Code too small | Zoom in, use large font (24pt+) |
| Dark theme blinding | Use high-contrast, light-friendly theme |
The 10-3-1 Rule:
Pre-demo checklist:
| Tip | Why |
|---|---|
| Type slowly | Audience needs to follow |
| Narrate what you type | "I'm creating a new handler..." |
| Explain errors | "This error means X, let me fix it" |
| Use snippets | For boilerplate, not core concepts |
| Show the result | Always run the code, show output |
| Checkpoint commits | git checkout checkpoint-1 |
| Approach | How |
|---|---|
| Direct search | "top [your tech] podcasts" |
| Guest networks | Podmatch, Matchmaker.fm |
| Peer asks | "What podcasts do you listen to?" |
| Twitter search | "[topic] podcast episode" |
| Listen Notes | Podcast search engine |
Subject: Guest Idea: [Specific Topic] for [Podcast Name]
Hi [Host Name],
I've been listening to [Podcast] for [time] — loved your episode on [specific episode].
I'd love to come on and talk about [specific topic]. Here's the angle:
[2-3 sentences on what you'd discuss and why it matters to their audience]
A bit about me:
- [Relevant credential 1]
- [Relevant credential 2]
- [Link to past podcast/talk]
Would this be a fit?
[Your name]| Prep Item | Details |
|---|---|
| Research the show | Listen to 2-3 episodes, understand format |
| Research the host | Their interests, style, Twitter |
| Prep talking points | 3-5 main things you want to say |
| Prep stories | Specific examples, not generalities |
| Audio setup | Good mic, quiet room, headphones |
| Water nearby | You'll be talking a lot |
| Do | Don't |
|---|---|
| Tell stories with specifics | Give generic advice |
| Pause before answering | Um and ah nervously |
| Disagree respectfully | Always agree to be polite |
| Promote subtly | Hard sell your product |
| Be concise | Ramble without structure |
| Show enthusiasm | Be monotone |
| Action | Timing |
|---|---|
| Thank the host | Same day |
| Share when published | Immediately |
| Engage with comments | First week |
| Cross-promote | Your newsletter, blog |
| Stay in touch | Ongoing relationship |
| Category | Content Ideas |
|---|---|
| Progress | "Shipped X today, here's what I learned" |
| Challenges | "Stuck on X, tried Y and Z, here's what worked" |
| Decisions | "Why we chose X over Y" |
| Metrics | Revenue, users, growth (transparently) |
| Behind scenes | Team, process, tools |
| Learnings | "Mistake we made and how we fixed it" |
| Format | Platform | Cadence |
|---|---|---|
| Tweet thread | Twitter/X | Daily-weekly |
| Changelog | Blog, Notion, website | Weekly |
| Indie hacker posts | Indie Hackers, HN | Monthly |
| Video update | YouTube, Loom | Weekly-monthly |
| Newsletter | Weekly | |
| Livestream | Twitch, YouTube | Weekly |
| Avoid | Why |
|---|---|
| Customer data | Privacy, trust |
| Team conflicts | Professionalism |
| Security details | Vulnerability |
| Competitor attacks | Looks petty |
| Venting | Not productive |
| Content Type | % of Posts | Example |
|---|---|---|
| Value content | 60% | Tips, tutorials, insights |
| Engagement | 20% | Replies, retweets with commentary |
| Personal | 10% | Behind-the-scenes, personality |
| Promotion | 10% | Your product, talks, content |
| Format | Example |
|---|---|
| Thread | "10 things I learned building X" |
| Hot take | "Unpopular opinion: [opinion]" |
| Quick tip | "TIL: You can do X by..." |
| Question | "What's your favorite way to..." |
| Meme/humor | Tech jokes, relatable content |
| Showcase | "Just shipped X, here's how it works" |
| Appreciation | "Shoutout to @person for..." |
| Action | Frequency |
|---|---|
| Tweet original content | Daily |
| Reply to others | 5-10x daily |
| Quote tweet with value | 2-3x weekly |
| DM interesting people | Weekly |
| Join Twitter Spaces | As relevant |
| Tactic | Implementation |
|---|---|
| Consistency | Post daily, engage daily |
| Niche down | Be known for ONE thing first |
| Reply game | Add value to big accounts' tweets |
| Collaborate | Twitter Spaces, threads together |
| Cross-promote | Newsletter, talks, blog |
| Activity | Metrics |
|---|---|
| Talks | Attendees, feedback scores, recording views |
| Content | Views, shares, engagement |
| Social | Followers, engagement rate, reach |
| Podcasts | Listener estimates, traffic spikes |
| Community | Growth, engagement, sentiment |
Developer advocacy impact is notoriously hard to measure. Proxy metrics:
| Signal | What It Indicates |
|---|---|
| Traffic spikes | Content/talk/podcast drove visits |
| "How did you hear about us?" | Direct attribution |
| Social mentions | Brand awareness |
| Inbound leads quality | Community-qualified leads |
| Conference invites | Growing reputation |
Monthly advocacy report:
# Developer Advocacy Report - [Month]
## Talks & Appearances
- [Talk 1]: [Conference], [Attendees], [Link]
- [Podcast 1]: [Show], [Episode link]
## Content Published
- [Article 1]: [Views], [Engagement]
- [Video 1]: [Views]
## Social Growth
- Twitter: +X followers, Y impressions
- Notable tweets: [Links]
## Community
- Discord/Slack: +X members, Y messages
- Notable threads/discussions
## Learnings
- What worked: [X]
- What didn't: [Y]
- Trying next: [Z]| Level | Focus |
|---|---|
| Junior DA | Content creation, community support, talk prep |
| Developer Advocate | Talks, own content strategy, community building |
| Senior DA | Strategy, mentoring, major conferences |
| Staff DA | Cross-company impact, industry thought leadership |
| Head of DevRel | Team building, strategy, executive alignment |
| Skill | How to Develop |
|---|---|
| Public speaking | Meetups, Toastmasters, practice |
| Writing | Blog consistently, get feedback |
| Video | YouTube, live streaming, improve iteratively |
| Technical depth | Build projects, contribute to OSS |
| Community | Moderate, organize events, connect people |
| Tool | Use Case |
|---|---|
| Octolens | Monitor your name/brand across GitHub, Twitter, Reddit, HN, Stack Overflow. Track conference mentions. Find podcast opportunities. Measure share of voice. |
| Cal.com / Calendly | Schedule podcast appearances |
| StreamYard | Live streaming setup |
| Descript | Video/podcast editing |
| Canva / Figma | Slides and graphics |
| Otter.ai | Transcription for talks |
| Notion | Talk prep, content calendar |
| Buffer / Typefully | Social scheduling |
developer-audience-context — Know who you're reachingdevrel-content — Written content strategycommunity-building — Community managementopen-source-marketing — OSS-specific advocacyhacker-news-strategy — HN engagement© 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/developer-advocacy of sickn33/agentic-awesome-skills.
Open the folder on GitHubat commit 680176d
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.
Developer Advocacy 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 |
|---|---|---|---|---|---|---|
| Developer Advocacy this skillsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.3k | Automated safety check: Pass | MIT | |
| BibiJimmyLv/BibiGPT-v1 | 6.2k | — | ~885 | Automated safety check: Pass | GPL-3.0 | |
| Video Transcribewendy7756/AI-Video-Transcriber | 3.3k | — | ~937 | Automated safety check: Notes | Apache-2.0 | |
| Podcastzarazhangrui/personalized-podcast | 437 | — | ~2.3k | Automated safety check: Notes | None | |
| Video Podcast Maker NanoAgents365-ai/video-podcast-maker | 1.7k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Azure Realtime Podcast Generationmicrosoft/skills | 3.1k | 1 repos | ~947 | Automated safety check: Pass | MIT |
JimmyLv/BibiGPT-v1
BibiGPT CLI for summarizing videos, audio, and podcasts directly in the terminal.
wendy7756/AI-Video-Transcriber
Transcribe and summarize a video or podcast from a URL (YouTube, TikTok, Bilibili, Apple Podcasts, SoundCloud, 30+ platforms) or from a local media/.txt file.
zarazhangrui/personalized-podcast
Generate a podcast episode from content you provide. An agent skill from zarazhangrui/personalized-podcast.
Agents365-ai/video-podcast-maker
Smallest personal narrated-explainer-video pipeline (spoken narration over visuals, not an audio podcast), fully tool-agnostic and autonomous by default — topic → research ∥ asset collection →…
microsoft/skills
Builds podcast-style audio narration from text with Azure OpenAI's GPT Realtime Mini over WebSocket, from a Python FastAPI backend to a React player.
xiaoleiy/podpull
A skill your agent uses when the user wants to download a podcast episode's audio file (mp3/m4a) to disk — from an Apple Podcasts show or episode link, a raw RSS feed, or a 小宇宙/xiaoyuzhou episode…
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.
Categories
When the user wants to do developer advocacy activities including conference talks, live coding, podcasts, and building in public. Developer Advocacy is an agent skill from sickn33/agentic-awesome-skills. When the user wants to do developer advocacy activities including conference talks, live coding, podcasts, and building in public.
Developer Advocacy fits situations like: wants to do developer advocacy activities including conference talks; building in public.
Run `npx skills add sickn33/agentic-awesome-skills --skill developer-advocacy -a claude-code`. Or copy the skill folder (skills/developer-advocacy in sickn33/agentic-awesome-skills) into .claude/skills/developer-advocacy in your project. Claude Code loads it when a task matches its description.
Run `npx skills add sickn33/agentic-awesome-skills --skill developer-advocacy -a codex`. Or copy the skill folder (skills/developer-advocacy in sickn33/agentic-awesome-skills) into .agents/skills/developer-advocacy 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 developer-advocacy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/developer-advocacy, .gemini/skills/developer-advocacy, .github/skills/developer-advocacy and .opencode/skills/developer-advocacy in your project.
Going by SKILL.md and its folder, Developer Advocacy needs the command-line tools its instructions call (git).
SKILL.md names 1 domain. 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.
Developer Advocacy 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.3k 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 Developer Advocacy: Bibi (JimmyLv/BibiGPT-v1, 6.2k stars), Video Transcribe (wendy7756/AI-Video-Transcriber, 3.3k stars), Podcast (zarazhangrui/personalized-podcast, 437 stars) and Video Podcast Maker Nano (Agents365-ai/video-podcast-maker, 1.7k 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,379 GitHub stars. The repository holds 1,493 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.