[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AEEN3KG705K7E6P3TP1B27":3,"skill-same:01M7AEEN3KG705K7E6P3TP1B27":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M7AEEN3KG705K7E6P3TP1B27","influencer-discovery",null,"Use when the user asks to \"find influencers\", \"build an influencer list\", or \"discover creators in [niche]\"; produces a multi-platform candidate pool, per-influencer evidence profiles, authenticity red-flag screening, and a Fit-readiness queue without action ranking. Not for STAR scoring or ranking a known shortlist — use fit-scorer. 达人挖掘\u002F找达人\u002F创作者名单","iamwaqargulzar\u002FMarketing-Agent-OS","iamwaqargulzar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96654715?v=4","01M7ACMBN0TACNXY53QYG8KDF6","Waqar Gulzar","01M7ACMBNP5ZX60H8CD3JK0633",8,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Finfluencer\u002Fscout\u002Finfluencer-discovery\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: influencer-discovery\nslug: influencer-discovery\ndisplayName: \"Influencer Discovery · 红人发现\"\nsummary: \"多平台红人挖掘:候选池、证据画像、真实性红旗筛查与 Fit 就绪队列\"\ndescription: 'Use when the user asks to \"find influencers\", \"build an influencer list\", or \"discover creators in [niche]\"; produces a multi-platform candidate pool, per-influencer evidence profiles, authenticity red-flag screening, and a Fit-readiness queue without action ranking. Not for STAR scoring or ranking a known shortlist — use fit-scorer. 达人挖掘\u002F找达人\u002F创作者名单'\nversion: \"20.1.0\"\nlicense: Apache-2.0\ncompatibility: \"Claude Code and compatible agent-skill hosts\"\nhomepage: \"https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Faaron-marketing-skills\"\nwhen_to_use: \"Activate when building an influencer roster from scratch, expanding into a new platform or niche, replacing churned partners, finding micro and nano creators at scale, identifying which influencers a competitor partners with, or standing up an always-on discovery pipeline. The user names a niche, platform, follower band, or brand and wants a list of candidate creators to evaluate.\"\nargument-hint: \"\u003Cbrand or niche> [platform] [follower-range]\"\nmetadata: {\"author\": \"aaron-he-zhu\", \"version\": \"20.1.0\", \"discipline\": \"influencer\", \"phase\": \"scout\", \"geo-relevance\": \"low\", \"hermes\": {\"tags\": [\"marketing\", \"influencer\", \"scout\"], \"category\": \"influencer\"}, \"openclaw\": {\"emoji\": \"📣\", \"homepage\": \"https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Faaron-marketing-skills\"}}\n---\n\n# Influencer Discovery\n\nFind evidence-backed creator candidates across platforms, screen them against declared discovery filters, and build a non-ranked readiness queue for typed Fit evaluation.\n\n## Quick Start\n\n```\nFind 20 influencers in [niche] for [brand\u002Fproduct]\n```\n\n```\nFind influencers in [niche] with 50K-200K followers on TikTok and Instagram,\nbased in [location], engagement above 4%, who have worked with brands like [brand]\n```\n\n## Skill Contract\n\n- **Reads**: brand\u002Fproduct, niche or category, target platforms, follower range, engagement floor, decision-relevant geography\u002Flanguage, audience demographics, exclusions; dated candidate records from a user export, public source, roster, or live connector; the current campaign's STAR `evidence_window` when supplied; prior `entity-registry` brand profile and any `audience-mapper` output if present in memory; existing roster records under `memory\u002Fcreators\u002F` (dedupe only through verified identity links against creators already rostered by [creator-registry](..\u002F..\u002F..\u002Fprotocol\u002Fcreator-registry\u002FSKILL.md)).\n- **Writes**: return discovery results inline by default; only with separate exact authorization, save them to `memory\u002Finfluencer\u002Finfluencer-discovery\u002FYYYY-MM-DD-\u003Ctopic>.md`. A saved artifact uses a stable opaque `creator_ref` plus pseudonymous `recipient_ref`, `contact_source_ref`, and `agency_ref`, keeps raw handles, profile URLs, and contact coordinates transient-only, and retains geography only at the granularity required by the declared filter. Save an opaque `handle_ref`\u002F`source_ref` identity resolver only when the authorized source artifact or verified creator-registry link can resolve it. Without one, keep `identity_status: unresolved`, save no hidden raw-locator mapping, and set `cross_session_locator_required: true`. Reuse a verified creator-registry aggregate ID when one exists; otherwise generate `creator-\u003CUUIDv4>` once for the candidate lineage. Never set `creator_ref` to a raw handle, name, URL, email, provider ID, or a deterministic hash of any of them. Each roster-worthy creator update requires another exact authorization for an `operation: propose` request through `registry-events.py` to `memory\u002Fevents\u002Fcreators.ndjson`; only `creator-registry` writes canonical records under `memory\u002Fcreators\u002F`.\n- **Promotes**: only with separate exact authorization, durable facts (verified creator\u002Fhandle refs, confirmed niche\u002Fplatform coverage, competitor-saturated creators) to `memory\u002Fhot-cache.md`; discovery readiness or queue position is not a durable ranking fact.\n- **Done when**:\n  - The required search criteria are present; otherwise stop with `NEEDS_INPUT` and name the missing criteria without fabricating candidates.\n  - Exactly two raw locators without complete criteria\u002Fevidence remain `NEEDS_INPUT`, not a vetted shortlist. A separately authorized partial checkpoint is labeled `PARTIAL`, lists every gap, and contains no tier or rank.\n  - A candidate pool exists with at least the requested count screened past follower, engagement, and brand-safety filters.\n  - Each candidate has a field-level evidence trail (`provider\u002Ftool`, `source_ref`, `observed_at`, window, evidence label), an audience read, and an evidence-completeness triage state (`READY_FOR_FIT | NEEDS_REFRESH | INELIGIBLE`) that is neither a score nor a STAR Suitability verdict.\n  - Every candidate keeps one stable opaque `creator_ref` across the report and handoff; raw identity locators remain transient and are never copied into `creator_ref`.\n  - Conflicting observations remain separate, identity merges have a verified cross-link, and the Fit handoff marks each volatile field `current`, `stale`, or `unknown` against the current STAR `evidence_window` with any `refresh_required` fields named.\n  - A non-ranked Fit-readiness queue is compiled with next-step pointers; every stale\u002Funknown required field produces `NEEDS_REFRESH`, `NOT_RANKED`, and `NEEDS_INPUT` until refreshed.\n- **Primary next skill**: [fit-scorer](..\u002Ffit-scorer\u002FSKILL.md) — score and rank the discovered candidates with weighted criteria.\n\n### Handoff Summary\n\n> Emit the standard shape from [skill-contract.md §Handoff Summary Format](..\u002F..\u002F..\u002Freferences\u002Fskill-contract.md).\n\n## Data Sources\n\nPlanning and screening need no live integration (Tier 1), but a real creator list still needs candidate records: public handles\u002Flinks or an export supplied by the user, existing roster records, or a live search connector. Search criteria alone are not evidence that any specific creator or metric exists. If no candidate source is available, return a query\u002Fcollection plan and `NEEDS_INPUT`; never invent handles, profiles, counts, or audience data.\n\nNormalize evidence only in the report template, not through a new ingestion layer. For every factual field retain `provider\u002Ftool`, `source_ref`, `observed_at`, the measurement window (or `not-supplied`), and one label: `Measured`, `Calculated`, `Estimated`, `User-provided`, or `Proxy`. Keep conflicting values for the same field as parallel observations; do not average them, prefer the newest automatically, or merge identities from names\u002Fhandles alone. A cross-provider identity becomes one creator only after a verified cross-link or explicit user confirmation.\n\nWhere a tool *could* sharpen results, use `~~` connector placeholders:\n\n- `~~influencer database` — bulk discovery, follower\u002Fengagement metrics, audience demographics.\n- `~~social platform analytics` — native creator-marketplace data, trending sounds, related accounts.\n- `~~CRM` — surface possible existing-partner matches for verified identity-link review; never auto-merge records.\n- `~~audience overlap` — estimate creator-audience vs. brand-audience match.\n\n**Keyless candidate-card metadata (oEmbed)**: YouTube (`https:\u002F\u002Fwww.youtube.com\u002Foembed?url=\u003Cvideo-url>&format=json`), TikTok (`https:\u002F\u002Fwww.tiktok.com\u002Foembed?url=\u003Cpost-url>`), and X (`https:\u002F\u002Fpublish.twitter.com\u002Foembed?url=\u003Cpost-url>`) return a post's title, author name\u002Fhandle, and thumbnail with **no key** — enough to resolve a candidate transiently and retain an opaque verified-handle evidence ref instead of hand-copying identity data. A handle ref remains separate from `creator_ref`: only an explicitly carried upstream `creator_ref` or a verified creator-registry identity link may resolve the aggregate; otherwise create a fresh random opaque ref and preserve the identity gap. Metadata only: no follower or engagement metrics, so those stay `~~influencer database` or manual export — **except YouTube**, below.\n\n**Measured YouTube metrics (free key)**: `python3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fconnectors\u002Fyoutube.py\" channel @handle` returns the real displayed subscriber count, total views, and video count, and `youtube.py videos @handle --limit 10` adds per-video views\u002Flikes\u002Fcomments — upgrading a YouTube candidate's profile row from Estimated to **Measured**. Free `YOUTUBE_API_KEY` (10,000 units\u002Fday; one channel check ≈ 1–3 units). ToS boundary: vet a **named shortlist**, don't build a bulk creator database — quota extensions are refused for competitive harvesting. See [scripts\u002Fconnectors\u002FREADME.md](..\u002F..\u002F..\u002Fscripts\u002Fconnectors\u002FREADME.md).\n\nSee [CONNECTORS.md](..\u002F..\u002F..\u002FCONNECTORS.md) for the free\u002Fkeyless recipe per category and the opt-in MCP layer. None are required — every step degrades to user-supplied inputs.\n\n## Instructions\n\nEach step has a fill-in block in [references\u002Ftemplates.md](references\u002Ftemplates.md) — copy the matching block. This skill does *not* compute a per-influencer score, STAR Suitability verdict, outreach priority, or action rank. It records evidence completeness and declared-filter results; [fit-scorer](..\u002Ffit-scorer\u002FSKILL.md) owns typed comparison and ranking downstream.\n\n1. **Define search criteria.** Capture brand, goal, audience definition, budget\u002Ffollower tier, platforms, engagement floor, location\u002Flanguage, exclusions, and the required\u002Fpreferred parameter table. If any required criterion is missing, stop with `NEEDS_INPUT`; offer [audience-mapper](..\u002Faudience-mapper\u002FSKILL.md) only when the user wants help defining the audience. Step 1 template.\n2. **Conduct the search.** Work hashtags, similar-accounts, competitor mentions, and platform-native discovery. Raw handles\u002Fprofile URLs may appear only in Step 2's transient lookup block and must be removed before any save or handoff. Log the saved-safe batch with `creator_ref`, identity status, opaque `handle_ref`\u002F`source_ref` when resolvable, provider\u002Ftool, query purpose, `observed_at`, window, and evidence label. If no public handles\u002Flinks, user export, roster records, or live search connector can supply candidate records, produce the exact query pack and collection template, return `NEEDS_INPUT`, and stop before naming creators. Step 2 template.\n3. **Initial screening.** Filter the pool on follower range, engagement, recency, relevance, and brand safety; tally red flags (suspected fake followers, controversy, competitor exclusivity, inactivity). These are discovery signals, not verified STAR failures or vetoes; unsupported applicable evidence remains Unknown for downstream scoring. Per-platform reading cues: [references\u002Fplatform-vetting.md](references\u002Fplatform-vetting.md). Step 3 template.\n4. **Build influencer profiles.** For each qualified creator, first reuse an explicitly carried opaque `creator_ref` or a creator-registry aggregate ID whose handle link is verified. If neither exists, generate one random `creator-\u003CUUIDv4>` and reuse it unchanged throughout this report lineage. Never derive it from a handle or other identity data. Save an opaque handle\u002Fevidence ref only when an authorized artifact or verified registry link resolves it; otherwise keep `identity_status: unresolved`, create no hidden locator map, and require the raw locator again in a later session. Then fill the profile (pseudonymous identity refs, field-level metrics and audience evidence, content, partnership history, contact-path refs, and evidence-completeness triage state). Preserve conflicts as parallel rows and merge provider identities only after a verified cross-link. Compare each volatile observation with the current campaign's STAR `evidence_window`: within it is `current`; outside it is `stale`; a missing window\u002Fdate or absent STAR window is `unknown`. A stale or unknown required field stays visible, becomes `refresh_required`, and forces `triage_state: NEEDS_REFRESH`, `ranking_status: NOT_RANKED`, and `NEEDS_INPUT`; never invent a global TTL. Do not emit a score, recommendation tier, or STAR Suitability verdict. For a deep single-creator read with a contact waterfall, use [references\u002Fcreator-dossier.md](references\u002Fcreator-dossier.md). Step 4 template.\n5. **Compile the discovery report.** Roll profiles into summary stats, descriptive platform\u002Ffollower-band breakdowns, and three non-ranked evidence queues: `READY_FOR_FIT`, `NEEDS_REFRESH`, and `INELIGIBLE` under the declared filters. Do not recommend a creator mix, label anyone Priority\u002FHighly Recommended, or action-rank candidates before typed Fit. If the input is only two raw locators and criteria\u002Fevidence are incomplete, return `NEEDS_INPUT` and do not save a vetted pool. A partial checkpoint requires separate exact save authorization, must say `PARTIAL`\u002F`NOT_VETTED`, list criteria\u002Fevidence gaps, and contain no rank, score, “top” label, or fit-scorer handoff. Step 5 template.\n6. **Add insights.** Note niche content trends, the competitive picture, and recommendations for future searches. Step 6 template.\n\nReturn the discovery report inline. Saving the report, caching the shortlist, and submitting each roster-worthy creator through `registry-events.py` as `operation: propose` are three separate operations and each requires exact authorization; without it, offer the eligible path and write nothing. After a vetted shortlist exists, hand [fit-scorer](..\u002Ffit-scorer\u002FSKILL.md) the field-level evidence plus the STAR `evidence_window`, `freshness_status`, and `refresh_required` list; if no current STAR window exists, mark freshness `unknown` rather than inventing one. `fit-scorer` records the S1-S10 evidence read; [creator-content-auditor](..\u002F..\u002Factivate\u002Fcreator-content-auditor\u002FSKILL.md) alone determines verified STAR vetoes and renders the gate verdict.\n\n## Compact Example\n\n**User**: \"Find 15 micro-influencers (10K-100K followers) in sustainable fashion for a new eco clothing brand.\"\n\n**Illustrative output when a dated export or live connector returned candidate records**: create one field-level evidence profile per opaque `creator_ref`, then place each row in `READY_FOR_FIT`, `NEEDS_REFRESH`, or `INELIGIBLE` under the declared filters. All rows remain `NOT_RANKED`; stale\u002Funknown required fields are `NEEDS_INPUT`, and only the current complete rows hand off to `fit-scorer`. Without candidate records, return only the query\u002Fcollection plan and `NEEDS_INPUT`. The report is returned inline, then save, promotion, and registry-proposal permissions are offered separately. Full walkthrough in [references\u002Ftemplates.md](references\u002Ftemplates.md#worked-example--sustainable-fashion-micro-influencers).\n\n## Reference Materials\n\n- [references\u002Ftemplates.md](references\u002Ftemplates.md) — all step fill-in blocks (criteria, search, screening, profile, report, insights), the worked example, tips, and the \"what\u002Fwhen\" overview.\n- [references\u002Fplatform-vetting.md](references\u002Fplatform-vetting.md) — per-platform creator playbooks (X\u002FLinkedIn\u002FTikTok\u002FYouTube\u002FReddit) feeding screening and profiling in steps 3-4.\n- [references\u002Fcreator-dossier.md](references\u002Fcreator-dossier.md) — structured per-creator dossier from public data, with a contact-discovery waterfall.\n- [skill-contract.md](..\u002F..\u002F..\u002Freferences\u002Fskill-contract.md) — shared contract and Handoff Summary format.\n- [state-model.md](..\u002F..\u002F..\u002Freferences\u002Fstate-model.md) — memory tiers and save-path conventions.\n- [CONNECTORS.md](..\u002F..\u002F..\u002FCONNECTORS.md) — free\u002Fkeyless data recipes and opt-in MCP layer.\n- STAR benchmark at [references\u002Fstar-benchmark.md](..\u002F..\u002F..\u002Freferences\u002Fstar-benchmark.md) — scoring framework that fit-scorer applies downstream.\n- Siblings in the scout phase: [fit-scorer](..\u002Ffit-scorer\u002FSKILL.md), [audience-mapper](..\u002Faudience-mapper\u002FSKILL.md), [trend-spotter](..\u002Ftrend-spotter\u002FSKILL.md).\n\n## Next Best Skill\n\n**Primary**: [fit-scorer](..\u002Ffit-scorer\u002FSKILL.md) — score and rank the discovered candidates with weighted criteria before outreach.\n\n**Alternates (same influencer family)**:\n- [competitor-tracker](..\u002F..\u002Ftarget\u002Fcompetitor-tracker\u002FSKILL.md) — when discovery surfaced competitor-saturated creators and you want to map the competitive field first.\n- [audience-mapper](..\u002Faudience-mapper\u002FSKILL.md) — when the target audience is still fuzzy and criteria need sharpening before a re-search.\n\n**Termination**: Maintain a visited-set. If a skill has already been invoked this session, stop and report chain-complete rather than re-invoking it. Max chain depth is 3 hops from the originating request; stop and summarize when reached.\n\n## Related Skills\n\n- [audience-mapper](..\u002Faudience-mapper\u002FSKILL.md) - Define who to reach\n- [fit-scorer](..\u002Ffit-scorer\u002FSKILL.md) - Score and rank discovered influencers\n- [competitor-tracker](..\u002F..\u002Ftarget\u002Fcompetitor-tracker\u002FSKILL.md) - Find competitor influencers\n- [outreach-manager](..\u002F..\u002Factivate\u002Foutreach-manager\u002FSKILL.md) - Contact discovered influencers\n","# Influencer Discovery\n\nFind evidence-backed creator candidates across platforms, screen them against declared discovery filters, and build a non-ranked readiness queue for typed Fit evaluation.\n\n## Quick Start\n\n```\nFind 20 influencers in [niche] for [brand\u002Fproduct]\n```\n\n```\nFind influencers in [niche] with 50K-200K followers on TikTok and Instagram,\nbased in [location], engagement above 4%, who have worked with brands like [brand]\n```\n\n## Skill Contract\n\n- **Reads**: brand\u002Fproduct, niche or category, target platforms, follower range, engagement floor, decision-relevant geography\u002Flanguage, audience demographics, exclusions; dated candidate records from a user export, public source, roster, or live connector; the current campaign's STAR `evidence_window` when supplied; prior `entity-registry` brand profile and any `audience-mapper` output if present in memory; existing roster records under `memory\u002Fcreators\u002F` (dedupe only through verified identity links against creators already rostered by [creator-registry](..\u002F..\u002F..\u002Fprotocol\u002Fcreator-registry\u002FSKILL.md)).\n- **Writes**: return discovery results inline by default; only with separate exact authorization, save them to `memory\u002Finfluencer\u002Finfluencer-discovery\u002FYYYY-MM-DD-\u003Ctopic>.md`. A saved artifact uses a stable opaque `creator_ref` plus pseudonymous `recipient_ref`, `contact_source_ref`, and `agency_ref`, keeps raw handles, profile URLs, and contact coordinates transient-only, and retains geography only at the granularity required by the declared filter. Save an opaque `handle_ref`\u002F`source_ref` identity resolver only when the authorized source artifact or verified creator-registry link can resolve it. Without one, keep `identity_status: unresolved`, save no hidden raw-locator mapping, and set `cross_session_locator_required: true`. Reuse a verified creator-registry aggregate ID when one exists; otherwise generate `creator-\u003CUUIDv4>` once for the candidate lineage. Never set `creator_ref` to a raw handle, name, URL, email, provider ID, or a deterministic hash of any of them. Each roster-worthy creator update requires another exact authorization for an `operation: propose` request through `registry-events.py` to `memory\u002Fevents\u002Fcreators.ndjson`; only `creator-registry` writes canonical records under `memory\u002Fcreators\u002F`.\n- **Promotes**: only with separate exact authorization, durable facts (verified creator\u002Fhandle refs, confirmed niche\u002Fplatform coverage, competitor-saturated creators) to `memory\u002Fhot-cache.md`; discovery readiness or queue position is not a durable ranking fact.\n- **Done when**:\n  - The required search criteria are present; otherwise stop with `NEEDS_INPUT` and name the missing criteria without fabricating candidates.\n  - Exactly two raw locators without complete criteria\u002Fevidence remain `NEEDS_INPUT`, not a vetted shortlist. A separately authorized partial checkpoint is labeled `PARTIAL`, lists every gap, and contains no tier or rank.\n  - A candidate pool exists with at least the requested count screened past follower, engagement, and brand-safety filters.\n  - Each candidate has a field-level evidence trail (`provider\u002Ftool`, `source_ref`, `observed_at`, window, evidence label), an audience read, and an evidence-completeness triage state (`READY_FOR_FIT | NEEDS_REFRESH | INELIGIBLE`) that is neither a score nor a STAR Suitability verdict.\n  - Every candidate keeps one stable opaque `creator_ref` across the report and handoff; raw identity locators remain transient and are never copied into `creator_ref`.\n  - Conflicting observations remain separate, identity merges have a verified cross-link, and the Fit handoff marks each volatile field `current`, `stale`, or `unknown` against the current STAR `evidence_window` with any `refresh_required` fields named.\n  - A non-ranked Fit-readiness queue is compiled with next-step pointers; every stale\u002Funknown required field produces `NEEDS_REFRESH`, `NOT_RANKED`, and `NEEDS_INPUT` until refreshed.\n- **Primary next skill**: [fit-scorer](..\u002Ffit-scorer\u002FSKILL.md) — score and rank the discovered candidates with weighted criteria.\n\n### Handoff Summary\n\n> Emit the standard shape from [skill-contract.md §Handoff Summary Format](..\u002F..\u002F..\u002Freferences\u002Fskill-contract.md).\n\n## Data Sources\n\nPlanning and screening need no live integration (Tier 1), but a real creator list still needs candidate records: public handles\u002Flinks or an export supplied by the user, existing roster records, or a live search connector. Search criteria alone are not evidence that any specific creator or metric exists. If no candidate source is available, return a query\u002Fcollection plan and `NEEDS_INPUT`; never invent handles, profiles, counts, or audience data.\n\nNormalize evidence only in the report template, not through a new ingestion layer. For every factual field retain `provider\u002Ftool`, `source_ref`, `observed_at`, the measurement window (or `not-supplied`), and one label: `Measured`, `Calculated`, `Estimated`, `User-provided`, or `Proxy`. Keep conflicting values for the same field as parallel observations; do not average them, prefer the newest automatically, or merge identities from names\u002Fhandles alone. A cross-provider identity becomes one creator only after a verified cross-link or explicit user confirmation.\n\nWhere a tool *could* sharpen results, use `~~` connector placeholders:\n\n- `~~influencer database` — bulk discovery, follower\u002Fengagement metrics, audience demographics.\n- `~~social platform analytics` — native creator-marketplace data, trending sounds, related accounts.\n- `~~CRM` — surface possible existing-partner matches for verified identity-link review; never auto-merge records.\n- `~~audience overlap` — estimate creator-audience vs. brand-audience match.\n\n**Keyless candidate-card metadata (oEmbed)**: YouTube (`https:\u002F\u002Fwww.youtube.com\u002Foembed?url=\u003Cvideo-url>&format=json`), TikTok (`https:\u002F\u002Fwww.tiktok.com\u002Foembed?url=\u003Cpost-url>`), and X (`https:\u002F\u002Fpublish.twitter.com\u002Foembed?url=\u003Cpost-url>`) return a post's title, author name\u002Fhandle, and thumbnail with **no key** — enough to resolve a candidate transiently and retain an opaque verified-handle evidence ref instead of hand-copying identity data. A handle ref remains separate from `creator_ref`: only an explicitly carried upstream `creator_ref` or a verified creator-registry identity link may resolve the aggregate; otherwise create a fresh random opaque ref and preserve the identity gap. Metadata only: no follower or engagement metrics, so those stay `~~influencer database` or manual export — **except YouTube**, below.\n\n**Measured YouTube metrics (free key)**: `python3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fconnectors\u002Fyoutube.py\" channel @handle` returns the real displayed subscriber count, total views, and video count, and `youtube.py videos @handle --limit 10` adds per-video views\u002Flikes\u002Fcomments — upgrading a YouTube candidate's profile row from Estimated to **Measured**. Free `YOUTUBE_API_KEY` (10,000 units\u002Fday; one channel check ≈ 1–3 units). ToS boundary: vet a **named shortlist**, don't build a bulk creator database — quota extensions are refused for competitive harvesting. See [scripts\u002Fconnectors\u002FREADME.md](..\u002F..\u002F..\u002Fscripts\u002Fconnectors\u002FREADME.md).\n\nSee [CONNECTORS.md](..\u002F..\u002F..\u002FCONNECTORS.md) for the free\u002Fkeyless recipe per category and the opt-in MCP layer. None are required — every step degrades to user-supplied inputs.\n\n## Instructions\n\nEach step has a fill-in block in [references\u002Ftemplates.md](references\u002Ftemplates.md) — copy the matching block. This skill does *not* compute a per-influencer score, STAR Suitability verdict, outreach priority, or action rank. It records evidence completeness and declared-filter results; [fit-scorer](..\u002Ffit-scorer\u002FSKILL.md) owns typed comparison and ranking downstream.\n\n1. **Define search criteria.** Capture brand, goal, audience definition, budget\u002Ffollower tier, platforms, engagement floor, location\u002Flanguage, exclusions, and the required\u002Fpreferred parameter table. If any required criterion is missing, stop with `NEEDS_INPUT`; offer [audience-mapper](..\u002Faudience-mapper\u002FSKILL.md) only when the user wants help defining the audience. Step 1 template.\n2. **Conduct the search.** Work hashtags, similar-accounts, competitor mentions, and platform-native discovery. Raw handles\u002Fprofile URLs may appear only in Step 2's transient lookup block and must be removed before any save or handoff. Log the saved-safe batch with `creator_ref`, identity status, opaque `handle_ref`\u002F`source_ref` when resolvable, provider\u002Ftool, query purpose, `observed_at`, window, and evidence label. If no public handles\u002Flinks, user export, roster records, or live search connector can supply candidate records, produce the exact query pack and collection template, return `NEEDS_INPUT`, and stop before naming creators. Step 2 template.\n3. **Initial screening.** Filter the pool on follower range, engagement, recency, relevance, and brand safety; tally red flags (suspected fake followers, controversy, competitor exclusivity, inactivity). These are discovery signals, not verified STAR failures or vetoes; unsupported applicable evidence remains Unknown for downstream scoring. Per-platform reading cues: [references\u002Fplatform-vetting.md](references\u002Fplatform-vetting.md). Step 3 template.\n4. **Build influencer profiles.** For each qualified creator, first reuse an explicitly carried opaque `creator_ref` or a creator-registry aggregate ID whose handle link is verified. If neither exists, generate one random `creator-\u003CUUIDv4>` and reuse it unchanged throughout this report lineage. Never derive it from a handle or other identity data. Save an opaque handle\u002Fevidence ref only when an authorized artifact or verified registry link resolves it; otherwise keep `identity_status: unresolved`, create no hidden locator map, and require the raw locator again in a later session. Then fill the profile (pseudonymous identity refs, field-level metrics and audience evidence, content, partnership history, contact-path refs, and evidence-completeness triage state). Preserve conflicts as parallel rows and merge provider identities only after a verified cross-link. Compare each volatile observation with the current campaign's STAR `evidence_window`: within it is `current`; outside it is `stale`; a missing window\u002Fdate or absent STAR window is `unknown`. A stale or unknown required field stays visible, becomes `refresh_required`, and forces `triage_state: NEEDS_REFRESH`, `ranking_status: NOT_RANKED`, and `NEEDS_INPUT`; never invent a global TTL. Do not emit a score, recommendation tier, or STAR Suitability verdict. For a deep single-creator read with a contact waterfall, use [references\u002Fcreator-dossier.md](references\u002Fcreator-dossier.md). Step 4 template.\n5. **Compile the discovery report.** Roll profiles into summary stats, descriptive platform\u002Ffollower-band breakdowns, and three non-ranked evidence queues: `READY_FOR_FIT`, `NEEDS_REFRESH`, and `INELIGIBLE` under the declared filters. Do not recommend a creator mix, label anyone Priority\u002FHighly Recommended, or action-rank candidates before typed Fit. If the input is only two raw locators and criteria\u002Fevidence are incomplete, return `NEEDS_INPUT` and do not save a vetted pool. A partial checkpoint requires separate exact save authorization, must say `PARTIAL`\u002F`NOT_VETTED`, list criteria\u002Fevidence gaps, and contain no rank, score, “top” label, or fit-scorer handoff. Step 5 template.\n6. **Add insights.** Note niche content trends, the competitive picture, and recommendations for future searches. Step 6 template.\n\nReturn the discovery report inline. Saving the report, caching the shortlist, and submitting each roster-worthy creator through `registry-events.py` as `operation: propose` are three separate operations and each requires exact authorization; without it, offer the eligible path and write nothing. After a vetted shortlist exists, hand [fit-scorer](..\u002Ffit-scorer\u002FSKILL.md) the field-level evidence plus the STAR `evidence_window`, `freshness_status`, and `refresh_required` list; if no current STAR window exists, mark freshness `unknown` rather than inventing one. `fit-scorer` records the S1-S10 evidence read; [creator-content-auditor](..\u002F..\u002Factivate\u002Fcreator-content-auditor\u002FSKILL.md) alone determines verified STAR vetoes and renders the gate verdict.\n\n## Compact Example\n\n**User**: \"Find 15 micro-influencers (10K-100K followers) in sustainable fashion for a new eco clothing brand.\"\n\n**Illustrative output when a dated export or live connector returned candidate records**: create one field-level evidence profile per opaque `creator_ref`, then place each row in `READY_FOR_FIT`, `NEEDS_REFRESH`, or `INELIGIBLE` under the declared filters. All rows remain `NOT_RANKED`; stale\u002Funknown required fields are `NEEDS_INPUT`, and only the current complete rows hand off to `fit-scorer`. Without candidate records, return only the query\u002Fcollection plan and `NEEDS_INPUT`. The report is returned inline, then save, promotion, and registry-proposal permissions are offered separately. Full walkthrough in [references\u002Ftemplates.md](references\u002Ftemplates.md#worked-example--sustainable-fashion-micro-influencers).\n\n## Reference Materials\n\n- [references\u002Ftemplates.md](references\u002Ftemplates.md) — all step fill-in blocks (criteria, search, screening, profile, report, insights), the worked example, tips, and the \"what\u002Fwhen\" overview.\n- [references\u002Fplatform-vetting.md](references\u002Fplatform-vetting.md) — per-platform creator playbooks (X\u002FLinkedIn\u002FTikTok\u002FYouTube\u002FReddit) feeding screening and profiling in steps 3-4.\n- [references\u002Fcreator-dossier.md](references\u002Fcreator-dossier.md) — structured per-creator dossier from public data, with a contact-discovery waterfall.\n- [skill-contract.md](..\u002F..\u002F..\u002Freferences\u002Fskill-contract.md) — shared contract and Handoff Summary format.\n- [state-model.md](..\u002F..\u002F..\u002Freferences\u002Fstate-model.md) — memory tiers and save-path conventions.\n- [CONNECTORS.md](..\u002F..\u002F..\u002FCONNECTORS.md) — free\u002Fkeyless data recipes and opt-in MCP layer.\n- STAR benchmark at [references\u002Fstar-benchmark.md](..\u002F..\u002F..\u002Freferences\u002Fstar-benchmark.md) — scoring framework that fit-scorer applies downstream.\n- Siblings in the scout phase: [fit-scorer](..\u002Ffit-scorer\u002FSKILL.md), [audience-mapper](..\u002Faudience-mapper\u002FSKILL.md), [trend-spotter](..\u002Ftrend-spotter\u002FSKILL.md).\n\n## Next Best Skill\n\n**Primary**: [fit-scorer](..\u002Ffit-scorer\u002FSKILL.md) — score and rank the discovered candidates with weighted criteria before outreach.\n\n**Alternates (same influencer family)**:\n- [competitor-tracker](..\u002F..\u002Ftarget\u002Fcompetitor-tracker\u002FSKILL.md) — when discovery surfaced competitor-saturated creators and you want to map the competitive field first.\n- [audience-mapper](..\u002Faudience-mapper\u002FSKILL.md) — when the target audience is still fuzzy and criteria need sharpening before a re-search.\n\n**Termination**: Maintain a visited-set. If a skill has already been invoked this session, stop and report chain-complete rather than re-invoking it. Max chain depth is 3 hops from the originating request; stop and summarize when reached.\n\n## Related Skills\n\n- [audience-mapper](..\u002Faudience-mapper\u002FSKILL.md) - Define who to reach\n- [fit-scorer](..\u002Ffit-scorer\u002FSKILL.md) - Score and rank discovered influencers\n- [competitor-tracker](..\u002F..\u002Ftarget\u002Fcompetitor-tracker\u002FSKILL.md) - Find competitor influencers\n- [outreach-manager](..\u002F..\u002Factivate\u002Foutreach-manager\u002FSKILL.md) - Contact discovered influencers\n",{"name":5,"slug":5,"license":15,"summary":24,"version":25,"homepage":26,"metadata":27,"description":7,"displayName":37,"when_to_use":38,"argument-hint":39,"compatibility":40},"多平台红人挖掘:候选池、证据画像、真实性红旗筛查与 Fit 就绪队列","20.1.0","https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Faaron-marketing-skills",{"phase":28,"author":29,"hermes":30,"version":25,"openclaw":34,"discipline":33,"geo-relevance":36},"scout","aaron-he-zhu",{"tags":31,"category":33},[32,33,28],"marketing","influencer",{"emoji":35,"homepage":26},"📣","low","Influencer Discovery · 红人发现","Activate when building an influencer roster from scratch, expanding into a new platform or niche, replacing churned partners, finding micro and nano creators at scale, identifying which influencers a competitor partners with, or standing up an always-on discovery pipeline. The user names a niche, platform, follower band, or brand and wants a list of candidate creators to evaluate.","\u003Cbrand or niche> [platform] [follower-range]","Claude Code and compatible agent-skill hosts","main","ad108f7eb3f6764136d02fb875772ebb34f54078","upstreams\u002Fsource-a\u002Finfluencer\u002Fscout\u002Finfluencer-discovery",2,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar","iamwaqargulzar.com","2026-11-03 21:14:34",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill influencer-discovery",{"tool":55,"command":56},"bunx","bunx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill influencer-discovery",{"tool":58,"command":59},"pnpm","pnpm dlx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill influencer-discovery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Finfluencer\u002Fscout\u002Finfluencer-discovery\u002FSKILL.md",true,[63,69,73],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fcreator-dossier.md","REFERENCE","参考文档",8688,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Finfluencer\u002Fscout\u002Finfluencer-discovery\u002Freferences\u002Fcreator-dossier.md",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fplatform-vetting.md",1500,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Finfluencer\u002Fscout\u002Finfluencer-discovery\u002Freferences\u002Fplatform-vetting.md",{"path":74,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Ftemplates.md",23734,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Finfluencer\u002Fscout\u002Finfluencer-discovery\u002Freferences\u002Ftemplates.md",[78,85,92,99,106,113],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7AG5VYEX7J2R2AAD54A7YT7","video","When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Sora,' 'Runway,' 'Kling,' 'Seedance,' 'Hailuo,' 'MiniMax,' 'Pika,' 'Hunyuan,' 'Wan,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'record a product demo,' 'feature demo video,' 'in-app demo,' 'video pipeline,' 'copy this edit,' 'match this video style,' 'reverse-engineer this video,' 'edit like this reference,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social. For paid video ad creative, see ad-creative.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fvideo\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7AG5FMXWA33FQDNS9PS1TE6","social","When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter\u002FX, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' 'grow my following,' 'TikTok video,' 'Reels,' 'Shorts,' 'video script,' 'video hook,' 'short-form video,' 'create a reel,' 'social listening,' 'brand mentions,' 'competitor monitoring,' 'top posts to comment on,' 'find people asking for,' 'carousel,' 'slide-by-slide,' or 'document post.' Use this for social content, repurposing, scheduling, video scripts, and listening. Posts avoid AI tells like 'it's not X, it's Y' reveals and broetry. For broader content strategy, see content-strategy. For paid ads, see ad-creative. For earned media, see public-relations.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsocial\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7AG559W96W3DGE31KXYY78S","sms","When the user wants to plan, build, or optimize SMS, MMS, or WhatsApp marketing — including welcome flows, abandoned cart texts, post-purchase, win-back, promotional sends, or transactional\u002Fauth SMS. Also use when the user mentions \"SMS marketing,\" \"text message campaigns,\" \"SMS sequence,\" \"SMS automation,\" \"abandoned cart text,\" \"post-purchase SMS,\" \"Klaviyo SMS,\" \"Postscript,\" \"Attentive,\" \"Twilio,\" \"A2P 10DLC,\" \"TCPA,\" \"SMS compliance,\" \"short code,\" \"toll-free SMS,\" \"MMS campaign,\" \"should I do SMS,\" \"SMS vs email,\" \"WhatsApp marketing,\" \"WhatsApp Business API,\" \"WhatsApp templates,\" or \"click-to-WhatsApp.\" For email sequences, see emails. For SMS copy framing, see copywriting. For opt-in popups that capture phone numbers, see popups.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsms\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7AG4WJ9EDSECNTQN0FEAYCQ","site-architecture","When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions \"sitemap,\" \"site map,\" \"visual sitemap,\" \"site structure,\" \"page hierarchy,\" \"information architecture,\" \"IA,\" \"navigation design,\" \"URL structure,\" \"breadcrumbs,\" \"internal linking strategy,\" \"website planning,\" \"what pages do I need,\" \"how should I organize my site,\" \"site navigation,\" \"which website builder should I use,\" \"migrate my website,\" or \"add a blog to my existing site.\" Use this whenever someone is planning what pages a website should have, how they connect, and where to build them. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsite-architecture\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7AG4MH58GRMSHC0TADAWQ69","signup","When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions \"signup conversions,\" \"registration friction,\" \"signup form optimization,\" \"free trial signup,\" \"reduce signup dropoff,\" \"account creation flow,\" \"people aren't signing up,\" \"signup abandonment,\" \"trial conversion rate,\" \"nobody completes registration,\" \"too many steps to sign up,\" or \"simplify our signup.\" Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsignup\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7AG4CGGH35KYDFHYSS1BQZ5","seo-audit","When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions \"SEO audit,\" \"technical SEO,\" \"why am I not ranking,\" \"SEO issues,\" \"on-page SEO,\" \"meta tags review,\" \"SEO health check,\" \"my traffic dropped,\" \"lost rankings,\" \"not showing up in Google,\" \"site isn't ranking,\" \"Google update hit me,\" \"page speed,\" \"core web vitals,\" \"crawl errors,\" \"indexing issues,\" \"stuck on page 2,\" \"striking distance keywords,\" \"title tag rewrite,\" \"low CTR,\" \"local SEO,\" \"Google Business Profile,\" or \"map pack.\" Use this even if the user just says something vague like \"my SEO is bad\" or \"help with SEO\" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fseo-audit\u002FSKILL.md",[],[]]