skill-finder
Skill757 starsChanged 8 months agoMITView on GitHub
Find the right Affitor skill for your goal. Triggers on: "which skill should I use", "find me a skill", "what skills are available", "help me choose a skill", "skill for SEO", "skill for email", "explore skills", "I'm new to Affitor", "what can Affitor do", "search skills", "skill for blog writing", "skill for landing pages", "skill for analytics".
26 other projects use a version of this.
Adopted by
Most recently taken up by
- milad-ahmd/agent-skillstheir own version, first seen Nov 8, 2026
- aktsmm/Agent-Skillstheir own version, first seen Nov 8, 2026
- omnigami-ai/skill-findertheir own version, first seen Nov 8, 2026
- c95tj48sd8-a11y/skill-findertheir own version, first seen Nov 8, 2026
- zedarvates/frugal-skillstheir own version, first seen Nov 8, 2026
- chinaretaildesign/agent-skillstheir own version, first seen Nov 8, 2026
Other versions26 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 26
- mizchi/skills★ 369same name
- aktsmm/Agent-Skills★ 26same name
- peter-tu-zynkr/zynkr-skill-builder★ 21same name
- ckorhonen/claude-skills★ 17same name
- geekfujiwara/copilot-cowork-skills★ 13same name
- kargnas/skills★ 9same name
- milad-ahmd/agent-skills★ 5same name
- robinbril/claude-code-harness★ 3same name
- sanyamk23/aphanis★ 3same name
- yfge/skill-finder★ 3same name
16 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
- 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
- your-skill-nameSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Search and discover Affitor skills by task, stage, keyword, or natural language goal.
- Very specific: line 51
Read registry.json from the repository root (or from conversation context if already loaded).
- Very specific: line 61
If stage_filter is provided, restrict results to that stage.
- Distinctive: line 72
If the user's goal spans multiple stages, suggest a skill sequence:
- Distinctive: line 86
Before presenting output, verify:
- Distinctive: line 94
If any check fails, fix the output before delivering.
“Common” is measured: kept by at least 6 in 10 of the 24 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
Skill Finder
Search and discover Affitor skills by task, stage, keyword, or natural language goal. Returns a ranked list of matching skills with descriptions, input requirements, and recommended next steps. Output is a concise Markdown guide.
Stage
S8: Meta — The entry point to the entire Affitor ecosystem. New users don't know what's available. Experienced users forget skill names. Skill Finder bridges the gap — it reads the registry, matches intent to capability, and recommends the fastest path to the user's goal.
When to Use
- User is new to Affitor and asks "what can I do?" or "where do I start?"
- User describes a goal but doesn't name a specific skill
- User wants to find skills by stage (e.g., "what analytics skills exist?")
- User asks "which skill helps with [topic]?"
- User says anything like "find skill", "search skill", "explore skills"
- Chaining: recommended as the first skill for new users before S1-S7
Input Schema
query: string # REQUIRED — natural language: "I want to write a blog review"
# or "what skills help with SEO?" or "analytics skills"
stage_filter: string # OPTIONAL — filter by stage: research | content | blog | landing
# | distribution | analytics | automation | meta
goal: string # OPTIONAL — broader goal: "first commission" | "scale to 1k"
# | "optimize conversions" | "automate my workflow"Workflow
Step 1: Load Skill Catalog
Read registry.json from the repository root (or from conversation context if already loaded). Parse all skills with their stage, name, slug, and description.
Step 2: Match Query to Skills
Match the user's query against:
- Skill names and slugs (exact match → top priority)
- Skill descriptions (keyword overlap)
- Stage labels and descriptions (if user is browsing by stage)
- Inferred intent (e.g., "SEO" →
seo-audit,affiliate-blog-builder)
If stage_filter is provided, restrict results to that stage.
Step 3: Rank Results
Rank matches by relevance:
- Direct name/slug match
- Description keyword match count
- Stage alignment with user's apparent funnel position
Step 4: Recommend a Path
If the user's goal spans multiple stages, suggest a skill sequence:
- "You want to go from zero to first commission → S1 → S2 → S3 → S5"
- "You want to optimize existing content → S6 (seo-audit, ab-test-generator)"
Step 5: Output Results
Present top 3-5 matching skills with:
- Skill name and stage
- What it does (one sentence)
- What input it needs
- Example invocation prompt
Step 6: Self-Validation
Before presenting output, verify:
- All matched skills exist in the current registry
- Example prompts are copy-paste ready and grammatically correct
- Recommended path follows logical funnel sequence
- Relevance ranking: exact match > partial match > related
- Input needed descriptions match actual skill Input Schemas
If any check fails, fix the output before delivering. Do not flag the checklist to the user — just ensure the output passes.
Output Schema
output_schema_version: "1.0.0" # Semver — bump major on breaking changes
matches:
- skill: string # skill slug
stage: string # e.g., "S6: Analytics"
description: string # one-sentence summary
input_needed: string # what the user needs to provide
example_prompt: string # copy-paste prompt to invoke the skill
relevance: string # "exact" | "high" | "related"
recommended_path:
description: string # why this path
steps:
- order: number
skill: string
action: string # what this step accomplishesOutput Format
- Matching Skills — table with skill name, stage, description, and relevance
- How to Use — for each top match, show the exact prompt to invoke it
- Recommended Path — if the goal spans multiple stages, a numbered sequence
Error Handling
- Empty query: "What are you trying to accomplish? For example: 'write a blog review', 'track conversions', or 'plan a full funnel'."
- No matches found: "No skills match '[query]'. Here are all available stages: [list stages]. Try describing your goal differently."
- Too broad query ("everything"): Show one skill per stage as a sampler, then ask: "Which stage interests you most?"
Examples
Example 1: Specific task query
User: "I want to write a blog review of an AI tool"
Action: Match → affiliate-blog-builder (S3, exact), comparison-post-writer (S3, related), viral-post-writer (S2, related). Show top 3 with example prompts. Recommend: "Start with S1 affiliate-program-search to find the best program, then use S3 affiliate-blog-builder for the review."
Example 2: Stage browsing
User: "What analytics skills are available?"
Action: Filter by analytics stage → show all 4: conversion-tracker, ab-test-generator, performance-report, seo-audit. Describe each with input requirements.
Example 3: Goal-oriented
User: "I'm new to affiliate marketing, where do I start?"
Action: Recommend the beginner path: S1 (affiliate-program-search) → S2 (viral-post-writer) → S3 (affiliate-blog-builder) → S5 (bio-link-deployer). Explain each step in one sentence.
References
registry.json— Machine-readable skill catalog. Read in Step 1.shared/references/flywheel-connections.md— master flywheel connection map
Revenue & Action Plan
Expected Outcomes
- Revenue potential: The fastest path to your first commission is using the right skill at the right time. Skill Finder saves you hours of guessing — it matches your current situation to the exact workflow that generates revenue. Affiliates who follow a structured skill sequence report 3x faster time-to-first-commission
- Benchmark: The typical path to first commission: S1 (find product, 30 min) → S2 (create content, 1 hour) → S5 (distribute, 30 min) = first affiliate link live in 2 hours. First commission typically arrives within 7-14 days
- Key metric to track: Time-to-first-commission. How long from "I started" to "I earned my first dollar"? Use
performance-reportto track ongoing revenue
Do This Right Now (15 min)
- Copy the first recommended prompt from the Recommended Path section and run it immediately
- Don't skip steps — the recommended path is ordered for a reason. S1 before S2, S2 before S5
- Set a goal: earn your first commission within 14 days by running one skill per day
- Bookmark this skill — come back whenever you're unsure what to do next
Track Your Results
After running 3-5 skills in sequence: do you have a live affiliate link? Is it getting clicks? If yes, you're on the path. If no, re-run Skill Finder with a more specific goal ("I have a blog but no traffic" vs "I'm starting from zero").
Next step — run the first skill in your Recommended Path!
Flywheel Connections
Feeds Into
- Any skill —
matched_skillroutes the user to the right skill
Fed By
registry.json— skill catalog with all 44 skills across 8 stages
Feedback Loop
- Track which skills are most frequently requested → surface popular skills higher in recommendations
chain_metadata:
skill_slug: "skill-finder"
stage: "meta"
timestamp: string
suggested_next: [] # Dynamic — depends on matched skillDoes 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.

