Blog Outline
AgriciDaniel/claude-blog
SERP-informed outline generation with H2/H3 heading hierarchy, competitive content gap analysis, section-by-section word count targets, chart and image placement markers, optional FAQ question…
How to author a content brief that actually guides a writer (human or AI) to produce a piece that ranks, converts, or both.
$ npx skills add rampstackco/claude-skills --skill content-brief-authoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rampstackco/claude-skills content-brief-authoring --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/rampstackco/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/content-brief-authoring .claude/skills/content-brief-authoring && 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-brief-authoring" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/content-brief-authoring into .claude/skills/content-brief-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-brief-authoring", 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/rampstackco/claude-skills/tree/main/skills/content-brief-authoringType 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 rampstackco/claude-skills --skill content-brief-authoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rampstackco/claude-skills content-brief-authoring --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/content-brief-authoring .agents/skills/content-brief-authoring && 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-brief-authoring" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/content-brief-authoring into .agents/skills/content-brief-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-brief-authoring", 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 rampstackco/claude-skills --skill content-brief-authoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rampstackco/claude-skills content-brief-authoring --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/content-brief-authoring .cursor/skills/content-brief-authoring && 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-brief-authoring" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/content-brief-authoring into .cursor/skills/content-brief-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-brief-authoring", 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/rampstackco/claude-skills.git --path skills/content-brief-authoring--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 rampstackco/claude-skills --skill content-brief-authoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rampstackco/claude-skills content-brief-authoring --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/content-brief-authoring .gemini/skills/content-brief-authoring && 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-brief-authoring" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/content-brief-authoring into .gemini/skills/content-brief-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-brief-authoring", 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 rampstackco/claude-skills content-brief-authoringInstalls 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 rampstackco/claude-skills --skill content-brief-authoring -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/content-brief-authoring .github/skills/content-brief-authoring && 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-brief-authoring" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/content-brief-authoring into .github/skills/content-brief-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-brief-authoring", 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 rampstackco/claude-skills --skill content-brief-authoring -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rampstackco/claude-skills content-brief-authoring --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/content-brief-authoring .opencode/skills/content-brief-authoring && 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-brief-authoring" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/content-brief-authoring into .opencode/skills/content-brief-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-brief-authoring", 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.
content-brief-authoringHow to author a content brief that actually guides a writer (human or AI) to produce a piece that ranks, converts, or both.
Content Brief Authoring is an agent skill from rampstackco/claude-skills. How to author a content brief that actually guides a writer (human or AI) to produce a piece that ranks, converts, or both. Per-piece editorial brief: target keyword and cluster, search intent, audience and JTBD, heading structure, entity coverage for AEO/GEO, internal linking strategy, success criteria. The middle path between thin briefs (a keyword and a deadline) and thick briefs (a 4-page document nobody reads). Triggers on content brief, brief the writer, brief the article, brief authoring, content brief…
Its SKILL.md is about 5.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `README.md`, `references/brief-governance-patterns.md` and `references/brief-templates.md`).
It sits in Marketing & SEO, covering Content strategy, On-page SEO and AI search optimization. The repository describes itself as: Stack-agnostic Claude Skills covering the full website lifecycle: brand, design, content, SEO, dev, ops, growth, and research. Build, ship, audit, optimize. The licence is MIT.
12 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 482c9bf. 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.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From 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.
Content Brief Authoring loads about 5.6k tokens when it runs, and up to ~18k if it reads all its reference files. Until then it costs about 181 tokens; SKILL.md has 3,114 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 rampstackco/claude-skills at commit 482c9bf, republished under its MIT licence (© rampstackco). 3,114 words, ~5,633 tokens.
.claude/skills/content-brief-authoring/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.A senior content strategist's playbook for authoring per-piece content briefs that actually guide writers to produce content worth publishing.
Most content briefs are some flavor of broken. The thin version is a keyword, a word count, and a deadline; the writer fills in everything else from scratch and the output is generic. The thick version is a 4-page document nobody reads, that the writer skims for the headline and the outline and ignores the rest. Either way, the brief failed at its job: making the writer's work easier and the output more predictable.
This skill is the middle path. It defines the 12 fields that earn their keep in a content brief, the fields that bloat without helping, and the discipline of writing briefs that route a writer (human or AI) toward a content piece that ranks for its target keyword, gets cited by AI engines, converts the right reader, or whatever the success criteria say. It assumes you have decided what to write (see content-strategy for program-level decisions) and now you are briefing each piece. The piece itself gets written separately (see content-and-copy).
When to use this skill: briefing a writer (human or AI) on an individual content piece, auditing existing briefs that are not producing good content, building a brief template for a content program, or running a brief-generation pipeline through Frase, AirOps, or another tool.
This skill spans the per-piece editorial brief discipline. It composes with three sister skills, and the distinction between them is what keeps each one sharp.
creative-brief is a project brief. It bridges discovery to execution at the project level: a new website, app, brand, or campaign. Audience, goals, scope, success at project scope.content-strategy is a program-level editorial strategy. Pillars, calendar, topic clusters, governance. What to produce across a quarter or a year.content-and-copy is the writing itself. Voice, structure, edit pass, tone calibration. Execution scope for general editorial.content-strategy (program decided) and content-and-copy (piece gets written). It briefs a single content artifact: keyword, intent, audience, outline, entities, success criteria.The clean reading order: content-strategy decides what to produce; this skill briefs each piece; content-and-copy writes it. If the team is briefing a redesign or a new brand build, that is creative-brief, not this skill.
The audience: content strategists, SEO content marketers, editorial leads, content ops managers, agencies running content programs at scale, and any PM or marketer briefing a writer (human or AI). The voice is senior content strategist to junior content marketer. Specific, opinionated, honest about what makes a brief useful versus useless.
The keystone distinction. Three concrete shapes.
Thin brief. Keyword, word count target, deadline. Maybe a one-line summary of the angle. The writer fills in everything else from scratch. Output is generic, drifts off-topic, does not rank, and does not convert. The cost is the rewrite cycle: editor spends two hours rewriting because the writer chose the wrong intent, the wrong audience, or the wrong outline.
Thick brief. A 4-page document with executive summary, brand-guidelines refresher, comprehensive competitive analysis, voice guidelines, plus the actual brief somewhere in the middle. The writer skims for the outline, ignores the rest. Output is not materially better than from a thin brief because the writer never read most of the document. The cost is the authoring time: the strategist spends three hours producing pages of context the writer will never absorb.
Effective brief. One to two pages. Every field earns its keep. Writer reads all of it because there is no fluff. Output is predictable enough that the editor does not have to rewrite the lede. The cost is the discipline of cutting fields that do not change writer behavior.
The discipline. Every field in the brief has a job. If you can remove the field without degrading the output, remove it. The brief is the contract between editorial leader and writer; vague contracts produce vague output, overstuffed contracts produce output that reflects only the parts the writer read.
Most briefs that are not working are thin, not thick. The instinct to add more usually makes the brief worse. The instinct to be more specific in fewer fields usually makes the brief better.
A useful brief has 12 fields. Skip any of them and the writer fills the gap from priors; the gap is where output drifts.
The fields that do not earn their keep, and should be omitted from briefs unless the writer is brand new to the program:
Detail and templates per content type in references/brief-templates.md.
The four standard intents:
The dominant SERP format check. After classifying intent, scan the SERP top 10 and tag the dominant format: article, listicle, comparison, video, tool, hybrid. The dominant format tells you the shape of the piece, which is more decisive than the intent label.
The override pattern. When the intent feels informational but the SERP shows mostly listicles, write the listicle. When the intent feels commercial but the SERP shows mostly long-form articles, write the article. The SERP is the source of truth, not your priors. Rankings come from matching the SERP's accepted shape; deviating costs ranking.
The AEO/GEO consideration. AI engines tend to favor pieces that match SERP intent format because the intent classification was trained on the SERP corpus. Mismatched format is a citation risk in addition to a ranking risk.
Detail in references/search-intent-classification.md.
Heading hierarchy patterns the brief should specify:
Anti-patterns the brief should explicitly forbid:
Detail in references/heading-structure-patterns.md.
AI engines (ChatGPT, Perplexity, Claude, Gemini, Google AI Mode) tend to cite content that mentions the entities the SERP top-ranking pages mention, includes specific statistics with sources, contains citation-formatted proof points, and demonstrates topical depth via entity coverage.
The entity discovery pattern, run before briefing the piece:
The brief lists the entities the writer must mention, with light context on why each matters. The writer is not expected to research each entity from scratch; the brief includes a one-line note ("CUPED is the variance-reduction technique used by data-warehouse-experimentation teams; mention in the methodology section") so the writer can integrate without breaking flow.
Tools that automate this: Frase has entity-gap analysis built in; AirOps composes the same analysis through its workflow builder; Surfer SEO ships entity coverage scoring. The skill is tool-agnostic; the workflow is what matters.
Detail in references/entity-coverage-checklist.md.
The brief should specify two link directions:
The orphan-content failure mode: piece publishes, no other piece links to it, search engines deprioritize it, AI engines do not see it as cluster-anchored. Prevented by upstream-link planning in the brief.
The self-cannibalization check: if this piece would compete with an existing piece for the same keyword cluster, the brief flags it explicitly. The options are consolidate (merge into the existing piece), differentiate (the brief sharpens the angle so the two do not compete), or kill one. Flagging late, after the piece is written, costs more than flagging in the brief.
Detail in references/internal-linking-strategy.md.
Different content types call for different brief shapes. The 12 fields are constant; the weight of each field shifts.
Each template gets a worked example in references/brief-templates.md.
Whether the writer is human or AI, the handoff has the same shape.
For AI handoff specifically, the brief becomes a structured prompt or a tool input. Frase, AirOps, and similar tools structure briefs as YAML or JSON for machine consumption; the same 12 fields apply. The structured format is the only difference; the contract is the same.
Detail in references/writer-handoff-protocols.md.
Versioning. Every brief has a version. Significant changes (target keyword change, audience shift, scope expansion) bump the version; cosmetic edits do not. The writer always works from the current version, not a stale draft pasted into Slack three weeks ago.
Approval. The brief approver is the editorial owner of the content program. Single approver, not a committee. The approver is also the editor on the back end, so the same person is responsible for both the contract and the review. Splitting these roles is how briefs and reviews drift apart.
Archival. After publish, the brief is archived alongside the content piece (Notion database row, dbt model, content management system metadata, whatever the team's source of truth is). Future content audits reference both brief and published piece to assess gap between intent and execution. Without the brief in the archive, a content audit cannot tell whether the piece succeeded against the original goal or drifted from it.
Detail in references/brief-governance-patterns.md.
Rapid-fire. Diagnoses and fixes in references/common-brief-failures.md.
When authoring or auditing a content brief, walk these 12 considerations.
The output of the framework is a brief document the writer can absorb in 5 minutes and execute against in the next 5 hours.
This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.
references/brief-templates.md - Pillar, supporting, comparison, listicle, how-to, and thought-leadership brief templates with field-weight notes per type.references/search-intent-classification.md - Four-intent framework, SERP format check, override patterns.references/heading-structure-patterns.md - H2 and H3 patterns, featured snippet bait, anti-patterns.references/entity-coverage-checklist.md - Entity discovery from SERP, gap analysis, AEO/GEO citation drivers.references/internal-linking-strategy.md - Outbound and inbound linking patterns, orphan prevention, self-cannibalization check.references/writer-handoff-protocols.md - Human-writer handoff, AI-agent handoff, success-criteria anchoring.references/brief-governance-patterns.md - Versioning, approval, archival, audit trail.references/common-brief-failures.md - Ten-plus failure patterns with diagnoses and fixes.A content brief is the contract between editorial leader and writer. If the contract is vague, the output is vague. If the contract is overstuffed, the output reflects only the parts the writer read. The discipline is writing contracts the writer can absorb in 5 minutes and execute against in the next 5 hours; that is the entire job.
Most briefs that are not working are thin, not thick. The instinct to add more pages usually makes the brief worse. The instinct to be more specific in fewer fields usually makes the brief better.
When in doubt about whether a brief is ready, ask: are all 12 fields populated, do they each earn their keep, is the SERP intent matched, are the entities listed, are the internal links specified, is the success criteria measurable, and is the document under 2 pages? If yes to all of those, ship the brief and let the writer work.
© rampstackco, 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 9 other files (references) in skills/content-brief-authoring of rampstackco/claude-skills.
Open the folder on GitHubat commit 482c9bf
Content Brief Authoring 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 Brief Authoring this skillrampstackco/claude-skills | 935 | — | ~5.6k | Automated safety check: Pass | MIT | |
| Blog OutlineAgriciDaniel/claude-blog | 2.3k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| SEO Keyword ClusteringAgriciDaniel/claude-seo | 18k | 2 repos | ~3.3k | Automated safety check: Pass | MIT | |
| SEO Content Brief GeneratorAgriciDaniel/claude-seo | 18k | 2 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Keyword Researchnowork-studio/notfair-plugin | 3.9k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| SEO Keyword Clusterseranking/seo-skills | 160 | — | ~2.5k | Automated safety check: Pass | MIT |
AgriciDaniel/claude-blog
SERP-informed outline generation with H2/H3 heading hierarchy, competitive content gap analysis, section-by-section word count targets, chart and image placement markers, optional FAQ question…
AgriciDaniel/claude-seo
Clusters keywords by how much their search results overlap and designs a hub-and-spoke content plan with an internal link matrix and an interactive cluster map.
AgriciDaniel/claude-seo
Builds research-backed SEO content briefs with competitor scoring, per-section word counts and page-type templates, for new pages or improving existing ones.
nowork-studio/notfair-plugin
Finds, scores and groups keywords from a seed term or niche for SEO and AI search content strategies, with intent labels, difficulty estimates and topic clusters.
seranking/seo-skills
Build a content cluster plan from seed keywords — intent-grouped clusters, pillar+spokes architecture with H1/H2 suggestions per spoke, prioritised build order, and an internal-linking map.
secondsky/claude-skills
SEO keyword clustering with topic organization, content hub architecture, internal linking strategies.
rampstackco/claude-skills
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.
rampstackco/claude-skills
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy.
rampstackco/claude-skills
Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts.
rampstackco/claude-skills
Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples.
rampstackco/claude-skills
Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal.
rampstackco/claude-skills
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning.
Categories
How to author a content brief that actually guides a writer (human or AI) to produce a piece that ranks, converts, or both. Content Brief Authoring is an agent skill from rampstackco/claude-skills. How to author a content brief that actually guides a writer (human or AI) to produce a piece that ranks, converts, or both.
Content Brief Authoring fits situations like: brief the writer; brief the article; brief authoring; content brief template.
Run `npx skills add rampstackco/claude-skills --skill content-brief-authoring -a claude-code`. Or copy the skill folder (skills/content-brief-authoring in rampstackco/claude-skills) into .claude/skills/content-brief-authoring in your project. Claude Code loads it when a task matches its description.
Run `npx skills add rampstackco/claude-skills --skill content-brief-authoring -a codex`. Or copy the skill folder (skills/content-brief-authoring in rampstackco/claude-skills) into .agents/skills/content-brief-authoring 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 rampstackco/claude-skills --skill content-brief-authoring -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-brief-authoring, .gemini/skills/content-brief-authoring, .github/skills/content-brief-authoring and .opencode/skills/content-brief-authoring in your project.
SKILL.md names no scripts, command-line tools or credentials: Content Brief Authoring is instructions for the agent only.
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.
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.
Content Brief Authoring is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.6k tokens (SKILL.md is roughly 23k 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 12k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Content Brief Authoring: Blog Outline (AgriciDaniel/claude-blog, 2.3k stars), SEO Keyword Clustering (AgriciDaniel/claude-seo, 18k stars), SEO Content Brief Generator (AgriciDaniel/claude-seo, 18k stars) and Keyword Research (nowork-studio/notfair-plugin, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
rampstackco (a GitHub organization) maintains it in rampstackco/claude-skills, which has 935 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 7, 2026.
Source: rampstackco/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.