your-skill-name
Skill757 starsChanged 8 months agoMITView on GitHub
Replace with when the AI should activate this skill. Be pushy — cover multiple phrasings so the AI activates for a wide range of user prompts.
49 other projects use a version of this.
Adopted by
Most recently taken up by
- 123ccw/fandextheir own version, first seen Nov 8, 2026
- findscripter/everything-skillstheir own version, first seen Nov 2, 2026
- artherahq/skillstheir own version, first seen Oct 31, 2026
- artheras/skillstheir own version, first seen Oct 31, 2026
- grafana/skillstheir own version, first seen Oct 27, 2026
- osamabinjannat/remote-hiring-skillstheir own version, first seen Oct 25, 2026
Other versions49 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 49
- Fullive-AI/Anima★ 1ksame name
- grafana/skills★ 302same name
- openocta/openocta_skills★ 166same name
- trustwallet/tw-agent-skills★ 111same name
- frankxai/claude-skills-library★ 47same name
- inbharatai/claude-skills★ 33same name
- lionelsimai/claude-skills-collection★ 26same name
- findscripter/everything-skills★ 8same name
- TheArchitectit/awesome-cline-skills★ 8same name
- ceasarXuu/AstartesSkills★ 4same name
39 more not listed
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 repository55 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- affiliate-checkSkill
- ab-test-generatorSkill
- conversion-trackerSkill
- internal-linking-optimizerSkill
- performance-reportSkill
- seo-auditSkill
- content-repurposerSkill
- email-automation-builderSkill
- multi-program-managerSkill
- paid-ad-copy-writerSkill
- proprietary-data-generatorSkill
- affiliate-blog-builderSkill
- comparison-post-writerSkill
- content-decay-detectorSkill
- content-moat-calculatorSkill
- how-to-tutorial-writerSkill
- keyword-cluster-architectSkill
- listicle-generatorSkill
- content-pillar-atomizerSkill
- content-research-briefSkill
- infographic-generatorSkill
- reddit-post-writerSkill
- tiktok-script-writerSkill
- twitter-thread-writerSkill
- viral-post-writerSkill
- bio-link-deployerSkill
- email-drip-sequenceSkill
- github-pages-deployerSkill
- social-media-schedulerSkill
- bonus-stack-builderSkill
- grand-slam-offerSkill
- guarantee-generatorSkill
- landing-page-creatorSkill
- product-showcase-pageSkill
- squeeze-page-builderSkill
- value-ladder-architectSkill
- webinar-registration-pageSkill
- category-designerSkill
- compliance-checkerSkill
- create-skillSkill
- funnel-plannerSkill
- self-improverSkill
- skill-finderSkill
- affiliate-program-searchSkill
- commission-calculatorSkill
- competitor-spySkill
- content-angle-rankerSkill
- find-and-verify-affiliate-programSkill
- monopoly-niche-finderSkill
- niche-opportunity-finderSkill
- purple-cow-auditSkill
- submit-programSkill
- traffic-analyzerSkill
- trending-content-scoutSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 26 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 113
Before delivering output, verify:
- Very specific: line 143
When this skill produces unexpected, incomplete, or incorrect output, generate a skill_feedback block (see …
“Common” is measured: kept by at least 6 in 10 of the 26 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Your Skill Name
What this skill does in 2-3 sentences. Focus on the outcome, not the process.
Stage
This skill belongs to Stage SX: StageName
When to Use
- Scenario 1
- Scenario 2
- Scenario 3
Input Schema
{
required_field: { # (required) Description
name: string # Example value
}
optional_field: string # (optional, default: "value") Description
}Workflow
Step 1: Gather Context
What to check first. How to handle missing inputs.
Step 2: Execute Core Task
The main work the skill does.
Step 3: Format and Deliver
How to structure the output.
Output Schema
Other skills can consume these fields from conversation context:
{
primary_output: string # Main result for downstream chaining
secondary_output: string # Additional data for downstream skills
}Output Format
## [Skill Name]: [Context]
### Section 1
[Main content]
### Section 2
[Supporting content]Error Handling
- Missing required input: How to recover gracefully.
- External data unavailable: Fallback strategy.
- Edge case: How to handle unexpected scenarios.
Examples
Example 1: [realistic user prompt] → [step-by-step what the skill does] → [expected output summary]
Example 2: [different scenario] → [step-by-step] → [expected output summary]
Example 3: [edge case or beginner scenario] → [step-by-step] → [expected output summary]
Flywheel Connections
Feeds Into
[skill](S[X]) — [what data/output flows forward to this skill]
Fed By
[skill](S[X]) — [what data/output flows back from this skill]
Feedback Loop
- [analytics metric or data point that improves this skill's next run]
Quality Gate
Include this section for content-producing skills (S2, S3, S4, S5, S7). Remove for non-content skills.
Before delivering output, verify:
- Would I share this on MY personal social?
- Contains specific, surprising detail? (not generic)
- Respects reader's intelligence?
- Remarkable enough to share? (Purple Cow test)
- Irresistible offer framing? (if S4 offer skills ran)
Any NO → rewrite before delivering. Do not flag this checklist to the user.
Volume Mode
Include this section for S2 Content skills only. Remove for other stages.
When mode: "volume":
- Generate 5-10 variations instead of 1
- Prioritize speed + variety over perfection
- Tag each with variant ID for A/B tracking
- Let data pick the winner (GaryVee philosophy)
volume_output:
variants:
- id: string # e.g., "v1", "v2"
content: string # The variation
angle: string # What makes this one differentFeedback & Issue Reporting
When this skill produces unexpected, incomplete, or incorrect output, generate a
skill_feedback block (see shared/references/feedback-protocol.md for full schema).
Skill-specific failure modes:
- [Failure mode 1]: [What triggers it, what to report]
- [Failure mode 2]: [What triggers it, what to report]
Auto-detect triggers for this skill:
- [Specific condition that means this skill underperformed]
- [Another condition]
Report issues: GitHub Issues | Discussions
References
references/your-reference.md— description of what it containsshared/references/ftc-compliance.md— FTC disclosure requirementsshared/references/affitor-branding.md— branding rulesshared/references/flywheel-connections.md— master flywheel connection mapshared/references/feedback-protocol.md— issue detection and reporting standardshared/references/version-check.md— update notification system
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.

