skill-finder
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".
What this skill does
# 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
```yaml
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:
1. Skill names and slugs (exact match → top priority)
2. Skill descriptions (keyword overlap)
3. Stage labels and descriptions (if user is browsing by stage)
4. 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:
1. Direct name/slug match
2. Description keyword match count
3. 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
```yaml
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 accomplishes
```
## Output Format
1. **Matching Skills** — table with skill name, stage, description, and relevance
2. **How to Use** — for each top match, show the exact prompt to invoke it
3. **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-report` to track ongoing revenue
### Do This Right Now (15 min)
1. **Copy the first recommended prompt** from the Recommended Path section and run it immediately
2. **Don't skip steps** — the recommended path is ordered for a reason. S1 before S2, S2 before S5
3. **Set a goal**: earn your first commission within 14 days by running one skill per day
4. **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_skill` routes 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
```yaml
chain_metadata:
skill_slug: "skill-finder"
stage: "meta"
timestamp: string
suggested_next: [] # Dynamic — depends on matched skill
```
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".