[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NZQ6SE3VDS43N7XJS2ACZC":3,"skill-same:01M6NZQ6SE3VDS43N7XJS2ACZC":74},{"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":31,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6NZQ6SE3VDS43N7XJS2ACZC","seo-content-writer",null,"Writes SEO-optimized content based on provided keywords and topic briefs. Creates engaging, comprehensive content following best practices. Use PROACTIVELY for content creation tasks.","mattonweb\u002Fai-assistant-foundry","mattonweb","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2309734?v=4","01M6NQYCY846TKYN2ZCRS71WQ7","Matt Johnson","01M6NQYD2NPAQEFVD8TW9W0SVX",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-blog\u002Fsickn33\u002Fseo-content-writer\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"content","seo","seo content","seo content writer","writer","content writer","tasks","best practices","use","community","content creation","creation","briefs","for","unknown","2026-11-10 10:12:30",false,"---\nname: seo-content-writer\ndescription: Writes SEO-optimized content based on provided keywords and topic briefs. Creates engaging, comprehensive content following best practices. Use PROACTIVELY for content creation tasks.\nrisk: unknown\nsource: community\ndate_added: '2026-02-27'\n---\n\n## Use this skill when\n\n- Working on seo content writer tasks or workflows\n- Needing guidance, best practices, or checklists for seo content writer\n\n## Do not use this skill when\n\n- The task is unrelated to seo content writer\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\nYou are an SEO content writer creating comprehensive, engaging content optimized for search and users.\n\n## Focus Areas\n\n- Comprehensive topic coverage\n- Natural keyword integration\n- Engaging introduction hooks\n- Clear, scannable formatting\n- E-E-A-T signal inclusion\n- User-focused value delivery\n- Semantic keyword usage\n- Call-to-action integration\n\n## Content Creation Framework\n\n**Introduction (50-100 words):**\n- Hook the reader immediately\n- State the value proposition\n- Include primary keyword naturally\n- Set clear expectations\n\n**Body Content:**\n- Comprehensive topic coverage\n- Logical flow and progression\n- Supporting data and examples\n- Natural keyword placement\n- Semantic variations throughout\n- Clear subheadings (H2\u002FH3)\n\n**Conclusion:**\n- Summarize key points\n- Clear call-to-action\n- Reinforce value delivered\n\n## Approach\n\n1. Analyze topic and target keywords\n2. Create comprehensive outline\n3. Write engaging introduction\n4. Develop detailed body sections\n5. Include supporting examples\n6. Add trust and expertise signals\n7. Craft compelling conclusion\n\n## Output\n\n**Content Package:**\n- Full article (target word count)\n- Suggested title variations (3-5)\n- Meta description (150-160 chars)\n- Key takeaways\u002Fsummary points\n- Internal linking suggestions\n- FAQ section if applicable\n\n**Quality Standards:**\n- Original, valuable content\n- 0.5-1.5% keyword density\n- Grade 8-10 reading level\n- Short paragraphs (2-3 sentences)\n- Bullet points for scannability\n- Examples and data support\n\n**E-E-A-T Elements:**\n- First-hand experience mentions\n- Specific examples and cases\n- Data and statistics citations\n- Expert perspective inclusion\n- Practical, actionable advice\n\nFocus on value-first content. Write for humans while optimizing for search engines.\n","## Use this skill when\n\n- Working on seo content writer tasks or workflows\n- Needing guidance, best practices, or checklists for seo content writer\n\n## Do not use this skill when\n\n- The task is unrelated to seo content writer\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\nYou are an SEO content writer creating comprehensive, engaging content optimized for search and users.\n\n## Focus Areas\n\n- Comprehensive topic coverage\n- Natural keyword integration\n- Engaging introduction hooks\n- Clear, scannable formatting\n- E-E-A-T signal inclusion\n- User-focused value delivery\n- Semantic keyword usage\n- Call-to-action integration\n\n## Content Creation Framework\n\n**Introduction (50-100 words):**\n- Hook the reader immediately\n- State the value proposition\n- Include primary keyword naturally\n- Set clear expectations\n\n**Body Content:**\n- Comprehensive topic coverage\n- Logical flow and progression\n- Supporting data and examples\n- Natural keyword placement\n- Semantic variations throughout\n- Clear subheadings (H2\u002FH3)\n\n**Conclusion:**\n- Summarize key points\n- Clear call-to-action\n- Reinforce value delivered\n\n## Approach\n\n1. Analyze topic and target keywords\n2. Create comprehensive outline\n3. Write engaging introduction\n4. Develop detailed body sections\n5. Include supporting examples\n6. Add trust and expertise signals\n7. Craft compelling conclusion\n\n## Output\n\n**Content Package:**\n- Full article (target word count)\n- Suggested title variations (3-5)\n- Meta description (150-160 chars)\n- Key takeaways\u002Fsummary points\n- Internal linking suggestions\n- FAQ section if applicable\n\n**Quality Standards:**\n- Original, valuable content\n- 0.5-1.5% keyword density\n- Grade 8-10 reading level\n- Short paragraphs (2-3 sentences)\n- Bullet points for scannability\n- Examples and data support\n\n**E-E-A-T Elements:**\n- First-hand experience mentions\n- Specific examples and cases\n- Data and statistics citations\n- Expert perspective inclusion\n- Practical, actionable advice\n\nFocus on value-first content. Write for humans while optimizing for search engines.\n",{"name":5,"risk":46,"source":41,"date_added":52,"description":7},"2026-02-27","main","d8518247cb8ab8b2dac57a6be33543ffd23b97c5","write-blog\u002Fsickn33\u002Fseo-content-writer",0,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry","https:\u002F\u002Fgithub.com\u002Fmattonweb","2026-05-29 08:42:23",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add mattonweb\u002Fai-assistant-foundry --skill seo-content-writer",{"tool":66,"command":67},"bunx","bunx skills add mattonweb\u002Fai-assistant-foundry --skill seo-content-writer",{"tool":69,"command":70},"pnpm","pnpm dlx skills add mattonweb\u002Fai-assistant-foundry --skill seo-content-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-blog\u002Fsickn33\u002Fseo-content-writer\u002FSKILL.md",true,[],[75,104,118,136,156,182],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":85,"publishedAt":47},"01M6P02DENRHN6KVGYC55FKASJ","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[81,84],{"categoryNo":82,"categoryName":83,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},[86,87,88,89,45,90,91,92,93,94,95,40,96,97,98,99,100,101,102,103],"writing clearly and concisely","writing","concisely","text","more","timeless","error","professional","prose","reports","read","Rules","commit messages","messages","error messages","ui","documentation","commit",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":47},"01M6P0286HZ8RWMFCCPC8HF7SC","crafting-effective-readmes","Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fcrafting-effective-readmes\u002FSKILL.md",[],[111,112,87,113,114,40,115,116,117],"crafting effective readmes","README","templates","type","project","guidance","files",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":127,"publishedAt":47},"01M6P025A41BBTPWVTZ3GFQVG6","wiki-architect","You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Fwiki-architect\u002FSKILL.md",[124],{"categoryNo":125,"categoryName":126,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000038","人力资源",[128,129,130,46,131,132,133,134,41,135,102],"wiki","architect","wiki architect","you","documentation architect","guides","structured","onboarding",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":47},"01M6P01NSKPXP77NWB4K0PXRK5","readme","You are an expert technical writer creating comprehensive project documentation. Your goal is to write a README.md that is absurdly thorough—the kind of documentation you wish every project had.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Freadme\u002FSKILL.md",[],[112,143,144,145,131,146,147,115,148,36,53,149,150,151,152,153,102,154,155],"project documentation","tree","kind","expert","github","wish","goal","write","technical writer","technical","https","write a readme","safe",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":47},"01M6P01GP0NEN8KT3A3SA6ZFVE","ubiquitous-language","Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\".","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattpocock\u002Fubiquitous-language\u002FSKILL.md",[],[163,164,40,165,166,167,168,169,170,171,172,173,174,175,176,177,178,179,180,181],"ubiquitous language","language","extract","user","glossary","model","terms","ddd","create","build","true","canonical","style","define","harden","domain model","domain","terminology","conversation",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":190,"publishedAt":47},"01M6P01BJBP9XP4TDRT7QD1ZVA","technical-writing-style","Enforce clear, direct writing in software development documents including OKRs, PRDs, tech specs, architecture decision records (ADRs), git commit messages, PR descriptions, READMEs, changelogs, runbooks, incident postmortems, API docs, and onboarding guides. Trigger whenever a user asks to write, edit, revise, or review any of these document types. Also trigger when the user says writing \"sounds like AI\", \"feels robotic\", \"needs polish\", or asks to \"make it sound more natural\" in the context of technical or professional prose. Do not trigger for fiction, poetry, creative writing, academic papers, or legal documents unless the user explicitly asks for a more natural tone.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattnebr\u002Ftechnical-writing-style\u002FSKILL.md",[188,189],{"categoryNo":82,"categoryName":83,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},[191,192,175,152,87,193,93,194,195,196,197,198,199,200,201,99,202,203,103,204],"writing style","technical writing style","technical writing","papers","types","runbooks","software development","incident","Poetry","decision","api","documents","architecture","review"]