Humanizer
Azure-Samples/interview-coach-agent-framework
Remove signs of AI-generated writing from text. An agent skill from Azure-Samples/interview-coach-agent-framework.
When the user wants to establish or update their developer audience context.
Install Developer Audience Context
$ npx skills add sickn33/agentic-awesome-skills --skill developer-audience-context -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills developer-audience-context --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-audience-context .claude/skills/developer-audience-context && 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-audience-context" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-audience-context into .claude/skills/developer-audience-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-audience-context", 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-audience-contextType 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-audience-context -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills developer-audience-context --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-audience-context .agents/skills/developer-audience-context && 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-audience-context" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-audience-context into .agents/skills/developer-audience-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-audience-context", 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-audience-context -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills developer-audience-context --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-audience-context .cursor/skills/developer-audience-context && 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-audience-context" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-audience-context into .cursor/skills/developer-audience-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-audience-context", 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-audience-context--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-audience-context -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills developer-audience-context --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-audience-context .gemini/skills/developer-audience-context && 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-audience-context" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-audience-context into .gemini/skills/developer-audience-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-audience-context", 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-audience-contextInstalls 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-audience-context -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-audience-context .github/skills/developer-audience-context && 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-audience-context" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-audience-context into .github/skills/developer-audience-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-audience-context", 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-audience-context -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-audience-context --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-audience-context .opencode/skills/developer-audience-context && 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-audience-context" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-audience-context into .opencode/skills/developer-audience-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-audience-context", 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
developer-audience-context- GitHub stars
- 47k
- Used in
- 1 other repo
- Token cost
- ~2.4k tokens
- SKILL.md length
- 984 words
- Files
- 4 (incl. references)
- Skills in repo
- 1,394
- Repo updated
- First seen
- Licence
- MIT
At a glance
When the user wants to establish or update their developer audience context.
- Works in 10 steps: Product Overview → Developer Persona → Where They Hang Out → …
- Wants to establish
- SKILL.md covers When to Use, Before You Start, Two Ways to Build Context and The 10 Sections to Capture, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Developer Audience Context is an agent skill from sickn33/agentic-awesome-skills. When the user wants to establish or update their developer audience context. Also use when starting any other developer marketing skill to ensure foundational context is loaded.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `README.md`, `references/example-apitest.md` and `references/template.md`).
It sits in Writing & Content. 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.
When your agent uses it
- Wants to establish
- Update their developer audience context
- Starting any other developer marketing skill to ensure foundational context is loaded
Example prompts
- “/developer-audience-context”
Requirements
- Docker
Workflow steps
10 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 1e53ce2. 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 (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
octolens.com
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
Developer Audience Context loads about 2.4k tokens when it runs, and up to ~4.8k if it reads all its reference files. Until then it costs about 51 tokens; SKILL.md has 984 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 sickn33/agentic-awesome-skills at commit 1e53ce2, republished under its MIT licence (© sickn33). 984 words, ~2,354 tokens.
Download SKILL.mdSave it as
.claude/skills/developer-audience-context/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- developer-audience-context
- description
- When the user wants to establish or update their developer audience context. Also use when starting any other developer marketing skill to ensure foundational context is loaded.
- risk
- critical
- source
- https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-audience-context
- source_repo
- jonathimer/devmarketing-skills
- source_type
- community
- date_added
- 2026-07-01
- license
- MIT
- license_source
- https://github.com/jonathimer/devmarketing-skills/blob/main/LICENSE
Developer Audience Context
When to Use
Use this skill when you need when the user wants to establish or update their developer audience context. Also use when starting any other developer marketing skill to ensure foundational context is loaded. Trigger phrases include "developer persona," "target developers," "who are our developers," "developer...
This skill helps you create and maintain .agents/developer-audience-context.md — a foundational document that captures everything about your target developers. All other developer marketing skills reference this document first, so you only define your audience once.
Before You Start
Check if .agents/developer-audience-context.md exists:
- If it exists: Read it and offer to update specific sections
- If it doesn't exist: Create the directory and file, then walk through each section
Two Ways to Build Context
Option 1: Auto-Draft from Codebase (Recommended)
Analyze existing materials to draft an initial version:
- README.md — Product description, features, getting started
- Documentation —
/docs, API reference, tutorials - Landing pages —
index.html, marketing copy - package.json / pyproject.toml — Dependencies reveal ecosystem
- GitHub Issues — Common questions, frustrations, use cases
- Existing blog posts — Technical content, tutorials
After drafting, walk through each section to validate and fill gaps.
Option 2: Start from Scratch
Ask questions section-by-section. Don't advance until the current section is complete.
The 10 Sections to Capture
1. Product Overview
| Field | What to capture |
|---|---|
| Product name | Official name and any aliases |
| One-liner | "We help [developers] do [X] without [Y]" |
| Category | API, SDK, CLI, SaaS, open source library, infrastructure |
| Core technology | Languages, frameworks, platforms supported |
| Pricing model | Free/open source, freemium, usage-based, seat-based |
2. Developer Persona
Not "developers" generically — get specific:
| Field | What to capture |
|---|---|
| Primary role | Backend, frontend, full-stack, DevOps, data, ML, mobile |
| Seniority | Junior, mid, senior, staff, lead, architect |
| Company size | Solo, startup, scale-up, enterprise |
| Industry verticals | Fintech, healthtech, e-commerce, gaming, B2B SaaS |
| Tech stack | Languages, frameworks, cloud providers they use |
| Decision authority | Individual contributor, team lead, buyer, influencer |
Ask: "Describe the developer who gets the most value from your product in one paragraph. What's their day-to-day like?"
3. Where They Hang Out
Developers research before they buy. Know where:
| Channel | Specifics to capture |
|---|---|
| Communities | Specific subreddits, Discord servers, Slack groups |
| Social | Twitter/X hashtags, LinkedIn groups |
| Content | Blogs they read, newsletters they subscribe to, podcasts |
| Events | Conferences, meetups, hackathons |
| Code | GitHub topics, Stack Overflow tags |
Pro tip: Use social listening tools to monitor conversations across Hacker News, Reddit, Stack Overflow, GitHub, and Twitter. See where discussions about your problem space happen organically.
4. Problems & Pain Points
Capture the actual problems, not your solution's features:
| Level | What to capture |
|---|---|
| Functional | "I can't do X" / "X takes too long" / "X is error-prone" |
| Emotional | Frustration, anxiety, embarrassment, fear |
| Situational | When does the pain occur? What triggers the search? |
Ask: "What's the #1 frustration that brings developers to you?"
Research: Search Reddit, Hacker News, and Stack Overflow for complaints about your problem space. Capture verbatim quotes.
5. Current Alternatives
What are developers using today instead of you?
| Alternative type | Examples |
|---|---|
| Direct competitors | Tools that solve the same problem |
| DIY / build it yourself | Custom scripts, internal tools |
| Indirect solutions | Workarounds, manual processes |
| Do nothing | Live with the pain |
For each alternative, capture:
- Why developers choose it
- What's frustrating about it
- What would make them switch
6. Key Differentiators
What makes you different — in developer terms:
| Differentiator type | Example |
|---|---|
| Technical | "10x faster," "No dependencies," "Type-safe" |
| DX (Developer Experience) | "5-minute setup," "Great docs," "First-class CLI" |
| Ecosystem | "Works with X," "Built for Y framework" |
| Philosophy | "Open source," "Privacy-first," "Local-first" |
Warning: Avoid marketing fluff. Developers see through "best-in-class" and "enterprise-grade." Use specific, provable claims.
Show full SKILL.md (398 more words)Show less
7. Verbatim Developer Language
Capture exact phrases developers use — not polished marketing copy:
| Category | Examples |
|---|---|
| Describing the problem | "This is such a pain," "I wish I could just..." |
| Describing your product | How they explain it to others |
| Objections | "But what about...", "I'm worried that..." |
| Praise | Testimonials, tweets, GitHub comments |
Sources: GitHub issues, Twitter mentions, Hacker News comments, support tickets, sales calls, community Slack/Discord.
8. Technical Trust Signals
What proof points matter to developers:
| Signal type | Examples |
|---|---|
| Adoption | GitHub stars, npm downloads, Docker pulls |
| Quality | Test coverage, security audits, uptime SLA |
| Community | Contributors, Discord members, forum activity |
| Credibility | Backed by X, used by Y, created by Z |
| Transparency | Open source, public roadmap, changelog |
9. Conversion Actions
What does success look like at each stage?
| Stage | Primary action | Secondary actions |
|---|---|---|
| Awareness | Star repo, follow on Twitter | Read blog post, share content |
| Consideration | Clone repo, read docs | Watch demo, join Discord |
| Trial | Sign up, install SDK | Complete quickstart, make first API call |
| Activation | Reach "Hello World" moment | Integrate into real project |
| Conversion | Upgrade to paid | Add team members, expand usage |
10. Voice & Tone
How should you sound when talking to these developers?
| Dimension | Spectrum |
|---|---|
| Formality | Casual ← → Professional |
| Technicality | Accessible ← → Deep technical |
| Personality | Neutral ← → Opinionated |
| Humor | Serious ← → Playful |
Examples:
- Stripe → Professional, precise, clean
- Vercel → Modern, confident, developer-first
- Supabase → Friendly, accessible, community-driven
- Tailwind → Opinionated, direct, practical
Output Format
Save to .agents/developer-audience-context.md with this structure:
# Developer Audience Context
Last updated: [DATE]
## Product Overview
[Section content]
## Developer Persona
[Section content]
## Where They Hang Out
[Section content]
## Problems & Pain Points
[Section content]
## Current Alternatives
[Section content]
## Key Differentiators
[Section content]
## Verbatim Developer Language
[Section content]
## Technical Trust Signals
[Section content]
## Conversion Actions
[Section content]
## Voice & Tone
[Section content]Maintenance
Update this document when:
- You learn something new from user research
- You find great verbatim quotes
- Your positioning or differentiation changes
- You expand to new developer segments
Tools
| Tool | Use case |
|---|---|
| Octolens | Monitor developer conversations across GitHub, Hacker News, Reddit, Stack Overflow, Twitter. Essential for capturing verbatim language, finding pain points, and understanding where your developers hang out. |
| GitHub Search | Find how developers describe problems in issues |
| Twitter Advanced Search | Find discussions about your space |
| Google Alerts | Track mentions of competitors and problem keywords |
Related Skills
After establishing context, these skills will reference it:
devrel-content— Writing content that resonateshacker-news-strategy— Engaging on HN authenticallydeveloper-onboarding— Optimizing time-to-valuedeveloper-seo— Targeting the right technical queriescompetitor-tracking— Understanding your competitive landscape
Limitations
- Use this skill only when the task clearly matches its upstream source and local project context.
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
© sickn33, 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 3 other files (references) in skills/developer-audience-context of sickn33/agentic-awesome-skills.
- SKILL.md
- README.md
- references/example-apitest.md
- references/template.md
Open the folder on GitHubat commit 1e53ce2
Used in 1 other repository
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.
Compare with similar skills
Developer Audience Context 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 Audience Context this skillsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| HumanizerAzure-Samples/interview-coach-agent-framework | 172 | 37 repos | ~5.8k | Automated safety check: Pass | MIT | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| JavaScript Concept Fact Checkerleonardomso/33-js-concepts | 67k | 1 repos | ~5k | Automated safety check: Pass | MIT | |
| User-Facing Text Cleanupguillaumemeyer/watermarks-remover | 23k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Install Anti Sloptrycompai/crm | 11k | 1 repos | ~881 | Automated safety check: Pass | MIT |
Similar skills
- Official
Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
JavaScript Concept Fact Checker
leonardomso/33-js-concepts
Verifies the technical accuracy of JavaScript concept pages by checking code examples, MDN and ECMAScript claims and external links through a five-phase method.
User-Facing Text Cleanup
guillaumemeyer/watermarks-remover
Audits prose for invisible Unicode characters and rewrites it while keeping facts, citations, code and required disclosures unchanged and the writer's voice intact.
Install Anti Slop
trycompai/crm
Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository.
Social Content
freekmurze/dotfiles
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms.
More from sickn33/agentic-awesome-skills
All 1,394 skills in this repoLiuguang Banlan UI
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.
User Thoughts Memory
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.
Using LWC Memory and Graphs
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.
Find Complementary Founders
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.
Whatsapp Cloud API
sickn33/agentic-awesome-skills
Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.
Cline Pilot
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.
Related
Categories
Questions about Developer Audience Context
What does Developer Audience Context do?
When the user wants to establish or update their developer audience context. Developer Audience Context is an agent skill from sickn33/agentic-awesome-skills. When the user wants to establish or update their developer audience context.
When should I use Developer Audience Context?
Developer Audience Context fits situations like: wants to establish; update their developer audience context; starting any other developer marketing skill to ensure foundational context is loaded.
How do I install Developer Audience Context in Claude Code?
Run `npx skills add sickn33/agentic-awesome-skills --skill developer-audience-context -a claude-code`. Or copy the skill folder (skills/developer-audience-context in sickn33/agentic-awesome-skills) into .claude/skills/developer-audience-context in your project. Claude Code loads it when a task matches its description.
How do I install Developer Audience Context in Codex?
Run `npx skills add sickn33/agentic-awesome-skills --skill developer-audience-context -a codex`. Or copy the skill folder (skills/developer-audience-context in sickn33/agentic-awesome-skills) into .agents/skills/developer-audience-context in your project. Codex loads it when a task matches its description.
Can I use Developer Audience Context 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 sickn33/agentic-awesome-skills --skill developer-audience-context -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-audience-context, .gemini/skills/developer-audience-context, .github/skills/developer-audience-context and .opencode/skills/developer-audience-context in your project.
What does Developer Audience Context need to run?
SKILL.md names no scripts, command-line tools or credentials: Developer Audience Context is instructions for the agent only. Our summary lists: Docker.
Does Developer Audience Context access the network?
SKILL.md names 1 domain. As links in the text: octolens.com. This is read from the text; nothing was executed.
Is Developer Audience Context 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 Developer Audience Context use?
Developer Audience Context is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Developer Audience Context use?
About 2.4k tokens (SKILL.md is roughly 9.4k 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.5k tokens, read only when the agent opens those files.
What are the alternatives to Developer Audience Context?
Skills that share tags, products or a category with Developer Audience Context: Humanizer (Azure-Samples/interview-coach-agent-framework, 172 stars), Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), JavaScript Concept Fact Checker (leonardomso/33-js-concepts, 67k stars) and User-Facing Text Cleanup (guillaumemeyer/watermarks-remover, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Developer Audience Context?
sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,304 GitHub stars. The repository holds 1,394 skills in this directory. The repository was last updated on October 6, 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.