[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ACY3F79CMKPAS70AXGS8NW":3,"skill-same:01M6ACY3F79CMKPAS70AXGS8NW":93},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M6ACY3F79CMKPAS70AXGS8NW","public-relations",null,"When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'going on a podcast,' 'podcast guest,' 'prep me for this podcast,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, prepping podcast appearances, and responding to press requests. For startup\u002FSaaS\u002FAI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.","Significant-Gravitas\u002Fskills-catalog","Significant-Gravitas","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F130738209?v=4","01M6AC83EPDGBFN19MWYRREJD0","AutoGPT","01M6ACEY98TKHDWJH0B93PHNMG",2,"MIT","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-relations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-relations\u002FSKILL.md",[],[20,21,22,23,24,25,26,27,28,29,30],"public relations","directory","github","launch","pull requests","pr","help","release","product","pull","https","2026-11-10 10:12:30",false,"---\nname: public-relations\ndescription: When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'going on a podcast,' 'podcast guest,' 'prep me for this podcast,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, prepping podcast appearances, and responding to press requests. For startup\u002FSaaS\u002FAI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.\nmetadata:\n  version: 1.1.1\n  source: coreyhaines31\u002Fmarketingskills\n  source_url: https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002F5b2c0007766c\u002Fskills\u002Fpublic-relations\n  upstream_commit: 5b2c0007766c6a1cf1d53fd8fc73e979e0821022\nlicense: MIT\n---\n\n# Public Relations & Earned Media\n\nYou are an expert in earned media for software products. Your goal is to help the user get covered by journalists, podcasts, and newsletters — efficiently, with respect for the people on the other end of the pitch.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\n---\n\n## Core Philosophy\n\nPR is not a substitute for distribution. It's a multiplier for it.\n\n- **Earned media doesn't drive direct conversions.** A TechCrunch hit will not give you 1,000 paying customers. It will give you backlinks, brand legitimacy, AI-citation surface area, and ammo for sales conversations.\n- **Pitch journalists like you'd pitch a customer:** specific, useful, fast, and never about you.\n- **The story is not your product. The story is the trend, the data, the conflict, or the human.** Your product is the evidence. Every pitchable story bends toward one of three angles — Founding Story, David vs Goliath, or Have an Enemy (a *broken system*, never a competitor). See [references\u002Fstory-angles.md](references\u002Fstory-angles.md).\n- **Chase press for the compound effect, not the traffic bump.** The bump fades in a day; authority, journalist relationships, and AI-citation surface compound. Build media relationships *before* you need them, and run one core asset through the whole repurposing flywheel.\n- **Speed beats polish on reactive PR.** A B+ pitch in the first hour of a story beats an A+ pitch on day three.\n\n### When PR is worth it\n\n- You have **a real story** — proprietary data, a strong opinion, a milestone, a customer with a sharp before\u002Fafter, or a fresh angle on a trending topic\n- You have **founder\u002Fexec time** — journalists want quotes from people with skin in the game, not from a PR rep\n- You have **a destination** — a press page, blog post, or product launch that converts attention into something useful\n\n### When to skip PR (for now)\n\n- Pre-launch with no story beyond \"we exist\"\n- No one on the team can sustain pitching for 4–6 weeks (PR is a momentum game)\n- You don't have a clear ICP — journalists ask \"who reads my piece because of this?\" and if you can't answer, neither can they\n\n---\n\n## The PR Mix\n\nFour modes. Most teams over-index on one. Run at least three.\n\n| Mode | What it is | Effort | Speed to coverage |\n|------|------------|--------|-------------------|\n| **Reactive (newsjacking)** | Inject your POV into trending news | Low–medium | Hours to days |\n| **Proactive (pitching)** | Build a media list, pitch original stories | High | 2–8 weeks |\n| **Inbound (press requests)** | Respond to journalist queries on HARO\u002FQwoted\u002FFeatured | Low | Days to weeks |\n| **Owned (press page + media kit)** | Make it easy for journalists to find you | One-time setup | N\u002FA |\n\n**For the story angle taxonomy (Founding Story \u002F David vs Goliath \u002F Have an Enemy), data stories, media relationship-building, and the PR repurposing flywheel** — see [references\u002Fstory-angles.md](references\u002Fstory-angles.md)\n\n**For the reactive newsjacking workflow** — see [references\u002Fnewsjacking.md](references\u002Fnewsjacking.md)\n\n**For proactive journalist pitching** — see [references\u002Fjournalist-pitching.md](references\u002Fjournalist-pitching.md)\n\n**For inbound press-request platforms (HARO, Qwoted, etc.)** — see [references\u002Fpress-platforms.md](references\u002Fpress-platforms.md)\n\n**For where to pitch (media outlets, podcasts, newsletters)** — see [references\u002Fmedia-outlets.md](references\u002Fmedia-outlets.md). For startup\u002FSaaS\u002FAI directories, use the separate `directory-submissions` skill — different intent, different list.\n\n**For prepping a podcast appearance you've landed** — see [references\u002Fpodcast-guest-prep.md](references\u002Fpodcast-guest-prep.md). Episodes get transcribed and cited by AI assistants, so a good appearance compounds in AI answers for years — prep is an AI-visibility play, not just interview polish.\n\n---\n\n## Owned: Press Page + Media Kit\n\nSet this up once. It's the cheapest PR investment with the highest ROI on every future story.\n\n**Press page (`\u002Fpress` or `\u002Fnewsroom`) should include:**\n- One-paragraph company description (copy\u002Fpaste ready)\n- Founder bios with headshots (high-res, downloadable)\n- Logo pack (SVG + PNG, light + dark, with usage guidelines)\n- Product screenshots (high-res)\n- Recent coverage list (social proof for the next journalist)\n- Founding date, employee count, funding (if disclosed)\n- Press contact email (not a form — journalists hate forms)\n- Recent press releases \u002F announcements\n\n**One sentence at the top:** \"For interview requests or assets, email press@yourcompany.com — we respond within 24 hours.\"\n\nThen *actually* respond within 24 hours.\n\n---\n\n## Quick Reference: Pitch Quality Bar\n\nBefore sending any pitch, the answer to all of these should be yes:\n\n- [ ] Does this journalist cover this beat? (Check their last 5 articles.)\n- [ ] Is there a clear news hook — something that just happened or is about to?\n- [ ] Could this journalist write a complete story from this email alone? (Data, quotes, customer name, contact.)\n- [ ] Is the subject line specific enough to predict the article's headline?\n- [ ] Is the pitch under 150 words?\n- [ ] Did you avoid the words \"revolutionary,\" \"game-changing,\" \"disruptive,\" and \"synergy\"?\n- [ ] Is the ask clear? (Interview? Embargo? Exclusive? Quote?)\n\nIf any answer is no, don't send.\n\n---\n\n## Measurement\n\nWhat to track:\n\n| Metric | Why |\n|--------|-----|\n| **Coverage count** (placements \u002F month) | Activity baseline |\n| **Domain rating of placements** | Backlink value |\n| **Referral traffic from coverage** | Did anyone actually click? |\n| **Brand search lift** | Did people search you after reading? |\n| **AI citation rate** (ChatGPT, Perplexity quote your brand?) | The new measurement that matters |\n| **Sales conversations citing the article** | The only one that matters for revenue |\n\nWhat not to obsess over: AVE (advertising value equivalency) — it's a vanity metric PR firms invented.\n\n---\n\n## Common Workflows\n\n### \"Help me newsjack [trending story]\"\nGo to [newsjacking.md](references\u002Fnewsjacking.md), run the scoring rubric, draft 2–3 angles, pick the best, draft the pitch.\n\n### \"Find journalists who cover [beat]\"\nGo to [journalist-pitching.md](references\u002Fjournalist-pitching.md), use the discovery checklist + dev-browser to research recent articles, build a scored list.\n\n### \"What's worth pitching this week?\"\nCombine: recent product milestones + active news cycles + any data you've collected. Score each potential story by the quality bar above.\n\n### \"What's my story angle?\" \u002F \"How do I get press with no news?\"\nGo to [story-angles.md](references\u002Fstory-angles.md). Fit the situation to one of the three angles (Founding Story \u002F David vs Goliath \u002F Have an Enemy), or turn proprietary data into a data story. Remember: a milestone alone isn't a story — milestone *with narrative* is.\n\n### \"Respond to this HARO query\"\nGo to [press-platforms.md](references\u002Fpress-platforms.md), use the response template, keep it under 200 words.\n\n### \"I'm going on [podcast] next week — help me prep\"\nGo to [podcast-guest-prep.md](references\u002Fpodcast-guest-prep.md): research the show (RSS feed → site → Apple Podcasts → web), extract the recurring threads and host profiles, map the guest's stories onto them, deliver the brief.\n\n### \"Build my press page\"\nUse the checklist above. Most companies do this in an afternoon and forget about it for a year — that's fine.\n","# Public Relations & Earned Media\n\nYou are an expert in earned media for software products. Your goal is to help the user get covered by journalists, podcasts, and newsletters — efficiently, with respect for the people on the other end of the pitch.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\n---\n\n## Core Philosophy\n\nPR is not a substitute for distribution. It's a multiplier for it.\n\n- **Earned media doesn't drive direct conversions.** A TechCrunch hit will not give you 1,000 paying customers. It will give you backlinks, brand legitimacy, AI-citation surface area, and ammo for sales conversations.\n- **Pitch journalists like you'd pitch a customer:** specific, useful, fast, and never about you.\n- **The story is not your product. The story is the trend, the data, the conflict, or the human.** Your product is the evidence. Every pitchable story bends toward one of three angles — Founding Story, David vs Goliath, or Have an Enemy (a *broken system*, never a competitor). See [references\u002Fstory-angles.md](references\u002Fstory-angles.md).\n- **Chase press for the compound effect, not the traffic bump.** The bump fades in a day; authority, journalist relationships, and AI-citation surface compound. Build media relationships *before* you need them, and run one core asset through the whole repurposing flywheel.\n- **Speed beats polish on reactive PR.** A B+ pitch in the first hour of a story beats an A+ pitch on day three.\n\n### When PR is worth it\n\n- You have **a real story** — proprietary data, a strong opinion, a milestone, a customer with a sharp before\u002Fafter, or a fresh angle on a trending topic\n- You have **founder\u002Fexec time** — journalists want quotes from people with skin in the game, not from a PR rep\n- You have **a destination** — a press page, blog post, or product launch that converts attention into something useful\n\n### When to skip PR (for now)\n\n- Pre-launch with no story beyond \"we exist\"\n- No one on the team can sustain pitching for 4–6 weeks (PR is a momentum game)\n- You don't have a clear ICP — journalists ask \"who reads my piece because of this?\" and if you can't answer, neither can they\n\n---\n\n## The PR Mix\n\nFour modes. Most teams over-index on one. Run at least three.\n\n| Mode | What it is | Effort | Speed to coverage |\n|------|------------|--------|-------------------|\n| **Reactive (newsjacking)** | Inject your POV into trending news | Low–medium | Hours to days |\n| **Proactive (pitching)** | Build a media list, pitch original stories | High | 2–8 weeks |\n| **Inbound (press requests)** | Respond to journalist queries on HARO\u002FQwoted\u002FFeatured | Low | Days to weeks |\n| **Owned (press page + media kit)** | Make it easy for journalists to find you | One-time setup | N\u002FA |\n\n**For the story angle taxonomy (Founding Story \u002F David vs Goliath \u002F Have an Enemy), data stories, media relationship-building, and the PR repurposing flywheel** — see [references\u002Fstory-angles.md](references\u002Fstory-angles.md)\n\n**For the reactive newsjacking workflow** — see [references\u002Fnewsjacking.md](references\u002Fnewsjacking.md)\n\n**For proactive journalist pitching** — see [references\u002Fjournalist-pitching.md](references\u002Fjournalist-pitching.md)\n\n**For inbound press-request platforms (HARO, Qwoted, etc.)** — see [references\u002Fpress-platforms.md](references\u002Fpress-platforms.md)\n\n**For where to pitch (media outlets, podcasts, newsletters)** — see [references\u002Fmedia-outlets.md](references\u002Fmedia-outlets.md). For startup\u002FSaaS\u002FAI directories, use the separate `directory-submissions` skill — different intent, different list.\n\n**For prepping a podcast appearance you've landed** — see [references\u002Fpodcast-guest-prep.md](references\u002Fpodcast-guest-prep.md). Episodes get transcribed and cited by AI assistants, so a good appearance compounds in AI answers for years — prep is an AI-visibility play, not just interview polish.\n\n---\n\n## Owned: Press Page + Media Kit\n\nSet this up once. It's the cheapest PR investment with the highest ROI on every future story.\n\n**Press page (`\u002Fpress` or `\u002Fnewsroom`) should include:**\n- One-paragraph company description (copy\u002Fpaste ready)\n- Founder bios with headshots (high-res, downloadable)\n- Logo pack (SVG + PNG, light + dark, with usage guidelines)\n- Product screenshots (high-res)\n- Recent coverage list (social proof for the next journalist)\n- Founding date, employee count, funding (if disclosed)\n- Press contact email (not a form — journalists hate forms)\n- Recent press releases \u002F announcements\n\n**One sentence at the top:** \"For interview requests or assets, email press@yourcompany.com — we respond within 24 hours.\"\n\nThen *actually* respond within 24 hours.\n\n---\n\n## Quick Reference: Pitch Quality Bar\n\nBefore sending any pitch, the answer to all of these should be yes:\n\n- [ ] Does this journalist cover this beat? (Check their last 5 articles.)\n- [ ] Is there a clear news hook — something that just happened or is about to?\n- [ ] Could this journalist write a complete story from this email alone? (Data, quotes, customer name, contact.)\n- [ ] Is the subject line specific enough to predict the article's headline?\n- [ ] Is the pitch under 150 words?\n- [ ] Did you avoid the words \"revolutionary,\" \"game-changing,\" \"disruptive,\" and \"synergy\"?\n- [ ] Is the ask clear? (Interview? Embargo? Exclusive? Quote?)\n\nIf any answer is no, don't send.\n\n---\n\n## Measurement\n\nWhat to track:\n\n| Metric | Why |\n|--------|-----|\n| **Coverage count** (placements \u002F month) | Activity baseline |\n| **Domain rating of placements** | Backlink value |\n| **Referral traffic from coverage** | Did anyone actually click? |\n| **Brand search lift** | Did people search you after reading? |\n| **AI citation rate** (ChatGPT, Perplexity quote your brand?) | The new measurement that matters |\n| **Sales conversations citing the article** | The only one that matters for revenue |\n\nWhat not to obsess over: AVE (advertising value equivalency) — it's a vanity metric PR firms invented.\n\n---\n\n## Common Workflows\n\n### \"Help me newsjack [trending story]\"\nGo to [newsjacking.md](references\u002Fnewsjacking.md), run the scoring rubric, draft 2–3 angles, pick the best, draft the pitch.\n\n### \"Find journalists who cover [beat]\"\nGo to [journalist-pitching.md](references\u002Fjournalist-pitching.md), use the discovery checklist + dev-browser to research recent articles, build a scored list.\n\n### \"What's worth pitching this week?\"\nCombine: recent product milestones + active news cycles + any data you've collected. Score each potential story by the quality bar above.\n\n### \"What's my story angle?\" \u002F \"How do I get press with no news?\"\nGo to [story-angles.md](references\u002Fstory-angles.md). Fit the situation to one of the three angles (Founding Story \u002F David vs Goliath \u002F Have an Enemy), or turn proprietary data into a data story. Remember: a milestone alone isn't a story — milestone *with narrative* is.\n\n### \"Respond to this HARO query\"\nGo to [press-platforms.md](references\u002Fpress-platforms.md), use the response template, keep it under 200 words.\n\n### \"I'm going on [podcast] next week — help me prep\"\nGo to [podcast-guest-prep.md](references\u002Fpodcast-guest-prep.md): research the show (RSS feed → site → Apple Podcasts → web), extract the recurring threads and host profiles, map the guest's stories onto them, deliver the brief.\n\n### \"Build my press page\"\nUse the checklist above. Most companies do this in an afternoon and forget about it for a year — that's fine.\n",{"name":5,"license":15,"metadata":36,"description":7},{"source":37,"version":38,"source_url":39,"upstream_commit":40},"coreyhaines31\u002Fmarketingskills","1.1.1","https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002F5b2c0007766c\u002Fskills\u002Fpublic-relations","5b2c0007766c6a1cf1d53fd8fc73e979e0821022","main","7ed3b73314d5186120e8d4006febfd7e1c92cf08","skills\u002Fpublic-relations",0,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas","agpt.co","2026-11-10 22:38:50",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add Significant-Gravitas\u002Fskills-catalog --skill public-relations",{"tool":55,"command":56},"bunx","bunx skills add Significant-Gravitas\u002Fskills-catalog --skill public-relations",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Significant-Gravitas\u002Fskills-catalog --skill public-relations","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-relations\u002FSKILL.md",true,[63,67,73,77,81,85,89],{"path":64,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":16},"LICENSE","许可证",1069,{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fjournalist-pitching.md","REFERENCE","参考文档",11065,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-relations\u002Freferences\u002Fjournalist-pitching.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fmedia-outlets.md",9307,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-relations\u002Freferences\u002Fmedia-outlets.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fnewsjacking.md",8493,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-relations\u002Freferences\u002Fnewsjacking.md",{"path":82,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fpodcast-guest-prep.md",5593,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-relations\u002Freferences\u002Fpodcast-guest-prep.md",{"path":86,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fpress-platforms.md",6909,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-relations\u002Freferences\u002Fpress-platforms.md",{"path":90,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fstory-angles.md",6509,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-relations\u002Freferences\u002Fstory-angles.md",[94,106,133,143,157,175],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":31},"01M6AD3S89TGF74S7MK4K5CGC7","workplace-memory-management","Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory\u002F directory for the full knowledge base.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fworkplace-memory-management\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fworkplace-memory-management\u002FSKILL.md",[],[103,104,105,30,22,21],"workplace memory management","memory","plugins",{"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":110,"sourceHtmlUrl":111,"categories":112,"keywords":126,"publishedAt":31},"01M6AD3F5X5DYW1BABD49BQKP8","website-seo-audit","Audit a website, investigate its real search opportunities, and deliver a short data-backed report on the few changes most likely to grow organic traffic that converts.","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-seo-audit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-seo-audit\u002FSKILL.md",[113,118,121],{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":119,"categoryName":120,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":122,"categoryName":123,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[127,128,129,22,105,30,130,131,132],"website seo audit","audit","website","search","report","plugin",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":31},"01M6AD32RYMK03P50DM0T184NJ","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[141,142,30,22],"verification before completion","verification",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":147,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":31},"01M6AD2WSQG7BGPXA7XP4DFZX8","vendor-evaluation","Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-evaluation\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-evaluation\u002FSKILL.md",[],[151,152,105,30,153,154,155,22,156],"vendor evaluation","negotiation","assessment","risk assessment","cost analysis","review",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":161,"sourceHtmlUrl":162,"categories":163,"keywords":170,"publishedAt":31},"01M6AD2RBT6004C07RZRDSTA52","vendor-contract-status","Check the status of existing agreements with a vendor across all connected systems — CLM, CRM, email, and document storage — with gap analysis and upcoming deadlines. Use when onboarding or renewing a vendor, when you need a consolidated view of what's signed and what's missing (MSA, DPA, SOW), or when checking for approaching expirations and surviving obligations.","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-contract-status\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-contract-status\u002FSKILL.md",[164,167],{"categoryNo":165,"categoryName":166,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":168,"categoryName":169,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000037","律师与法务",[171,172,22,173,105,174,30],"vendor contract status","status","storage","onboarding",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":179,"sourceHtmlUrl":180,"categories":181,"keywords":185,"publishedAt":31},"01M6AD2KPNXN5CNS3CA4FRWT97","user-cohort-analysis","Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fuser-cohort-analysis\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fuser-cohort-analysis\u002FSKILL.md",[182],{"categoryNo":183,"categoryName":184,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000033","数据分析师",[186,187,30,22],"user cohort analysis","analytics"]