creator-discovery-router

Creator Discovery Router

Use When

• The user wants creators, KOLs, KOCs, influencers, or partnership candidates.
• The request includes platform, niche, follower band, audience, geo, language, seeds, competitor handles, or collaboration fit.
• The first decision is how to collect candidates before outreach.

Do Not Use When

• Do not collect platform data in this skill; route to the narrowest downstream collector.
• Do not expose internal route labels in user-facing explanations.
• Do not stop at route diagnosis when the next skill is already clear.

Core Rule

Do not treat every "find creators" request as keyword profile search.

Extract the real constraints first: platform, follower range, recall range, topic, audience, geo/language, creator type, recency, activity, seeds, and contactability. Use a wider recall band when platform search is noisy, then tighten the shortlist later.

Route Modes

• handle-first: use when the user already has seed creators, competitor handles, usernames, or watchlists. Enrich profiles and recent content.
• content-first: use when niche fit, active posting, content relevance, or follower-band discovery matters. Collect content first, then enrich authors.
• graph-first: use when good candidates are hidden in clusters, hashtags, collaborations, mentions, local-language scenes, or seed-adjacent networks.
• mixed: use when discovery needs multiple passes, such as content-first for active creators, graph-first expansion, then handle-first enrichment.

Routing Heuristics

• Follower range plus niche fit should prefer content-first or graph-first, not keyword-only account search.
• Content relevance should collect posts/videos before ranking creators.
• Audience fit should use recent content patterns, language, and repeated framing instead of trusting bios alone.
• Creator type should be classified before final shortlist: individual creator, brand/product account, educator/consultant, or aggregator.
• Existing seeds should start handle-first; contact-ready leads should be collected, enriched, scored, then handed to outreach.

Default Workflow

1. Normalize the brief internally.
2. Create a machine-readable route artifact when it is useful.
3. Explain the plan in plain business language.
4. Hand off in the same turn when platform and route are clear.
5. Ask one short clarification only when the answer changes the route.

Output Shape

The artifact contains platform, route, primarySkill, explanation, and handoffReady. Use that output as the route artifact, then carry the user's business constraints into the downstream collector.

Stop Conditions

• Stop when required user intent, source evidence, or owned input artifacts are missing and guessing would change the result.
• If an owned CLI or script command fails, report the exact error and stop. Do not bypass the failure with metadata-only answers, readiness probing, local payload rewrites, fallback providers, or unpublished tools.

Handoff

• TikTok discovery -> tiktok-research.
• Instagram creator discovery -> instagram-creator-discovery.
• Instagram account enrichment -> instagram-account-research.
• X account discovery or enrichment -> x-tools.
• Outreach preparation after shortlist -> creator-outreach.

Public Command Boundary

• Choose the smallest matching command or workflow from the user input and run it directly.
• If an owned CLI or script command fails, report the exact error and stop. Do not bypass the failure with metadata-only answers, readiness probing, local payload rewrites, fallback providers, or unpublished tools.
• This public skill is instruction-driven. Produce the artifact described by the workflow directly from the available evidence.
• Do not call private provider/runtime paths or unpublished local tools.
• If the CLI returns a quote-confirmation challenge, run postplus quote confirm --json --challenge-file <challenge.json> and retry with the returned token.