[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7511FDP513M0BCBWWEEHS93":3,"skill-same:01M7511FDP513M0BCBWWEEHS93":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":31,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7511FDP513M0BCBWWEEHS93","media-monitor",null,"Turns raw brand mentions across news and social into an actionable comms picture - precise monitoring queries, grounded sentiment classification, numeric alert thresholds for narrative shifts, severity triage, and a daily digest a comms team can act on within minutes. Use when someone asks \"set up brand monitoring\", \"are people talking about us and how\", \"is this negative story spreading\", \"design our mention alert thresholds\", or \"write our daily media digest\". Do NOT use for spotting broader market or cultural trends beyond a tracked brand - use trend-analysis instead - or for gathering intelligence on competitors' moves - use competitive-intelligence instead.","SkillMedev\u002Fskills","SkillMedev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F298078254?v=4","01M74ZSGTQ918CB0VXW4EG3RMX","SkillMe","01M74ZSGVBT497NA95CBT8JTY4",25,"MIT","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmedia-monitor\u002FSKILL.md",[],[],"2026-11-11 18:11:01",false,"---\nname: media-monitor\ndescription: Turns raw brand mentions across news and social into an actionable comms picture - precise monitoring queries, grounded sentiment classification, numeric alert thresholds for narrative shifts, severity triage, and a daily digest a comms team can act on within minutes. Use when someone asks \"set up brand monitoring\", \"are people talking about us and how\", \"is this negative story spreading\", \"design our mention alert thresholds\", or \"write our daily media digest\". Do NOT use for spotting broader market or cultural trends beyond a tracked brand - use trend-analysis instead - or for gathering intelligence on competitors' moves - use competitive-intelligence instead.\nmetadata:\n  title: \"Media Monitor\"\n---\n\n# Media Monitor\n\nRaw mention feeds are noise; the costly failures are symmetric - missing the forum post that becomes a national story eighteen hours later, and escalating a comms fire drill over three sarcastic tweets. This skill turns mentions into an actionable picture: queries precise enough to trust, sentiment grounded in text, numeric thresholds that separate shift from chatter, and a digest that lets a comms team act within minutes.\n\n## Operating procedure\n\nQuery design comes first because every downstream number - volume, sentiment, spike detection - inherits the query's precision; a noisy query makes every alert a false one.\n\n### Step 1: Gather inputs\n\n1. Entities to track: brand names, products, executives, competitors, campaign hashtags.\n2. Known ambiguities: homonyms, generic words in the name, celebrity name collisions.\n3. Sources in scope and any platform access limits.\n4. The team's alert appetite: who gets paged, and how many false alarms per week they will tolerate (default: tune for under 2).\n5. Baseline history if it exists - 30 days of mention volume; without it, run 7 days silent to establish the baseline before alerting.\n\n### Step 2: Design the queries\n\n- Include common misspellings, abbreviations, and acronyms for every entity.\n- Exclude ambiguous homonyms with negative keywords, and iterate until precision holds.\n\nBad: `Apple` - drowns in fruit, recipes, and idioms; every metric downstream is garbage.\nGood: `(\"Apple\" OR \"AAPL\" OR \"@Apple\") AND (iPhone OR Mac OR Cupertino OR earnings) -fruit -pie -recipe -crumble`\n\n- Tier the sources: news (wire, national, trade), social (X, Reddit, forums), and owned channels. Weight by reach and credibility - one wire-service story outweighs fifty anonymous forum posts for severity, but the forum is where stories start, so it is watched, not ignored.\n- Test each query on a sample of 50 recent hits; require at least 90% of results to be genuinely about the entity before the query goes live. Below that, alerts will be ignored within a week.\n\n### Step 3: Classify each mention\n\nCapture for every item: source, date, reach estimate, sentiment, and topic\u002Ftheme. Sentiment rules:\n\n- Three labels - positive \u002F neutral \u002F negative - plus a one-line rationale quoting the text.\n- Ground sentiment in the body text, never the headline alone; headlines are written for clicks, not accuracy.\n- Mark low-confidence calls explicitly, especially sarcasm and irony - an over-confident sentiment score is worse than an honest \"unclear.\"\n\n### Step 4: Detect narrative shifts with numeric thresholds\n\nA single negative post is noise; a shift is signal. Alert on:\n\n- Volume spike: mentions exceeding the rolling 7-day baseline by 2x or more. Use the rolling baseline, not a fixed number, so growth and seasonality do not fire false alarms.\n- Sentiment swing: net sentiment (positive minus negative, as a share of total) moving more than ~20 points period-over-period.\n- New framings: keywords or phrases prominent this period that were absent last period - the earliest shift signal, and the one volume metrics miss.\n- Source migration: a story jumping tiers, forum to trade press to national. Migration is the strongest predictor that a story is about to get bigger; page on it even when volume is still small.\n\n### Step 5: Triage severity\n\n- Critical: legal or safety claim, an executive named, volume accelerating, credible source or migrating upward. Page now.\n- Watch: rising volume, mixed sentiment, contained to one platform. Recheck within hours, note in the digest.\n- Routine: normal chatter, stable sentiment. Digest only.\n\n### Step 6: Report\n\nDeliver the daily digest in this order:\n\n1. Headline numbers: total mentions, net sentiment, both versus prior period.\n2. Top 3 stories driving the conversation, each with reach and sentiment.\n3. Narrative shifts detected, with the threshold that tripped and why it matters.\n4. Recommended action per critical item: respond \u002F monitor \u002F escalate.\n\nWhen citing any mention, link the primary source and quote verbatim - never paraphrase a quote in a way that changes its meaning.\n\n## Worked artifact: daily digest template\n\n```\nMEDIA DIGEST - [FILL: brand] - [FILL: date]\n\nHEADLINE NUMBERS\n  Mentions: [FILL]  (7-day baseline: [FILL], ratio: [FILL]x)\n  Net sentiment: [FILL] pts  (prior period: [FILL], change: [FILL] pts)\n\nTOP 3 STORIES\n  1. [FILL: story] - reach [FILL], sentiment [FILL], link [FILL]\n  2. [FILL]\n  3. [FILL]\n\nSHIFTS DETECTED\n  [FILL: e.g., \"volume 2.4x baseline, driven by \u003Cframing>; migrated from\n   r\u002F\u003Csub> to \u003Ctrade outlet> at 14:00 - migration threshold tripped\"]\n\nACTIONS\n  CRITICAL: [FILL: item] -> [respond \u002F monitor \u002F escalate] - owner [FILL]\n  WATCH:    [FILL: item] -> recheck at [FILL: time]\n```\n\n## Deliverable\n\nProduce a monitoring package: the query set per entity with negative keywords and the 90% precision test result, the source tiers with weights, the alert thresholds (2x volume, 20-point sentiment, new-framing and migration triggers) tuned to the team's false-alarm tolerance, and the daily digest in the template above with a recommended action per critical item.\n\n## Do NOT\n\n- Do not alert off a raw mention count - always ratio against the rolling 7-day baseline, or growth guarantees permanent false alarms.\n- Do not score sentiment from headlines; headlines are engineered for clicks and routinely invert the body's tone.\n- Do not treat organic and coordinated activity as one signal - flag suspicious clusters (identical phrasing, synchronized timing, young accounts) and report them separately.\n- Do not infer causation from a single correlated spike; note the correlation and keep watching.\n- Do not paraphrase quotes; verbatim with a link, every time.\n- Do not dox individuals - aggregate patterns, respect platform terms and privacy.\n- Do not ignore small-volume stories that are migrating up source tiers; migration outranks volume as a warning sign.\n\n## Quality bar\n\n- Every live query passed the 90% precision sample test, and the test is recorded.\n- Every sentiment label carries a text-grounded rationale, with low-confidence calls marked.\n- Every alert in the digest names the numeric threshold that tripped it.\n- Every critical item has a recommended action and an owner.\n- Bot-suspect clusters are flagged and excluded from the organic numbers.\n","# Media Monitor\n\nRaw mention feeds are noise; the costly failures are symmetric - missing the forum post that becomes a national story eighteen hours later, and escalating a comms fire drill over three sarcastic tweets. This skill turns mentions into an actionable picture: queries precise enough to trust, sentiment grounded in text, numeric thresholds that separate shift from chatter, and a digest that lets a comms team act within minutes.\n\n## Operating procedure\n\nQuery design comes first because every downstream number - volume, sentiment, spike detection - inherits the query's precision; a noisy query makes every alert a false one.\n\n### Step 1: Gather inputs\n\n1. Entities to track: brand names, products, executives, competitors, campaign hashtags.\n2. Known ambiguities: homonyms, generic words in the name, celebrity name collisions.\n3. Sources in scope and any platform access limits.\n4. The team's alert appetite: who gets paged, and how many false alarms per week they will tolerate (default: tune for under 2).\n5. Baseline history if it exists - 30 days of mention volume; without it, run 7 days silent to establish the baseline before alerting.\n\n### Step 2: Design the queries\n\n- Include common misspellings, abbreviations, and acronyms for every entity.\n- Exclude ambiguous homonyms with negative keywords, and iterate until precision holds.\n\nBad: `Apple` - drowns in fruit, recipes, and idioms; every metric downstream is garbage.\nGood: `(\"Apple\" OR \"AAPL\" OR \"@Apple\") AND (iPhone OR Mac OR Cupertino OR earnings) -fruit -pie -recipe -crumble`\n\n- Tier the sources: news (wire, national, trade), social (X, Reddit, forums), and owned channels. Weight by reach and credibility - one wire-service story outweighs fifty anonymous forum posts for severity, but the forum is where stories start, so it is watched, not ignored.\n- Test each query on a sample of 50 recent hits; require at least 90% of results to be genuinely about the entity before the query goes live. Below that, alerts will be ignored within a week.\n\n### Step 3: Classify each mention\n\nCapture for every item: source, date, reach estimate, sentiment, and topic\u002Ftheme. Sentiment rules:\n\n- Three labels - positive \u002F neutral \u002F negative - plus a one-line rationale quoting the text.\n- Ground sentiment in the body text, never the headline alone; headlines are written for clicks, not accuracy.\n- Mark low-confidence calls explicitly, especially sarcasm and irony - an over-confident sentiment score is worse than an honest \"unclear.\"\n\n### Step 4: Detect narrative shifts with numeric thresholds\n\nA single negative post is noise; a shift is signal. Alert on:\n\n- Volume spike: mentions exceeding the rolling 7-day baseline by 2x or more. Use the rolling baseline, not a fixed number, so growth and seasonality do not fire false alarms.\n- Sentiment swing: net sentiment (positive minus negative, as a share of total) moving more than ~20 points period-over-period.\n- New framings: keywords or phrases prominent this period that were absent last period - the earliest shift signal, and the one volume metrics miss.\n- Source migration: a story jumping tiers, forum to trade press to national. Migration is the strongest predictor that a story is about to get bigger; page on it even when volume is still small.\n\n### Step 5: Triage severity\n\n- Critical: legal or safety claim, an executive named, volume accelerating, credible source or migrating upward. Page now.\n- Watch: rising volume, mixed sentiment, contained to one platform. Recheck within hours, note in the digest.\n- Routine: normal chatter, stable sentiment. Digest only.\n\n### Step 6: Report\n\nDeliver the daily digest in this order:\n\n1. Headline numbers: total mentions, net sentiment, both versus prior period.\n2. Top 3 stories driving the conversation, each with reach and sentiment.\n3. Narrative shifts detected, with the threshold that tripped and why it matters.\n4. Recommended action per critical item: respond \u002F monitor \u002F escalate.\n\nWhen citing any mention, link the primary source and quote verbatim - never paraphrase a quote in a way that changes its meaning.\n\n## Worked artifact: daily digest template\n\n```\nMEDIA DIGEST - [FILL: brand] - [FILL: date]\n\nHEADLINE NUMBERS\n  Mentions: [FILL]  (7-day baseline: [FILL], ratio: [FILL]x)\n  Net sentiment: [FILL] pts  (prior period: [FILL], change: [FILL] pts)\n\nTOP 3 STORIES\n  1. [FILL: story] - reach [FILL], sentiment [FILL], link [FILL]\n  2. [FILL]\n  3. [FILL]\n\nSHIFTS DETECTED\n  [FILL: e.g., \"volume 2.4x baseline, driven by \u003Cframing>; migrated from\n   r\u002F\u003Csub> to \u003Ctrade outlet> at 14:00 - migration threshold tripped\"]\n\nACTIONS\n  CRITICAL: [FILL: item] -> [respond \u002F monitor \u002F escalate] - owner [FILL]\n  WATCH:    [FILL: item] -> recheck at [FILL: time]\n```\n\n## Deliverable\n\nProduce a monitoring package: the query set per entity with negative keywords and the 90% precision test result, the source tiers with weights, the alert thresholds (2x volume, 20-point sentiment, new-framing and migration triggers) tuned to the team's false-alarm tolerance, and the daily digest in the template above with a recommended action per critical item.\n\n## Do NOT\n\n- Do not alert off a raw mention count - always ratio against the rolling 7-day baseline, or growth guarantees permanent false alarms.\n- Do not score sentiment from headlines; headlines are engineered for clicks and routinely invert the body's tone.\n- Do not treat organic and coordinated activity as one signal - flag suspicious clusters (identical phrasing, synchronized timing, young accounts) and report them separately.\n- Do not infer causation from a single correlated spike; note the correlation and keep watching.\n- Do not paraphrase quotes; verbatim with a link, every time.\n- Do not dox individuals - aggregate patterns, respect platform terms and privacy.\n- Do not ignore small-volume stories that are migrating up source tiers; migration outranks volume as a warning sign.\n\n## Quality bar\n\n- Every live query passed the 90% precision sample test, and the test is recorded.\n- Every sentiment label carries a text-grounded rationale, with low-confidence calls marked.\n- Every alert in the digest names the numeric threshold that tripped it.\n- Every critical item has a recommended action and an owner.\n- Bot-suspect clusters are flagged and excluded from the organic numbers.\n",{"name":5,"metadata":24,"description":7},{"title":25},"Media Monitor","main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Fmedia-monitor",3,"https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills","https:\u002F\u002Fskillme.dev","https:\u002F\u002Fgithub.com\u002FSkillMedev","MCP-native catalog of Claude Agent Skills. Browse, recommend, install, and auto-apply skills in chat. Open source, every skill free and clonable on GitHub.","2026-10-14 03:19:31",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add SkillMedev\u002Fskills --skill media-monitor",{"tool":41,"command":42},"bunx","bunx skills add SkillMedev\u002Fskills --skill media-monitor",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill media-monitor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmedia-monitor\u002FSKILL.md",true,[],[50,58,65,72,79,86],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":57},"01M75271B256DF3FX2VG5VRYEE","zone-2-cardio-plan","Use when someone asks to build a steady-state cardio plan, train an aerobic base or Zone 2, structure easy or endurance weekly cardio, train by heart-rate zones, or improve resting heart rate, VO2, or endurance. Builds a heart-rate-zone aerobic training block with session structure, modality choice, and progression. General fitness guidance, not medical advice. Do NOT use to design a strength or lifting program (use Strength Training Plan), high-intensity interval conditioning, HIIT, or circuits (use Conditioning & HIIT Program), or a mobility\u002Fflexibility routine (use Mobility Routine).","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzone-2-cardio-plan\u002FSKILL.md",[],[],"2026-11-11 18:27:18",{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":57},"01M7526VP1QBBKYBE17S1WR86Y","youtube-script-writer","Writes retention-engineered long-form YouTube scripts on a hook\u002Fbody\u002Fpayoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says \"script my next video\", \"my retention graph dies at the start\", \"tighten this draft\", or \"outline a video on X\". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-writer\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":57},"01M7526P2T0WKMHDXS4Q58237T","win-back-campaign","Designs segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says \"our users went quiet\", \"design a win-back campaign\", \"how do I re-engage lapsed customers\", \"should we email people who haven't logged in for months\", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwin-back-campaign\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":57},"01M7526HF2RCDJ50P93WRZRHVV","wikipedia-style","Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks \"write this like a Wikipedia article\", \"draft a Wikipedia page for this company or person\", \"make this neutral and encyclopedic\", or \"why does my article draft keep getting rejected\". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-driven academic papers, use academic-essay; for verifying claims in existing text, use fact-checker.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwikipedia-style\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":57},"01M7526D43CTGRKGKNQ2GB0KVX","whitepapers","Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks \"write a whitepaper on this topic\", \"turn our research into a lead-gen asset\", \"make this credible enough for executives\", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwhitepapers\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":57},"01M75268423Y3K50SY5WC2NX2G","white-space-analysis","Finds unmet market gaps by ranking jobs-to-be-done on importance versus satisfaction, overlaying them against current solutions and workarounds, and validating that each gap is real, winnable, and worth winning. Use when someone asks \"where are the gaps in this market\", \"what's underserved here\", \"where should we play next\", or is hunting for product, feature, or market-entry opportunities. Do NOT use for profiling competitors and building battle cards - use competitive-intelligence instead; for putting a dollar figure on an identified opportunity - use market-sizing instead; for extracting jobs-to-be-done from raw customer interviews - use jtbd-extractor instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwhite-space-analysis\u002FSKILL.md",[],[]]