Lead Magnet Generator
ognjengt/founder-skills
Creates viral lead magnet posts that drive comments and DMs.
Content distribution as a discipline. An agent skill from rampstackco/claude-skills.
$ npx skills add rampstackco/claude-skills --skill content-distribution -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rampstackco/claude-skills content-distribution --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-distribution .claude/skills/content-distribution && 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-distribution" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/content-distribution into .claude/skills/content-distribution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-distribution", 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-distributionType 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-distribution -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rampstackco/claude-skills content-distribution --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-distribution .agents/skills/content-distribution && 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-distribution" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/content-distribution into .agents/skills/content-distribution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-distribution", 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-distribution -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rampstackco/claude-skills content-distribution --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-distribution .cursor/skills/content-distribution && 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-distribution" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/content-distribution into .cursor/skills/content-distribution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-distribution", 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-distribution--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-distribution -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rampstackco/claude-skills content-distribution --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-distribution .gemini/skills/content-distribution && 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-distribution" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/content-distribution into .gemini/skills/content-distribution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-distribution", 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-distributionInstalls 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-distribution -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-distribution .github/skills/content-distribution && 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-distribution" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/content-distribution into .github/skills/content-distribution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-distribution", 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-distribution -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-distribution --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-distribution .opencode/skills/content-distribution && 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-distribution" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/content-distribution into .opencode/skills/content-distribution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-distribution", 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-distributionContent distribution as a discipline. An agent skill from rampstackco/claude-skills.
Content Distribution is an agent skill from rampstackco/claude-skills. Content distribution as a discipline. Owned channels (newsletter, blog, social), earned channels (PR, syndication, mentions), paid channels (boosted posts, syndication networks), and the channel-fit decisions that distinguish strategic distribution from spam-everywhere. Audience-channel matching, content-channel matching, distribution cadence. Triggers on content distribution, channel strategy for content, owned earned paid channels, content amplification, content promotion, audience-channel matching…
Its SKILL.md is about 6.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `README.md`, `references/audience-channel-matching.md` and `references/channel-taxonomy.md`).
It sits in Marketing & SEO, covering Content marketing. 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 Distribution loads about 6.5k tokens when it runs, and up to ~32k if it reads all its reference files. Until then it costs about 208 tokens; SKILL.md has 3,072 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,072 words, ~6,491 tokens.
.claude/skills/content-distribution/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.A senior editorial leader's playbook for content distribution as a discipline. Owned, earned, and paid channels matched to audience and content type, with the channel-fit decisions that distinguish strategic distribution from spam-everywhere or hope-and-pray.
Content distribution is half the work and gets a fraction of the attention. Most programs spend 90% of capacity on production and 10% on distribution; the resulting ratio of effort-to-reach is consistently poor. The teams producing content that reaches audiences are the ones who treat distribution as a real discipline: channels chosen for fit, cadence calibrated to audience attention, owned-earned-paid balance set by program strategy, and effectiveness measured per channel.
This skill is the channel discipline. Different from content-repurposing (which turns one piece into many formats), this skill is about getting content TO audiences via the right channels. The two skills compose: repurpose first, then distribute the right format on the right channel.
The voice is the senior editorial leader who has watched programs underperform because distribution was treated as posting-after-publishing rather than as the equal half of the work.
When to use this skill: building a distribution discipline for a content program, auditing why content publishes consistently but reach is low, calibrating owned-earned-paid balance, designing channel-fit decisions for a multi-format program.
This skill spans channel selection, audience-channel matching, content-channel matching, and distribution cadence. The content suite distinction:
content-strategy decides what to produce.pillar-content-architecture designs the topical hub.content-brief-authoring briefs each piece.content-and-copy writes pieces.editorial-qa verifies before publish.content-repurposing turns one piece into many formats (transformation).content-distribution (this skill) gets content TO audiences via channels (channel work).The distinction from content-repurposing is load-bearing. Repurposing is transformation work: turning one piece INTO many formats, each adapted for its medium. Distribution is channel work: getting content to audiences via the right channels. They compose: repurpose first, then distribute the right format on the right channel.
The audience: editorial leads, content directors, content ops managers, in-house teams running content programs that need reach, agencies running distribution for clients.
What is not in scope: paid acquisition for purposes other than content amplification (covered by paid-media-strategy), the specific email channel discipline (covered by email-sequences), the AI-search optimization layer that sits across distribution channels (covered partially by seo-aeo-geo).
The keystone framing.
Hope-and-pray. Publish and assume readers will find it. The piece goes live; the team links it on the blog homepage; maybe shares it once on social; assumes search and word of mouth will carry it. Output: most pieces reach a fraction of their potential audience because no deliberate distribution work was done. The program produces good content that nobody encounters.
Spam-everywhere. Blast every piece on every channel regardless of fit. Every piece on LinkedIn, Twitter/X, Facebook, Threads, Mastodon, Bluesky, plus 5 emails to the full list, plus paid promotion on every platform. Audience tunes out; channels deprioritize the program; trust degrades. AI tooling has made spam-everywhere cheap and increasingly common, which makes the audience reaction sharper.
Channel-fit. Distribute through channels matched to audience and content type. Specific channels chosen for specific pieces. Cadence calibrated to each channel's audience attention rhythm. Owned-earned-paid balance set by program strategy. Output: each distribution choice produces engagement from audiences who actually want the content; the program's distribution capacity is concentrated where it produces value.
The litmus test. Ask of any distribution decision: which audience is this piece for, where does that audience consume content, does the piece's format fit that channel's conventions, and at what cadence does the channel reward presence? If the answers are specific, the distribution is channel-fit. If the answers are "everyone, everywhere, every channel, all the time," the distribution is spam-everywhere.
Three categories with sub-types within each.
Owned channels. Channels the program owns and controls.
Earned channels. Channels where content reaches audiences via third-party amplification, not paid placement.
Paid channels. Channels where paid spending amplifies content.
Detail in references/channel-taxonomy.md.
Where the target audience actually consumes content. The distribution decision starts here.
The audit.
Common audience-channel maps.
The mismatch failure. Distributing on channels where the audience is present but not engaged produces low reach and low engagement. A B2B technical program publishing TikToks may technically reach audiences on TikTok but engage few of them; the audience is on TikTok for entertainment, not for technical learning.
Detail in references/audience-channel-matching.md.
Which formats fit which channels. Beyond audience match, the format must fit the channel's conventions.
Format-channel fit examples.
The mismatch failure. Distributing a format on a channel where the format does not fit produces low engagement. A 5,000-word whitepaper on TikTok (even repurposed) may not fit the format expectations of TikTok audiences regardless of audience overlap.
The compose-with-repurposing pattern. When the audience is on a channel but the format does not fit, the right answer is often to repurpose into a format that does fit (see content-repurposing), then distribute. The composition is "repurpose for fit, distribute on channel."
Detail in references/content-channel-matching.md.
How often, what mix, sustaining vs campaign rhythm.
Cadence axes.
Common cadence patterns.
Sustaining vs campaign.
The cadence audit. Programs that publish in fits and starts (3 posts in one week, then nothing for 3 weeks) underperform programs with steady cadence. Audience attention rewards predictability.
Detail in references/distribution-cadence-patterns.md.
Owned channels are the program's most reliable distribution. The discipline keeps them effective.
Newsletter. Direct subscriber relationship; near-100% delivery to inboxes (modulo spam filtering). Cadence consistency matters: weekly is the most common cadence for B2B; bi-weekly works for higher-investment formats. Each send earns the next; sloppy sends lose subscribers.
Blog. Canonical home for long-form content. SEO compounds over time; internal linking earns authority. The blog is where pieces persist; social and email send audiences to the blog.
Social channels owned by the program. LinkedIn, X, Instagram, etc. Reach is platform-controlled (not the program's), but the program controls what publishes and when. Algorithmic favor varies; content that the platform's algorithm rewards gets reach beyond the follower base.
Podcast. Owned distribution is the show feed; subscribers receive new episodes. Episodes also live on the blog with show notes; the show notes are an SEO asset.
Communities. Slack, Discord, forums where the program facilitates discussion. The community is the audience the program is most directly engaged with; distribution to the community is the most reliable engagement signal.
The owned-channel anti-pattern: starvation. Programs that under-invest in owned channels become dependent on third-party distribution. When platforms change algorithms, when paid costs rise, when earned channels go quiet, the program's reach collapses. Owned-channel investment is the durable foundation.
Detail in references/owned-channel-discipline.md.
Earned channels reach audiences the program cannot reach directly. The work to earn the channel is real.
PR and press. Pitching journalists, podcasters, newsletter operators on the program's content. Effective when the content is genuinely newsworthy or insightful; ineffective when pitches feel like blast emails.
Syndication. Negotiating with other publications to republish or excerpt the program's content with appropriate attribution and canonical signaling. The syndication earns reach; the canonical link preserves SEO value.
Mentions and citations. Earning mentions in other programs' content. Often happens when the program's pieces are genuinely useful as references; pieces that are generic or surface-level rarely get cited.
AI search citation. Earning citations from AI search engines. Increasingly important as AI search grows; pieces designed for citation (see content-repurposing's AEO extraction patterns) get cited at higher rates.
Word of mouth and shares. Audiences sharing pieces with their networks. The hardest to earn deliberately; pieces that are genuinely valuable get shared.
The earned-channel investment. Earned channels require relationship-building, pitch quality, and content quality. Programs that try to "do PR" with mass-blast pitches earn nothing; programs that invest in genuine relationships earn ongoing channel access.
Detail in references/earned-channel-work.md.
When boosting organic content earns its keep.
The pattern. A piece publishes organically; some pieces show strong engagement signals; the program boosts those pieces with paid spend to extend reach. The paid spend is on content that the audience has already validated.
When boosting fits.
When boosting fails.
The mix. Most strong programs allocate 0-20% of distribution capacity to paid content amplification. Programs heavily dependent on paid promotion are usually programs that have not yet built owned and earned distribution.
Detail in references/paid-promotion-patterns.md.
Which channels actually drive value. The discipline that prevents distribution-theater.
Per-channel metrics.
Channel-level analysis.
Cross-channel attribution. The same audience member encounters the program on multiple channels before converting. Single-touch attribution misrepresents which channels matter; multi-touch attribution is more accurate but harder to implement.
The measurement-honest program. Cuts channels that consistently underperform. Increases investment in channels that consistently produce. Adjusts cadence based on engagement patterns, not on arbitrary publishing schedules.
Detail in references/distribution-measurement.md.
Rapid-fire. Diagnoses in references/common-distribution-failures.md.
When designing or auditing a distribution program, walk these 12 considerations.
The output of the framework is a distribution program where each channel choice is deliberate, each cadence decision matches audience attention, each measurement informs the next decision, and the program's reach grows because the work is concentrated where it produces value.
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/channel-taxonomy.md - Owned, earned, paid with sub-types. Newsletter, blog, social, communities, PR, syndication, mentions, boosted social, syndication networks, sponsored placements.references/audience-channel-matching.md - Where audiences actually engage. Common audience-channel maps. The presence-vs-engagement distinction.references/content-channel-matching.md - Format-channel fit. The compose-with-repurposing pattern. The format-mismatch failure mode.references/distribution-cadence-patterns.md - Frequency, mix, rhythm. Sustaining vs campaign. Common cadence patterns by program type.references/owned-channel-discipline.md - Newsletter, blog, social, podcast, community discipline. The starvation anti-pattern.references/earned-channel-work.md - PR, syndication, mentions, AI-search citation, word of mouth. Relationship investment.references/paid-promotion-patterns.md - Boosting organic content. When paid amplification fits and when it fails. The paid-as-substitute anti-pattern.references/distribution-measurement.md - Per-channel metrics, channel-level analysis, cross-channel attribution, the measurement-honest program.references/common-distribution-failures.md - 11+ failure patterns with diagnoses and fixes.Most content programs are production-heavy and distribution-light. The teams producing flagship pieces typically spend 90% of capacity producing and 10% distributing; the resulting reach matches the inverse ratio. Pieces that took 60 hours to produce reach a fraction of their potential audience because the 6 hours allocated to distribution were not enough to do the channel work.
The discipline is not "distribute more"; it is "distribute deliberately." Channel-fit decisions concentrate distribution work where it produces value. Owned-channel investment builds durable foundations. Earned-channel relationships accumulate over years. Paid promotion amplifies what organic validated. Measurement informs what to keep and what to cut.
When in doubt about whether a distribution program is ready, ask: are channels chosen for fit, is audience-channel matching deliberate, do formats fit channels, is cadence calibrated, is owned-channel investment in place, are earned-channel relationships being built, is paid amplification on organically-validated pieces, is measurement informing the next decisions? If yes to all of those, the program is real. If no to any, the gap is where reach will fall short of what the production work earned.
© 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 10 other files (references) in skills/content-distribution of rampstackco/claude-skills.
Open the folder on GitHubat commit 482c9bf
Content Distribution 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 Distribution this skillrampstackco/claude-skills | 935 | — | ~6.5k | Automated safety check: Pass | MIT | |
| Lead Magnet Generatorognjengt/founder-skills | 406 | — | ~3k | Automated safety check: Pass | MIT | |
| Search Console Content Plannernowork-studio/notfair-plugin | 3.9k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Webnovel Qimao Writelujih/webnovel-writer-opencode | 213 | — | ~421 | Automated safety check: Pass | GPL-3.0 | |
| Content Engineaffaan-m/ECC | 274k | — | ~608 | Automated safety check: Pass | MIT | |
| 39 Content Auditminhnv0807/ai-business-skills | 608 | — | ~1.9k | Automated safety check: Pass | MIT |
ognjengt/founder-skills
Creates viral lead magnet posts that drive comments and DMs.
nowork-studio/notfair-plugin
Turns Google Search Console data into a dated content calendar by finding striking-distance queries and unanswered intent, ready to hand to a writer.
lujih/webnovel-writer-opencode
七猫写作技巧、七猫风章节、七猫留存与签约约束;Use ONLY when writing or revising Qimao chapters.
affaan-m/ECC
X、LinkedIn、TikTok、YouTube、ニュースレター、マルチプラットフォームキャンペーンのプラットフォームネイティブなコンテンツシステムを作成します。ソーシャル投稿、スレッド、スクリプト、コンテンツカレンダー、または1つのソースアセットを複数プラットフォームにきれいに適応したい場合に使用します。
minhnv0807/ai-business-skills
Dung khi cuoi thang can biet bai nao work bai nao khong va TAI SAO — phan loai winner/loser theo phan vi, tim pattern theo pillar, format, hook, gio dang va do dai.
ericrisco/rsc-harness
A skill your agent uses when a content operation needs a SYSTEM: a dated editorial calendar built top-down from pillars, plus the stage gates, briefs, WIP limits and 1:10 atomization plan that move…
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
Content distribution as a discipline. An agent skill from rampstackco/claude-skills. Content Distribution is an agent skill from rampstackco/claude-skills. Content distribution as a discipline.
Content Distribution fits situations like: content distribution; channel strategy for content; owned earned paid channels; content amplification.
Run `npx skills add rampstackco/claude-skills --skill content-distribution -a claude-code`. Or copy the skill folder (skills/content-distribution in rampstackco/claude-skills) into .claude/skills/content-distribution in your project. Claude Code loads it when a task matches its description.
Run `npx skills add rampstackco/claude-skills --skill content-distribution -a codex`. Or copy the skill folder (skills/content-distribution in rampstackco/claude-skills) into .agents/skills/content-distribution 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-distribution -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-distribution, .gemini/skills/content-distribution, .github/skills/content-distribution and .opencode/skills/content-distribution in your project.
SKILL.md names no scripts, command-line tools or credentials: Content Distribution 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 Distribution is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 6.5k tokens (SKILL.md is roughly 26k 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 25k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Content Distribution: Lead Magnet Generator (ognjengt/founder-skills, 406 stars), Search Console Content Planner (nowork-studio/notfair-plugin, 3.9k stars), Webnovel Qimao Write (lujih/webnovel-writer-opencode, 213 stars) and Content Engine (affaan-m/ECC, 274k 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.