content-distribution
Skill0 starsChanged 8 days agoApache-2.0View on GitHub
Plan, create, repurpose, and measure content for Solo Empire across search, social, email, and client-facing channels. Use when turning one idea or delivery insight into an editorial plan, SEO page, post series, newsletter, or distribution experiment.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- hdd105030-hub/HDDtheir own version, first seen Aug 14, 2026
- citriac/claude-skillstheir own version, first seen Mar 31, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- citriac/claude-skills★ 0same name
- hdd105030-hub/HDD★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository27 other files it gives its agents.
- ai-agentsSkill
- ai-agent-workflowsSkill
- ai-native-estimationSkill
- ai-product-deliverySkill
- book-dev-engineering-loopSkill
- business-analysisSkill
- client-discovery-and-proposalsSkill
- data-engineeringSkill
- flow-videoSkill
- game-engineeringSkill
- govern-ai-skillsSkill
- graphic-designSkill
- lead-research-and-crmSkill
- main-only-developmentSkill
- product-managementSkill
- product-ownerSkill
- project-managementSkill
- qa-testingSkill
- security-and-privacySkill
- skill-templateSkill
- solo-empire-operatorSkill
- solution-architectureSkill
- subagent-orchestrationSkill
- system-docpackSkill
- unused-file-cleanupSkill
- ux-reviewSkill
- xr-engineeringSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Start from evidence: repository-owned knowledge, verified delivery results, user-provided material, or clearly attributed sources.
- Distinctive: line 14
Create one strong source asset, then derive variants for the selected channels.
- Distinctive: line 17
Run a pre-publication review for factual accuracy, permissions, privacy, client confidentiality, legal or regulated claims, brand voice, …
- Distinctive: line 18
Keep drafts separate from approved, scheduled, and published content.
- Distinctive: line 23
No proof for a result → make the claim narrower or label it as a hypothesis.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Content Distribution
Turn useful expertise into channel-appropriate content that earns attention and produces a measurable next step.
Distribution workflow
- Define the audience, problem, offer, desired action, voice, proof available, channel, and publication status.
- Start from evidence: repository-owned knowledge, verified delivery results, user-provided material, or clearly attributed sources. Separate facts, opinions, hypotheses, and examples.
- Create one strong source asset, then derive variants for the selected channels. Preserve the central claim while adapting length, format, tone, call to action, and accessibility.
- For search content, match search intent, use a clear heading structure, write useful metadata, add relevant internal links, and avoid keyword stuffing or fabricated expertise.
- For social or email, lead with the reader's problem, give one concrete insight, use a specific low-friction call to action, and make the next step easy to track.
- Run a pre-publication review for factual accuracy, permissions, privacy, client confidentiality, legal or regulated claims, brand voice, links, accessibility, and formatting.
- Keep drafts separate from approved, scheduled, and published content. Publish or send only with explicit authorization and the correct account or workspace.
- Measure impressions, reach, click-through, saves, replies, qualified leads, conversion, and revenue. Record the hypothesis and use results to choose the next experiment.
Decision rules
- No proof for a result → make the claim narrower or label it as a hypothesis.
- Client or personal information → anonymize, obtain permission, or omit it.
- One asset across many channels → preserve the idea, not the exact wording.
- External source → attribute it and verify the link and date before publishing.
- Unclear audience or CTA → resolve that before producing volume.
- External publication or message → leave it in draft until approved; never report it as sent or published without evidence.
Handoff
Deliver the source asset, channel variants, approval checklist, scheduling state, source notes, tracking links or naming, and the next measurement date.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.