[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CD9N2172CD80WC565JWSBB":3,"skill-same:01M7CD9N2172CD80WC565JWSBB":50},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CD9N2172CD80WC565JWSBB","seo-aeo-blog-writer",null,"Writes long-form blog posts with TL;DR block, definition sentence, comparison table, and 5-question FAQ for SEO ranking and AEO citation. Activate when the user wants to write a blog post, article, or long-form content piece.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fseo-aeo-blog-writer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: seo-aeo-blog-writer\ndescription: \"Writes long-form blog posts with TL;DR block, definition sentence, comparison table, and 5-question FAQ for SEO ranking and AEO citation. Activate when the user wants to write a blog post, article, or long-form content piece.\"\nrisk: safe\nsource: community\ndate_added: \"2026-04-01\"\n---\n\n# SEO-AEO Blog Writer\n\n## Overview\n\nWrites structured long-form blog posts (800–3000 words) that satisfy both SEO ranking signals and AEO citation requirements. Every post includes a TL;DR direct-answer block, a definition sentence, structured H2\u002FH3 hierarchy, a comparison table where relevant, and exactly 5 FAQ entries written for AI extraction.\n\nPart of the [SEO-AEO Engine](https:\u002F\u002Fgithub.com\u002Fmrprewsh\u002Fseo-aeo-engine).\n\n## When to Use This Skill\n\n- Use when writing a cluster article from a content cluster map\n- Use when creating a long-form guide to build topical authority\n- Use when you need content that can be cited by AI engines like Perplexity or ChatGPT\n- Use when you need a blog post that follows a consistent, auditable structure\n\n## How It Works\n\n### Step 1: Write the TL;DR Block First\nWrite a 2–3 sentence direct answer to the article's core question. Place it immediately after the H1 in a blockquote. This is the first block AI engines attempt to extract.\n\n### Step 2: Build the Heading Skeleton\nSet H1, H2s (4–6), and H3s before writing any body content. The first H2 must be a \"What Is\" section with a clean definition sentence as its opening line.\n\n### Step 3: Write Body Sections\nFollow the section order: What Is → Why It Matters → How It Works (with H3 sub-concepts) → Practical Steps → Common Mistakes → FAQ → Conclusion.\n\n### Step 4: Write 5 FAQ Entries\nUse long-tail and secondary keywords as questions. Each answer must be under 50 words and self-contained — readable without any surrounding context.\n\n### Step 5: Run AEO and SEO Checklists\nVerify TL;DR presence, definition sentence, FAQ count, keyword placement, and heading structure before outputting.\n\n## Examples\n\n### Example: TL;DR Block\nHow to Manage a Remote Engineering Team\n\nTL;DR: Managing a remote engineering team requires async\ncommunication tools, clear documentation standards, and\ntimezone-aware sprint planning. Teams that nail these three\nareas ship consistently regardless of where members are located.\n\n\n### Example: FAQ Section\nQ: What is the biggest challenge of remote engineering teams?\nA: Async communication. Without shared hours, decisions slow down\nand context gets lost. Teams that document decisions in writing\nand use structured standup tools close this gap fastest.\nQ: How do you run a daily standup with a remote team?\nA: Use async video or text standups posted at the start of each\nmember's day. Tools like Loom or Slack threads work well.\nAvoid live calls across more than 2 timezones.\n\n## Best Practices\n\n- ✅ **Do:** Write the TL;DR block before writing anything else — it anchors the article\n- ✅ **Do:** Make the \"What Is\" definition sentence extractable on its own — one clean sentence\n- ✅ **Do:** Use secondary keywords as FAQ questions to capture long-tail traffic\n- ❌ **Don't:** Write FAQ answers longer than 50 words — AI engines skip long answers\n- ❌ **Don't:** Use duplicate H2 headings anywhere in the article\n- ❌ **Don't:** Skip the comparison table if the topic involves comparing options\n\n## Common Pitfalls\n\n- **Problem:** TL;DR block is too vague to be extracted as a direct answer\n  **Solution:** The TL;DR must answer the article's core question in 2–3 sentences. If it doesn't answer a specific question, rewrite it.\n\n- **Problem:** FAQ answers reference \"as mentioned above\" or other context\n  **Solution:** Every FAQ answer must stand completely alone — no references to other parts of the article.\n\n## Related Skills\n\n- `@seo-aeo-content-cluster` — provides the topic and keyword for this article\n- `@seo-aeo-content-quality-auditor` — audits the completed post for SEO and AEO signals\n- `@seo-aeo-internal-linking` — maps links between this post and related pages\n\n## Additional Resources\n\n- [SEO-AEO Engine Repository](https:\u002F\u002Fgithub.com\u002Fmrprewsh\u002Fseo-aeo-engine)\n- [Full Blog Writer SKILL.md](https:\u002F\u002Fgithub.com\u002Fmrprewsh\u002Fseo-aeo-engine\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fblog-writer\u002FSKILL.md)\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# SEO-AEO Blog Writer\n\n## Overview\n\nWrites structured long-form blog posts (800–3000 words) that satisfy both SEO ranking signals and AEO citation requirements. Every post includes a TL;DR direct-answer block, a definition sentence, structured H2\u002FH3 hierarchy, a comparison table where relevant, and exactly 5 FAQ entries written for AI extraction.\n\nPart of the [SEO-AEO Engine](https:\u002F\u002Fgithub.com\u002Fmrprewsh\u002Fseo-aeo-engine).\n\n## When to Use This Skill\n\n- Use when writing a cluster article from a content cluster map\n- Use when creating a long-form guide to build topical authority\n- Use when you need content that can be cited by AI engines like Perplexity or ChatGPT\n- Use when you need a blog post that follows a consistent, auditable structure\n\n## How It Works\n\n### Step 1: Write the TL;DR Block First\nWrite a 2–3 sentence direct answer to the article's core question. Place it immediately after the H1 in a blockquote. This is the first block AI engines attempt to extract.\n\n### Step 2: Build the Heading Skeleton\nSet H1, H2s (4–6), and H3s before writing any body content. The first H2 must be a \"What Is\" section with a clean definition sentence as its opening line.\n\n### Step 3: Write Body Sections\nFollow the section order: What Is → Why It Matters → How It Works (with H3 sub-concepts) → Practical Steps → Common Mistakes → FAQ → Conclusion.\n\n### Step 4: Write 5 FAQ Entries\nUse long-tail and secondary keywords as questions. Each answer must be under 50 words and self-contained — readable without any surrounding context.\n\n### Step 5: Run AEO and SEO Checklists\nVerify TL;DR presence, definition sentence, FAQ count, keyword placement, and heading structure before outputting.\n\n## Examples\n\n### Example: TL;DR Block\nHow to Manage a Remote Engineering Team\n\nTL;DR: Managing a remote engineering team requires async\ncommunication tools, clear documentation standards, and\ntimezone-aware sprint planning. Teams that nail these three\nareas ship consistently regardless of where members are located.\n\n\n### Example: FAQ Section\nQ: What is the biggest challenge of remote engineering teams?\nA: Async communication. Without shared hours, decisions slow down\nand context gets lost. Teams that document decisions in writing\nand use structured standup tools close this gap fastest.\nQ: How do you run a daily standup with a remote team?\nA: Use async video or text standups posted at the start of each\nmember's day. Tools like Loom or Slack threads work well.\nAvoid live calls across more than 2 timezones.\n\n## Best Practices\n\n- ✅ **Do:** Write the TL;DR block before writing anything else — it anchors the article\n- ✅ **Do:** Make the \"What Is\" definition sentence extractable on its own — one clean sentence\n- ✅ **Do:** Use secondary keywords as FAQ questions to capture long-tail traffic\n- ❌ **Don't:** Write FAQ answers longer than 50 words — AI engines skip long answers\n- ❌ **Don't:** Use duplicate H2 headings anywhere in the article\n- ❌ **Don't:** Skip the comparison table if the topic involves comparing options\n\n## Common Pitfalls\n\n- **Problem:** TL;DR block is too vague to be extracted as a direct answer\n  **Solution:** The TL;DR must answer the article's core question in 2–3 sentences. If it doesn't answer a specific question, rewrite it.\n\n- **Problem:** FAQ answers reference \"as mentioned above\" or other context\n  **Solution:** Every FAQ answer must stand completely alone — no references to other parts of the article.\n\n## Related Skills\n\n- `@seo-aeo-content-cluster` — provides the topic and keyword for this article\n- `@seo-aeo-content-quality-auditor` — audits the completed post for SEO and AEO signals\n- `@seo-aeo-internal-linking` — maps links between this post and related pages\n\n## Additional Resources\n\n- [SEO-AEO Engine Repository](https:\u002F\u002Fgithub.com\u002Fmrprewsh\u002Fseo-aeo-engine)\n- [Full Blog Writer SKILL.md](https:\u002F\u002Fgithub.com\u002Fmrprewsh\u002Fseo-aeo-engine\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fblog-writer\u002FSKILL.md)\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"safe","community","2026-04-01","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fseo-aeo-blog-writer",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill seo-aeo-blog-writer",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill seo-aeo-blog-writer",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill seo-aeo-blog-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fseo-aeo-blog-writer\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"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":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\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":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\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":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\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":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\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":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]