[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AEEWP7VECRRZYC79JSBDRQ":3,"skill-same:01M7AEEWP7VECRRZYC79JSBDRQ":73},{"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},"01M7AEEWP7VECRRZYC79JSBDRQ","trend-spotter",null,"Use when the user asks to \"find trending topics\", \"what trends should my brand jump on\", or \"time a campaign around a cultural moment\"; produces a ranked trend report with brand-fit scores, format calls (rising\u002Fpeak\u002Fdeclining), a cultural calendar, and go\u002Fskip recommendations. Not for finding the creators to run those trends — use influencer-discovery; not for building the brand posting calendar from a go verdict — use social-calendar-builder. 热点趋势洞察\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\u002Ftrend-spotter\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: trend-spotter\nslug: trend-spotter\ndisplayName: \"Trend Spotter · 趋势侦察\"\nsummary: \"排名化趋势报告:品牌契合评分、rising\u002Fpeak\u002Fdeclining 判断与 go\u002Fskip 建议\"\ndescription: 'Use when the user asks to \"find trending topics\", \"what trends should my brand jump on\", or \"time a campaign around a cultural moment\"; produces a ranked trend report with brand-fit scores, format calls (rising\u002Fpeak\u002Fdeclining), a cultural calendar, and go\u002Fskip recommendations. Not for finding the creators to run those trends — use influencer-discovery; not for building the brand posting calendar from a go verdict — use social-calendar-builder. 热点趋势洞察\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: \"Use when planning campaign timing and themes, deciding whether to join a hashtag, sound, or challenge, scouting trending content formats on a platform, mapping upcoming cultural moments to lead times, or checking which trends competitors have adopted or missed. Auto-activate when the request is about what is trending, what to post around, or when to act.\"\nargument-hint: \"\u003Cbrand or industry> [platform] [time horizon]\"\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# Trend Spotter\n\nThis skill helps you identify and capitalize on trends that matter to your audience. It monitors social conversations, emerging topics, viral content formats, and cultural moments to inform influencer campaign timing and content strategy.\n\n## Quick Start\n\nShortest invocation:\n\n```\nWhat trends are relevant for [brand\u002Findustry] right now?\n```\n\nCommon scenario — analyze one specific trend before committing:\n\n```\nShould [brand] participate in [trend\u002Fchallenge]? Score the brand fit and give a go\u002Fskip call.\n```\n\n## Skill Contract\n\n- **Reads**: brand\u002Findustry, target platforms, audience, geographic focus, time horizon, content categories; prior audience and niche findings from `memory\u002Finfluencer\u002F` if present.\n- **Writes**: return the trend report inline by default; save it to `memory\u002Finfluencer\u002Ftrend-spotter\u002FYYYY-MM-DD-\u003Ctopic>.md` only with exact authorization for that WARM path.\n- **Promotes**: only with separate exact authorization, promote durable facts (top trends to act on now, trends to avoid, next review date) to `memory\u002Fhot-cache.md`.\n- **Done when**:\n  1. Every named current trend, volume\u002Fgrowth\u002Fstatus claim, cultural moment, and competitor-adoption claim has a dated source ref plus the requested platform, geography, observation window, metric definition, and momentum comparison.\n  2. Each candidate with complete current evidence for that exact scope has a brand-fit score and a go \u002F caution \u002F skip call; RSS\u002Ftitle overlap alone remains a `Proxy candidate` with `score_state: NOT_SCORED`.\n  3. The report names the top 3 trends, watch list, and avoid list only when current evidence supports them; otherwise it returns `NEEDS_INPUT` with an exact query\u002Fcollection plan.\n- **Primary next skill**: [influencer-discovery](..\u002Finfluencer-discovery\u002FSKILL.md) — find the creators who can execute the chosen trends.\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\nThe intake and query plan work with no live integration. A report about what is current does not: it requires dated user-supplied evidence, a public fetch, or a live connector result for the requested platform, geography, and horizon. Brand inputs alone support search terms and evaluation criteria, not trend names, counts, growth, rising\u002Fpeak\u002Fdeclining calls, or go\u002Fskip recommendations. Without current evidence, return `NEEDS_INPUT` and the exact queries\u002Ffields to collect. Where a tool supplies the read, use a `~~` connector placeholder:\n\n- `~~social platform analytics` — trending hashtags, sounds, and view counts per platform.\n- `~~trend database` — emerging topics, challenge participation, and growth rates.\n- `~~social listening` — cultural conversations and sentiment around a topic.\n- `~~competitor tracking` — which trends rival brands have adopted and how they performed.\n\nNo connector is required to produce a useful **query plan**. A named current-trend report requires the source records above. See [CONNECTORS.md](..\u002F..\u002F..\u002FCONNECTORS.md) for the free\u002Fkeyless recipe per category.\n\nFor a keyless way to discover topics worth measuring, run the multi-source candidate scout — Google Trends RSS + Hacker News + Reddit + YouTube upload titles via the bundled stdlib `rss_monitor.py` (no new dependency): [references\u002Ftrend-scout-recipe.md](references\u002Ftrend-scout-recipe.md). RSS\u002Ftitle overlap is only a `Proxy candidate` and stays `NOT_SCORED`; it does not establish a platform trend, view-count outlier, lifecycle state, or act-now recommendation. This is the Tier-1 candidate recipe behind `~~trend database` (Google Trends RSS).\n\n**Keyless news pulse (Tavily)**: `python3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fconnectors\u002Ftavily.py\" search \"\u003Cvertical or candidate trend>\" --topic news --time-range w --limit 10` adds recency-filtered discovery refs. Agreement with an RSS title may raise query priority, but it remains a `Proxy candidate\u002FNOT_SCORED`; news overlap does not prove momentum on TikTok, Reels, YouTube, or another requested platform.\n\n**Keyless source-specific sharpeners**: `python3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fconnectors\u002Fpageviews.py\" \"\u003CTopic_Article>\" --granularity daily --days 30` measures Wikipedia page attention, and the Hacker News Algolia API (`https:\u002F\u002Fhn.algolia.com\u002Fapi\u002Fv1\u002Fsearch?query=\u003Ctopic>`, keyless) measures HN points\u002Fcomments. Those values are Measured only for their named source and window. Treat them as Proxy for a different requested platform; require dated momentum from the exact platform\u002Fgeography\u002Fwindow before any rising \u002F peak \u002F declining or act-now call.\n\n## Instructions\n\nWhen a user requests trend analysis, run these steps. Each step has a fill-in template in [references\u002Ftemplates.md](references\u002Ftemplates.md) — copy the matching block and populate it.\n\n1. **Define trend parameters** — capture brand\u002Findustry, platforms, audience, geographic focus, time horizon, and content categories. (Template: Step 1.)\n2. **Qualify current evidence** — for every candidate topic, hashtag, audio, challenge, format, cultural moment, and competitor observation, retain source ref, observed\u002Fretrieved date, measurement window, platform\u002Fgeography, metric definition, current value, and comparable prior value. RSS\u002Ftitle overlap alone stays `Proxy candidate\u002FNOT_SCORED`. Missing current evidence stops factual output and yields the query plan. (Template: Step 2.)\n3. **Analyze content format trends** — list rising\u002Fpeak\u002Fdeclining formats only from a dated momentum series for the exact requested platform\u002Fgeography\u002Fwindow; label explanations as observed association or hypothesis, never unsupported causation. (Template: Step 3.)\n4. **Track cultural moments** — source dates and current conversation\u002Fsentiment claims; otherwise return calendar\u002Fsearch fields as `TBD`. (Template: Step 4.)\n5. **Assess trend relevance** — score only evidence-backed candidates on audience alignment, brand value fit, content adaptability, risk, and timing (X\u002F25). Unsupported candidates remain `NOT_SCORED` with no go\u002Fcaution\u002Fskip call. (Template: Step 5.)\n6. **Monitor competitor trend adoption** — require dated post\u002Fcampaign evidence; do not infer adoption, performance, gaps, or overuse from general brand knowledge. (Template: Step 6.)\n7. **Generate the trend report** — fill top-3-act-now, watch, avoid, timed action, format, and hashtag blocks only for candidates that pass the complete current-evidence gate for the exact platform\u002Fgeography\u002Fwindow; otherwise leave those blocks `TBD` and return `NEEDS_INPUT` with the collection plan. Return it inline; offer the exact WARM save path, then ask separately before any HOT promotion. (Template: Step 7.)\n\nFor repeatable monitoring, return any proposed ledger write as an inline plan first. Do not run `ledger.py record` until the user gives a separate exact authorization naming the normalized ledger path, the `record` operation, and the exact source\u002Ftopic\u002Fplatform\u002Fgeography\u002Fwindow scope. Report-save or HOT-promotion authorization never covers that write.\n\n## Example\n\n**User**: \"What TikTok trends should a fitness brand run right now?\"\n\nOutput is `NEEDS_INPUT` because the prompt supplies no dated TikTok evidence. It returns platform\u002Fgeography\u002Fwindow-specific queries for topic, hashtag, sound, format, safety, and competitor-adoption records, plus the fields `source_ref`, `observed_at`, and `measurement_window`. It names no trend, count, status, hashtag, format winner, or this-week action until those records arrive. Full version: [references\u002Ftemplates.md](references\u002Ftemplates.md#extended-example--tiktok-fitness-trends).\n\n## Reference Materials\n\n- [references\u002Ftemplates.md](references\u002Ftemplates.md) — fill-in templates for every step, the extended worked example, and execution tips.\n\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) — HOT\u002FWARM\u002FCOLD memory tiers and save paths.\n- [CONNECTORS.md](..\u002F..\u002F..\u002FCONNECTORS.md) — free\u002Fkeyless data recipe per connector category.\n- STAR benchmark scoring at [references\u002Fstar-benchmark.md](..\u002F..\u002F..\u002Freferences\u002Fstar-benchmark.md) — for grading trend-driven creative output downstream.\n- Siblings in the scout phase: [audience-mapper](..\u002Faudience-mapper\u002FSKILL.md), [influencer-discovery](..\u002Finfluencer-discovery\u002FSKILL.md), [fit-scorer](..\u002Ffit-scorer\u002FSKILL.md).\n\n## Next Best Skill\n\n- **Primary**: [influencer-discovery](..\u002Finfluencer-discovery\u002FSKILL.md) — turn the chosen trends into a shortlist of creators who can execute them.\n- **Alternate**: [audience-mapper](..\u002Faudience-mapper\u002FSKILL.md) — confirm which trends actually resonate with your audience before committing.\n- **Alternate**: [fit-scorer](..\u002Ffit-scorer\u002FSKILL.md) — score which creators fit the chosen trends and the brand before committing.\n\nTermination: keep a visited-set of skills invoked this session. If the primary next skill was already run this turn, stop and report the chain complete rather than re-invoking. Max handoff depth is 3; once reached, summarize and return control to the user.\n","# Trend Spotter\n\nThis skill helps you identify and capitalize on trends that matter to your audience. It monitors social conversations, emerging topics, viral content formats, and cultural moments to inform influencer campaign timing and content strategy.\n\n## Quick Start\n\nShortest invocation:\n\n```\nWhat trends are relevant for [brand\u002Findustry] right now?\n```\n\nCommon scenario — analyze one specific trend before committing:\n\n```\nShould [brand] participate in [trend\u002Fchallenge]? Score the brand fit and give a go\u002Fskip call.\n```\n\n## Skill Contract\n\n- **Reads**: brand\u002Findustry, target platforms, audience, geographic focus, time horizon, content categories; prior audience and niche findings from `memory\u002Finfluencer\u002F` if present.\n- **Writes**: return the trend report inline by default; save it to `memory\u002Finfluencer\u002Ftrend-spotter\u002FYYYY-MM-DD-\u003Ctopic>.md` only with exact authorization for that WARM path.\n- **Promotes**: only with separate exact authorization, promote durable facts (top trends to act on now, trends to avoid, next review date) to `memory\u002Fhot-cache.md`.\n- **Done when**:\n  1. Every named current trend, volume\u002Fgrowth\u002Fstatus claim, cultural moment, and competitor-adoption claim has a dated source ref plus the requested platform, geography, observation window, metric definition, and momentum comparison.\n  2. Each candidate with complete current evidence for that exact scope has a brand-fit score and a go \u002F caution \u002F skip call; RSS\u002Ftitle overlap alone remains a `Proxy candidate` with `score_state: NOT_SCORED`.\n  3. The report names the top 3 trends, watch list, and avoid list only when current evidence supports them; otherwise it returns `NEEDS_INPUT` with an exact query\u002Fcollection plan.\n- **Primary next skill**: [influencer-discovery](..\u002Finfluencer-discovery\u002FSKILL.md) — find the creators who can execute the chosen trends.\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\nThe intake and query plan work with no live integration. A report about what is current does not: it requires dated user-supplied evidence, a public fetch, or a live connector result for the requested platform, geography, and horizon. Brand inputs alone support search terms and evaluation criteria, not trend names, counts, growth, rising\u002Fpeak\u002Fdeclining calls, or go\u002Fskip recommendations. Without current evidence, return `NEEDS_INPUT` and the exact queries\u002Ffields to collect. Where a tool supplies the read, use a `~~` connector placeholder:\n\n- `~~social platform analytics` — trending hashtags, sounds, and view counts per platform.\n- `~~trend database` — emerging topics, challenge participation, and growth rates.\n- `~~social listening` — cultural conversations and sentiment around a topic.\n- `~~competitor tracking` — which trends rival brands have adopted and how they performed.\n\nNo connector is required to produce a useful **query plan**. A named current-trend report requires the source records above. See [CONNECTORS.md](..\u002F..\u002F..\u002FCONNECTORS.md) for the free\u002Fkeyless recipe per category.\n\nFor a keyless way to discover topics worth measuring, run the multi-source candidate scout — Google Trends RSS + Hacker News + Reddit + YouTube upload titles via the bundled stdlib `rss_monitor.py` (no new dependency): [references\u002Ftrend-scout-recipe.md](references\u002Ftrend-scout-recipe.md). RSS\u002Ftitle overlap is only a `Proxy candidate` and stays `NOT_SCORED`; it does not establish a platform trend, view-count outlier, lifecycle state, or act-now recommendation. This is the Tier-1 candidate recipe behind `~~trend database` (Google Trends RSS).\n\n**Keyless news pulse (Tavily)**: `python3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fconnectors\u002Ftavily.py\" search \"\u003Cvertical or candidate trend>\" --topic news --time-range w --limit 10` adds recency-filtered discovery refs. Agreement with an RSS title may raise query priority, but it remains a `Proxy candidate\u002FNOT_SCORED`; news overlap does not prove momentum on TikTok, Reels, YouTube, or another requested platform.\n\n**Keyless source-specific sharpeners**: `python3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fconnectors\u002Fpageviews.py\" \"\u003CTopic_Article>\" --granularity daily --days 30` measures Wikipedia page attention, and the Hacker News Algolia API (`https:\u002F\u002Fhn.algolia.com\u002Fapi\u002Fv1\u002Fsearch?query=\u003Ctopic>`, keyless) measures HN points\u002Fcomments. Those values are Measured only for their named source and window. Treat them as Proxy for a different requested platform; require dated momentum from the exact platform\u002Fgeography\u002Fwindow before any rising \u002F peak \u002F declining or act-now call.\n\n## Instructions\n\nWhen a user requests trend analysis, run these steps. Each step has a fill-in template in [references\u002Ftemplates.md](references\u002Ftemplates.md) — copy the matching block and populate it.\n\n1. **Define trend parameters** — capture brand\u002Findustry, platforms, audience, geographic focus, time horizon, and content categories. (Template: Step 1.)\n2. **Qualify current evidence** — for every candidate topic, hashtag, audio, challenge, format, cultural moment, and competitor observation, retain source ref, observed\u002Fretrieved date, measurement window, platform\u002Fgeography, metric definition, current value, and comparable prior value. RSS\u002Ftitle overlap alone stays `Proxy candidate\u002FNOT_SCORED`. Missing current evidence stops factual output and yields the query plan. (Template: Step 2.)\n3. **Analyze content format trends** — list rising\u002Fpeak\u002Fdeclining formats only from a dated momentum series for the exact requested platform\u002Fgeography\u002Fwindow; label explanations as observed association or hypothesis, never unsupported causation. (Template: Step 3.)\n4. **Track cultural moments** — source dates and current conversation\u002Fsentiment claims; otherwise return calendar\u002Fsearch fields as `TBD`. (Template: Step 4.)\n5. **Assess trend relevance** — score only evidence-backed candidates on audience alignment, brand value fit, content adaptability, risk, and timing (X\u002F25). Unsupported candidates remain `NOT_SCORED` with no go\u002Fcaution\u002Fskip call. (Template: Step 5.)\n6. **Monitor competitor trend adoption** — require dated post\u002Fcampaign evidence; do not infer adoption, performance, gaps, or overuse from general brand knowledge. (Template: Step 6.)\n7. **Generate the trend report** — fill top-3-act-now, watch, avoid, timed action, format, and hashtag blocks only for candidates that pass the complete current-evidence gate for the exact platform\u002Fgeography\u002Fwindow; otherwise leave those blocks `TBD` and return `NEEDS_INPUT` with the collection plan. Return it inline; offer the exact WARM save path, then ask separately before any HOT promotion. (Template: Step 7.)\n\nFor repeatable monitoring, return any proposed ledger write as an inline plan first. Do not run `ledger.py record` until the user gives a separate exact authorization naming the normalized ledger path, the `record` operation, and the exact source\u002Ftopic\u002Fplatform\u002Fgeography\u002Fwindow scope. Report-save or HOT-promotion authorization never covers that write.\n\n## Example\n\n**User**: \"What TikTok trends should a fitness brand run right now?\"\n\nOutput is `NEEDS_INPUT` because the prompt supplies no dated TikTok evidence. It returns platform\u002Fgeography\u002Fwindow-specific queries for topic, hashtag, sound, format, safety, and competitor-adoption records, plus the fields `source_ref`, `observed_at`, and `measurement_window`. It names no trend, count, status, hashtag, format winner, or this-week action until those records arrive. Full version: [references\u002Ftemplates.md](references\u002Ftemplates.md#extended-example--tiktok-fitness-trends).\n\n## Reference Materials\n\n- [references\u002Ftemplates.md](references\u002Ftemplates.md) — fill-in templates for every step, the extended worked example, and execution tips.\n\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) — HOT\u002FWARM\u002FCOLD memory tiers and save paths.\n- [CONNECTORS.md](..\u002F..\u002F..\u002FCONNECTORS.md) — free\u002Fkeyless data recipe per connector category.\n- STAR benchmark scoring at [references\u002Fstar-benchmark.md](..\u002F..\u002F..\u002Freferences\u002Fstar-benchmark.md) — for grading trend-driven creative output downstream.\n- Siblings in the scout phase: [audience-mapper](..\u002Faudience-mapper\u002FSKILL.md), [influencer-discovery](..\u002Finfluencer-discovery\u002FSKILL.md), [fit-scorer](..\u002Ffit-scorer\u002FSKILL.md).\n\n## Next Best Skill\n\n- **Primary**: [influencer-discovery](..\u002Finfluencer-discovery\u002FSKILL.md) — turn the chosen trends into a shortlist of creators who can execute them.\n- **Alternate**: [audience-mapper](..\u002Faudience-mapper\u002FSKILL.md) — confirm which trends actually resonate with your audience before committing.\n- **Alternate**: [fit-scorer](..\u002Ffit-scorer\u002FSKILL.md) — score which creators fit the chosen trends and the brand before committing.\n\nTermination: keep a visited-set of skills invoked this session. If the primary next skill was already run this turn, stop and report the chain complete rather than re-invoking. Max handoff depth is 3; once reached, summarize and return control to the user.\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},"排名化趋势报告:品牌契合评分、rising\u002Fpeak\u002Fdeclining 判断与 go\u002Fskip 建议","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","Trend Spotter · 趋势侦察","Use when planning campaign timing and themes, deciding whether to join a hashtag, sound, or challenge, scouting trending content formats on a platform, mapping upcoming cultural moments to lead times, or checking which trends competitors have adopted or missed. Auto-activate when the request is about what is trending, what to post around, or when to act.","\u003Cbrand or industry> [platform] [time horizon]","Claude Code and compatible agent-skill hosts","main","ad108f7eb3f6764136d02fb875772ebb34f54078","upstreams\u002Fsource-a\u002Finfluencer\u002Fscout\u002Ftrend-spotter",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 trend-spotter",{"tool":55,"command":56},"bunx","bunx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill trend-spotter",{"tool":58,"command":59},"pnpm","pnpm dlx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill trend-spotter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Finfluencer\u002Fscout\u002Ftrend-spotter\u002FSKILL.md",true,[63,69],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Ftemplates.md","REFERENCE","参考文档",11673,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Finfluencer\u002Fscout\u002Ftrend-spotter\u002Freferences\u002Ftemplates.md",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Ftrend-scout-recipe.md",4557,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Finfluencer\u002Fscout\u002Ftrend-spotter\u002Freferences\u002Ftrend-scout-recipe.md",[74,81,88,95,102,109],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"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",[],[]]