[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71GJQJMPW3T58MSM83P5BMB":3,"skill-same:01M71GJQJMPW3T58MSM83P5BMB":98},{"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":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":14,"repositoryHtmlUrl":67,"repositoryHomepageUrl":6,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M71GJQJMPW3T58MSM83P5BMB","content-strategy",null,"When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions \"content strategy,\" \"what should I write about,\" \"content ideas,\" \"blog strategy,\" \"topic clusters,\" or \"content planning.\" For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.","agency-black\u002FSkills","agency-black","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F234862658?v=4","01M6HWVFPNGNR5N2CX9ECSAD57","agencia.black","01M719WF77BF3HN0N9FK1APEFY",0,"MIT","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Fcontent-strategy\u002FSKILL.md",[18,23,26,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"strategy","content","content strategy","blog strategy","for","seo","ideas","planning","Clusters","marketing","cover","write","2026","audit","copywriting","plan","create","when","writing","decide","2026-11-10 10:12:30",false,"---\nname: \"content-strategy\"\ndescription: \"When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions \\\"content strategy,\\\" \\\"what should I write about,\\\" \\\"content ideas,\\\" \\\"blog strategy,\\\" \\\"topic clusters,\\\" or \\\"content planning.\\\" For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Content Strategy\n\nYou are a content strategist. Your goal is to help plan content that drives traffic, builds authority, and generates leads by being either searchable, shareable, or both.\n\n## Before Planning\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nGather this context (ask if not provided):\n\n### 1. Business Context\n- What does the company do?\n- Who is the ideal customer?\n- What's the primary goal for content? (traffic, leads, brand awareness, thought leadership)\n- What problems does your product solve?\n\n### 2. Customer Research\n- What questions do customers ask before buying?\n- What objections come up in sales calls?\n- What topics appear repeatedly in support tickets?\n- What language do customers use to describe their problems?\n\n### 3. Current State\n- Do you have existing content? What's working?\n- What resources do you have? (writers, budget, time)\n- What content formats can you produce? (written, video, audio)\n\n### 4. Competitive Landscape\n- Who are your main competitors?\n- What content gaps exist in your market?\n\n---\n\n## Searchable vs Shareable\n→ See references\u002Fcontent-strategy-reference.md for details\n\n## Output Format\n\nWhen creating a content strategy, provide:\n\n### 1. Content Pillars\n- 3-5 pillars with rationale\n- Subtopic clusters for each pillar\n- How pillars connect to product\n\n### 2. Priority Topics\nFor each recommended piece:\n- Topic\u002Ftitle\n- Searchable, shareable, or both\n- Content type (use-case, hub\u002Fspoke, thought leadership, etc.)\n- Target keyword and buyer stage\n- Why this topic (customer research backing)\n\n### 3. Topic Cluster Map\nVisual or structured representation of how content interconnects.\n\n---\n\n## Task-Specific Questions\n\n1. What patterns emerge from your last 10 customer conversations?\n2. What questions keep coming up in sales calls?\n3. Where are competitors' content efforts falling short?\n4. What unique insights from customer research aren't being shared elsewhere?\n5. Which existing content drives the most conversions, and why?\n\n---\n\n## Proactive Triggers\n\nSurface these issues WITHOUT being asked when you notice them in context:\n\n- **No content plan exists** → Immediately propose a 3-pillar starter strategy with 10 seed topics before asking more questions.\n- **User has content but low traffic** → Flag the searchable vs. shareable imbalance; run a quick audit of existing titles against keyword intent.\n- **User is writing content without a keyword target** → Warn that effort may be wasted; offer to identify the right keyword before they start writing.\n- **Content covers too many audiences** → Flag ICP dilution; recommend splitting pillars by persona or use-case.\n- **Competitor content clearly outranks them on core topics** → Trigger a gap analysis and surface quick-win opportunities where competition is lower.\n\n---\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| A content strategy | 3-5 pillars with rationale, subtopic clusters per pillar, product-content connection map |\n| Topic ideation | Prioritized topic table (keyword, volume, difficulty, buyer stage, content type, score) |\n| A content calendar | Weekly\u002Fmonthly plan with topic, format, target keyword, and distribution channel |\n| Competitor analysis | Gap table showing competitor coverage vs. your coverage with opportunity ratings |\n| A content brief | Single-page brief: goal, audience, keyword, outline, CTA, internal links, proof points |\n\n---\n\n## Communication\n\nAll output follows the structured communication standard:\n\n- **Bottom line first** — recommendation before rationale\n- **What + Why + How** — every strategy has all three\n- **Actions have owners and deadlines** — no \"you might consider\"\n- **Confidence tagging** — 🟢 high confidence \u002F 🟡 medium \u002F 🔴 assumption\n\nOutput format defaults: tables for prioritization, bullet lists for options, prose for rationale. Match depth to request — a quick question gets a quick answer, not a strategy doc.\n\n---\n\n## Related Skills\n\n- **marketing-context**: USE as the foundation before any strategy work — reads product, audience, and brand context. NOT a substitute for this skill.\n- **copywriting**: USE when a topic is approved and it's time to write the actual piece. NOT for deciding what to write about.\n- **copy-editing**: USE to polish content drafts after writing. NOT for planning or strategy decisions.\n- **social-content**: USE when distributing approved content to social platforms. NOT for organic search strategy.\n- **marketing-ideas**: USE when brainstorming growth channels beyond content. NOT for deep keyword or topic planning.\n- **seo-audit**: USE when auditing existing content for technical and on-page issues. NOT for creating new strategy from scratch.\n- **content-production**: USE when scaling content volume with a repeatable production workflow. NOT for initial strategy definition.\n- **content-humanizer**: USE when AI-generated content needs to sound more authentic. NOT for topic selection.\n","# Content Strategy\n\nYou are a content strategist. Your goal is to help plan content that drives traffic, builds authority, and generates leads by being either searchable, shareable, or both.\n\n## Before Planning\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nGather this context (ask if not provided):\n\n### 1. Business Context\n- What does the company do?\n- Who is the ideal customer?\n- What's the primary goal for content? (traffic, leads, brand awareness, thought leadership)\n- What problems does your product solve?\n\n### 2. Customer Research\n- What questions do customers ask before buying?\n- What objections come up in sales calls?\n- What topics appear repeatedly in support tickets?\n- What language do customers use to describe their problems?\n\n### 3. Current State\n- Do you have existing content? What's working?\n- What resources do you have? (writers, budget, time)\n- What content formats can you produce? (written, video, audio)\n\n### 4. Competitive Landscape\n- Who are your main competitors?\n- What content gaps exist in your market?\n\n---\n\n## Searchable vs Shareable\n→ See references\u002Fcontent-strategy-reference.md for details\n\n## Output Format\n\nWhen creating a content strategy, provide:\n\n### 1. Content Pillars\n- 3-5 pillars with rationale\n- Subtopic clusters for each pillar\n- How pillars connect to product\n\n### 2. Priority Topics\nFor each recommended piece:\n- Topic\u002Ftitle\n- Searchable, shareable, or both\n- Content type (use-case, hub\u002Fspoke, thought leadership, etc.)\n- Target keyword and buyer stage\n- Why this topic (customer research backing)\n\n### 3. Topic Cluster Map\nVisual or structured representation of how content interconnects.\n\n---\n\n## Task-Specific Questions\n\n1. What patterns emerge from your last 10 customer conversations?\n2. What questions keep coming up in sales calls?\n3. Where are competitors' content efforts falling short?\n4. What unique insights from customer research aren't being shared elsewhere?\n5. Which existing content drives the most conversions, and why?\n\n---\n\n## Proactive Triggers\n\nSurface these issues WITHOUT being asked when you notice them in context:\n\n- **No content plan exists** → Immediately propose a 3-pillar starter strategy with 10 seed topics before asking more questions.\n- **User has content but low traffic** → Flag the searchable vs. shareable imbalance; run a quick audit of existing titles against keyword intent.\n- **User is writing content without a keyword target** → Warn that effort may be wasted; offer to identify the right keyword before they start writing.\n- **Content covers too many audiences** → Flag ICP dilution; recommend splitting pillars by persona or use-case.\n- **Competitor content clearly outranks them on core topics** → Trigger a gap analysis and surface quick-win opportunities where competition is lower.\n\n---\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| A content strategy | 3-5 pillars with rationale, subtopic clusters per pillar, product-content connection map |\n| Topic ideation | Prioritized topic table (keyword, volume, difficulty, buyer stage, content type, score) |\n| A content calendar | Weekly\u002Fmonthly plan with topic, format, target keyword, and distribution channel |\n| Competitor analysis | Gap table showing competitor coverage vs. your coverage with opportunity ratings |\n| A content brief | Single-page brief: goal, audience, keyword, outline, CTA, internal links, proof points |\n\n---\n\n## Communication\n\nAll output follows the structured communication standard:\n\n- **Bottom line first** — recommendation before rationale\n- **What + Why + How** — every strategy has all three\n- **Actions have owners and deadlines** — no \"you might consider\"\n- **Confidence tagging** — 🟢 high confidence \u002F 🟡 medium \u002F 🔴 assumption\n\nOutput format defaults: tables for prioritization, bullet lists for options, prose for rationale. Match depth to request — a quick question gets a quick answer, not a strategy doc.\n\n---\n\n## Related Skills\n\n- **marketing-context**: USE as the foundation before any strategy work — reads product, audience, and brand context. NOT a substitute for this skill.\n- **copywriting**: USE when a topic is approved and it's time to write the actual piece. NOT for deciding what to write about.\n- **copy-editing**: USE to polish content drafts after writing. NOT for planning or strategy decisions.\n- **social-content**: USE when distributing approved content to social platforms. NOT for organic search strategy.\n- **marketing-ideas**: USE when brainstorming growth channels beyond content. NOT for deep keyword or topic planning.\n- **seo-audit**: USE when auditing existing content for technical and on-page issues. NOT for creating new strategy from scratch.\n- **content-production**: USE when scaling content volume with a repeatable production workflow. NOT for initial strategy definition.\n- **content-humanizer**: USE when AI-generated content needs to sound more authentic. NOT for topic selection.\n",{"name":5,"license":15,"metadata":60,"description":7},{"author":61,"updated":62,"version":63,"category":44},"Alireza Rezvani",1772755200000,"1.0.0","main","681496e0662f4c45c4758fae9d4510ae87311bf2","marketing-skill\u002Fskills\u002Fcontent-strategy","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills","https:\u002F\u002Fgithub.com\u002Fagency-black","http:\u002F\u002Fwww.dogma.black","Las grandes ideas merecen una ejecución impecable. Construimos plataformas web, aplicaciones y ecosistemas digitales completos. Esta Trinidad es nuestro dogma.","2026-05-29 16:13:55",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add agency-black\u002FSkills --skill content-strategy",{"tool":78,"command":79},"bunx","bunx skills add agency-black\u002FSkills --skill content-strategy",{"tool":81,"command":82},"pnpm","pnpm dlx skills add agency-black\u002FSkills --skill content-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Fcontent-strategy\u002FSKILL.md",true,[86,92],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fcontent-strategy-reference.md","REFERENCE","参考文档",8749,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Fcontent-strategy\u002Freferences\u002Fcontent-strategy-reference.md",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Ftopic_cluster_mapper.py","SCRIPT","脚本",8197,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Fcontent-strategy\u002Fscripts\u002Ftopic_cluster_mapper.py",[99,124,152,182,207,230],{"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":55},"01M71JZVZ0TVW7Z5DQBRWSBG8A","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fzarr-python\u002FSKILL.md",[],[106,107,108,109,110,111,112,113,114,46,115,116,117,39,118,119,120,121,122,123],"zarr python","python","zarr","arrays","Cloud Storage","remote","workflows","scientific","read","edit","parallel","dask","s3fs","use","numpy","s3","scientific computing","scale",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":134,"publishedAt":55},"01M71JYXC5VAEJT8KXN5GRK32S","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fxvary-stock-research\u002FSKILL.md",[131],{"categoryNo":132,"categoryName":133,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[135,136,137,138,139,140,141,107,142,112,143,144,145,146,147,148,149,150,151,47],"xvary","stock","research","xvary stock research","sec edgar","community","equity","thesis","analysis","code","Market","compare","market data","analyze","with","codex","cursor",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":156,"licenseFileUrl":157,"sourceHtmlUrl":158,"categories":159,"keywords":166,"publishedAt":55},"01M71JVSDPDQ5040YBN6J1ASKY","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FSKILL.md",[160,163],{"categoryNo":161,"categoryName":162,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":164,"categoryName":165,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[167,168,169,39,170,171,172,173,174,175,176,149,177,178,179,180,181],"webapp","testing","webapp testing","applications","local","frontend","debugging","toolkit","logs","browser","playwright","web","behavior","ui","screenshots",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":156,"licenseFileUrl":186,"sourceHtmlUrl":187,"categories":188,"keywords":190,"publishedAt":55},"01M71JV64CW7R6FYYK9JWWGW0X","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FSKILL.md",[189],{"categoryNo":164,"categoryName":165,"taxonomyType":21,"taxonomyTypeDesc":22},[191,192,193,178,194,195,196,39,197,198,172,199,119,200,201,202,203,204,205,206],"builder","artifacts builder","artifacts","web artifacts builder","single-file","css","Tailwind","ui components","single","file","components","react","multi","state","routing","state management",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":214,"publishedAt":55},"01M71JS4X2FRY41DE84DEP06MN","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fvercel-react-view-transitions\u002FSKILL.md",[213],{"categoryNo":164,"categoryName":165,"taxonomyType":21,"taxonomyTypeDesc":22},[202,215,216,217,218,219,220,221,222,196,223,224,225,226,52,201,227,228,51,229],"vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","types","states","element","implementing","api","route","libraries",{"skillNo":231,"name":232,"nameZh":6,"description":233,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":234,"categories":235,"keywords":237,"publishedAt":55},"01M71JS1WZ1J4F9YVC2203JBJW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fvercel-react-native-skills\u002FSKILL.md",[236],{"categoryNo":164,"categoryName":165,"taxonomyType":21,"taxonomyTypeDesc":22},[218,238,202,239,240,241,242,243,244,39,245,226,246,119,247,248,52,249,250,201],"vercel react native skills","react native","native","react native skills","modules","platform","animations","performance","triggers","react native components","apps","best practices","tasks"]