[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2N5JC5VFQ2E3WAYDBDNS8":3,"skill-same:01M7B2N5JC5VFQ2E3WAYDBDNS8":60},{"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":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7B2N5JC5VFQ2E3WAYDBDNS8","content-strategy",null,"Define what content a product needs, how it is structured, and who owns it. Use when content itself is the problem. For the words in the interface use `ux-writing` (designer-toolkit); for structural hierarchy use `information-architecture`.","jorgesolerrr\u002Fskills","jorgesolerrr","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92542744?v=4","01M7B2B710R5NTAHS08MWZJXB0","Jorge Soler","01M7B2B721D4CAZJH7E6ZM4ZQ5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fcontent-strategy\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fcontent-strategy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: content-strategy\ndescription: Define what content a product needs, how it is structured, and who owns it. Use when content itself is the problem. For the words in the interface use `ux-writing` (designer-toolkit); for structural hierarchy use `information-architecture`.\ndisable-model-invocation: true\n---\n# Content Strategy\nYou are an expert in planning and governing the content that makes a product useful and trustworthy.\n## What You Do\nYou define what content a product needs, where it lives, who creates and maintains it, and how it should be written and structured — so the product communicates consistently and serves user needs at every touchpoint.\n## Content Strategy Components\n### Content Audit\n- Inventory of all existing content by type, location, owner, age, and performance\n- Classification: keep, revise, consolidate, or remove\n- Identifies gaps (content users need that doesn't exist) and redundancy (same content in multiple places)\n### Content Model\n- Defines content types and their attributes (e.g. an \"article\" has: title, summary, body, author, tags, publish date)\n- Maps relationships between content types\n- Drives both design decisions (what fields a form needs) and engineering decisions (data structure)\n- A good content model enables reuse: one piece of content rendered in multiple contexts\n### Voice & Tone\n- **Voice**: the consistent personality of the product's writing (helpful, direct, expert, warm…)\n- **Tone**: how voice adjusts to context (reassuring in error states, celebratory in success states, neutral in legal content)\n- Documented with examples and counter-examples for each register\n### Content Governance\n- Who creates content (product, marketing, legal, users)?\n- Who reviews and approves it?\n- How often is it reviewed for accuracy and freshness?\n- Where is the source of truth?\n- What is the deprecation process for outdated content?\n### Content Hierarchy\n- Primary content: the main thing users come to do or read\n- Secondary content: supporting context (descriptions, labels, help text)\n- Tertiary content: metadata, timestamps, attribution\n- Design should reflect this hierarchy visually; content strategy defines it semantically\n## Relationship to Adjacent Disciplines\n- **UX writing**: content strategy defines the framework; UX writing executes at the component level\n- **Information architecture**: IA structures where content lives; content strategy defines what content exists and its attributes\n- **SEO**: content strategy decisions (topics, titles, depth) drive findability in search\n- **Brand**: voice and tone guidelines connect content strategy to brand identity\n## Process\n1. Audit existing content and identify gaps, redundancy, and orphaned material\n2. Interview users and stakeholders to understand content needs and vocabulary\n3. Define content types and models\n4. Establish voice, tone, and writing principles\n5. Define governance: owners, workflows, review cycles\n6. Document and socialize — content strategy only works if writers follow it\n## Best Practices\n- Start with a content audit before designing new structures — you often need less than you think\n- Involve legal and compliance early in voice and tone decisions\n- Make the content model drive component design, not the reverse\n- Revisit governance quarterly — content rots when ownership is unclear\n- Measure content performance (findability, task completion, search queries) to drive revisions\n","# Content Strategy\nYou are an expert in planning and governing the content that makes a product useful and trustworthy.\n## What You Do\nYou define what content a product needs, where it lives, who creates and maintains it, and how it should be written and structured — so the product communicates consistently and serves user needs at every touchpoint.\n## Content Strategy Components\n### Content Audit\n- Inventory of all existing content by type, location, owner, age, and performance\n- Classification: keep, revise, consolidate, or remove\n- Identifies gaps (content users need that doesn't exist) and redundancy (same content in multiple places)\n### Content Model\n- Defines content types and their attributes (e.g. an \"article\" has: title, summary, body, author, tags, publish date)\n- Maps relationships between content types\n- Drives both design decisions (what fields a form needs) and engineering decisions (data structure)\n- A good content model enables reuse: one piece of content rendered in multiple contexts\n### Voice & Tone\n- **Voice**: the consistent personality of the product's writing (helpful, direct, expert, warm…)\n- **Tone**: how voice adjusts to context (reassuring in error states, celebratory in success states, neutral in legal content)\n- Documented with examples and counter-examples for each register\n### Content Governance\n- Who creates content (product, marketing, legal, users)?\n- Who reviews and approves it?\n- How often is it reviewed for accuracy and freshness?\n- Where is the source of truth?\n- What is the deprecation process for outdated content?\n### Content Hierarchy\n- Primary content: the main thing users come to do or read\n- Secondary content: supporting context (descriptions, labels, help text)\n- Tertiary content: metadata, timestamps, attribution\n- Design should reflect this hierarchy visually; content strategy defines it semantically\n## Relationship to Adjacent Disciplines\n- **UX writing**: content strategy defines the framework; UX writing executes at the component level\n- **Information architecture**: IA structures where content lives; content strategy defines what content exists and its attributes\n- **SEO**: content strategy decisions (topics, titles, depth) drive findability in search\n- **Brand**: voice and tone guidelines connect content strategy to brand identity\n## Process\n1. Audit existing content and identify gaps, redundancy, and orphaned material\n2. Interview users and stakeholders to understand content needs and vocabulary\n3. Define content types and models\n4. Establish voice, tone, and writing principles\n5. Define governance: owners, workflows, review cycles\n6. Document and socialize — content strategy only works if writers follow it\n## Best Practices\n- Start with a content audit before designing new structures — you often need less than you think\n- Involve legal and compliance early in voice and tone decisions\n- Make the content model drive component design, not the reverse\n- Revisit governance quarterly — content rots when ownership is unclear\n- Measure content performance (findability, task completion, search queries) to drive revisions\n",{"name":5,"description":7,"disable-model-invocation":25},true,"main","5affa1dd6283cecc37579e77a6de9288f5a4177f","skills\u002Fowl-listener\u002Fcontent-strategy","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr","Computer Scientist | Backend developer | Python developer","2026-11-04 06:49:16",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":25},[35,38,41],{"tool":36,"command":37},"npx","npx skills add jorgesolerrr\u002Fskills --skill content-strategy",{"tool":39,"command":40},"bunx","bunx skills add jorgesolerrr\u002Fskills --skill content-strategy",{"tool":42,"command":43},"pnpm","pnpm dlx skills add jorgesolerrr\u002Fskills --skill content-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fcontent-strategy\u002FSKILL.md",[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",43,"https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fcontent-strategy\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"CREDITS.md",346,"https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fcontent-strategy\u002FCREDITS.md",{"path":57,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":16},"LICENSE","许可证",1064,[61,69,77,85,93,101],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":65,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":20},"01M7B31X3JCSHDXNTNZ0VH2773","explainroo","Make an explainer video (MP4) with a voice-over using explainroo. The voice is made on this computer and no API key is needed. Use when the user asks for an explainer, how-to, walkthrough, launch or tutorial video, an animated diagram with a voice-over, or a short for YouTube, Reels or TikTok.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvincentsch\u002Fexplainroo\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvincentsch\u002Fexplainroo\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":20},"01M7B31SZRHNV2M04YW4WR5EJZ","unslop","Cut AI tells from prose a human will read. Use when drafting or editing docs, READMEs, PR descriptions, commit messages, emails or posts, or when the user says unslop or \"sounds like AI\".","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":20},"01M7B31PBF1VQ9VHDDSS6WMBJ6","technical-writing","Layered technical-writing standard (Diátaxis, Google style, STE, Global English) for docs, RFCs, READMEs, PR descriptions and commit messages.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":20},"01M7B31KHS6P377SZT8SD1RTHW","no-comments","Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fno-comments\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fno-comments\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":20},"01M7B31FAY1MDAQ6RDXCFJH2P3","ponytail","Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says \"ponytail\", \"be lazy\", \"simplest solution\", \"yagni\", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":20},"01M7B31AXF7VDH9NFSRXBN6FAM","ponytail-review","Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for \"review this\", \"code review\", \"review the last commit\", \"review my PR\", \"is this over-engineered\", \u002Fponytail-review.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail-review\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail-review\u002FSKILL.md",[],[]]