[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ENN0JB3S04VG17QNQYENJM":3,"skill-same:01M7ENN0JB3S04VG17QNQYENJM":54},{"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":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":47},"01M7ENN0JB3S04VG17QNQYENJM","blog-write",null,"Write new blog articles from scratch optimized for Google rankings and AI citations. Generates full articles with template selection, answer-first formatting, Key Takeaways summary box, information gain markers, evidence-backed explanations, sourced statistics, Pixabay\u002FUnsplash images, built-in SVG chart generation, optional FAQ sections, internal linking zones, and proper heading hierarchy. Supports MDX, markdown, and HTML output. Use when user says \"write blog\", \"new blog post\", \"create article\", \"write about\", \"draft blog\", \"generate blog post\".","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-imp-blog-write\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: blog-write\ndescription: >\n  Write new blog articles from scratch optimized for Google rankings and AI\n  citations. Generates full articles with template selection, answer-first\n  formatting, Key Takeaways summary box, information gain markers, evidence-backed explanations, sourced\n  statistics, Pixabay\u002FUnsplash images, built-in SVG chart generation, optional FAQ sections,\n  internal linking zones, and proper heading hierarchy. Supports MDX, markdown,\n  and HTML output.\n  Use when user says \"write blog\", \"new blog post\", \"create article\",\n  \"write about\", \"draft blog\", \"generate blog post\".\nuser-invokable: true\nargument-hint: \"\u003Ctopic>\"\nlicense: MIT\n---\n\n# Blog Writer: New Article Generation\n\nWrites complete blog articles from a topic, brief, or outline. Every article\nfollows the 6 pillars of dual optimization (Google rankings + AI citations).\n\n**Key references** (paths relative to repo root; references live in the\nmain `blog` skill's references directory, not in `blog-write\u002F`):\n\n- `skills\u002Fblog\u002Freferences\u002Fsynthesis-contract.md`: 6 LAWs for synthesis output (v1.8.0; applies whenever the article embeds research-synthesis prose)\n- `skills\u002Fblog\u002Freferences\u002Fcontent-templates.md`: Template selection guide and usage\n- `skills\u002Fblog\u002Freferences\u002Fquality-scoring.md`: 5-category scoring (Content 30, SEO 25, E-E-A-T 15, Technical 15, AI Citation 15)\n- `skills\u002Fblog\u002Freferences\u002Feeat-signals.md`: Experience, expertise, authority, trust markers\n- `skills\u002Fblog\u002Freferences\u002Finternal-linking.md`: Linking strategy and anchor text rules\n- `skills\u002Fblog\u002Freferences\u002Fvisual-media.md`: Image sourcing and chart styling\n- `skills\u002Fblog-write\u002Freferences\u002Fdelivery.md`: delivery contract steps and summary template for this sub-skill\n\n## Workflow\n\n### Phase 0: Surface Targeting (do this BEFORE research)\n\nDecide which of the FLOW 5 surfaces this post is meant to win. The choice\nshapes structure, length, citation density, and call-to-action. The 5 surfaces\nin 2026:\n\n1. Owned site (organic Google ranking)\n2. SERP including AI Overviews\n3. AI assistant citations (ChatGPT, Perplexity, Claude, Gemini, Copilot, You.com)\n4. Local pack (out of scope for blog content; use claude-seo for local)\n5. Communities and video (Reddit, YouTube, LinkedIn, Quora, niche forums)\n\nMost posts target surfaces 1, 2, and 3 by default. If the same query also\nsurfaces in a community (Reddit thread, YouTube comment), apply dual-surface\nthinking: optimize the post for extraction AND plan a community echo (covered\nin `\u002Fblog repurpose`).\n\nFor a deeper surface-by-surface workflow, see\n`skills\u002Fblog\u002Freferences\u002Fflow-alignment.md` and `\u002Fblog flow find`.\n\n### Phase 1: Topic Understanding\n\n1. **Clarify the topic** - If the user provides just a topic, ask:\n   - Target audience (who is this for?)\n   - Primary keyword \u002F search intent\n   - Desired word count (default: 2,000-2,500 words)\n   - Platform\u002Fformat (MDX, markdown, HTML - auto-detect if in a project)\n2. **If a brief exists** - Load it and skip to Phase 1.5\n\n### Phase 1.5: Template Selection\n\nSelect the appropriate content template from the 12 templates in\n`skills\u002Fblog\u002Ftemplates\u002F` (the main `blog` skill owns the templates directory).\n\n1. **Auto-detect content type** from the topic and search intent:\n   | Signal | Template |\n   |--------|----------|\n   | \"How to...\", process, steps | `how-to-guide` |\n   | \"Best X\", \"Top N\", list format | `listicle` |\n   | Client result, before\u002Fafter, metrics | `case-study` |\n   | \"X vs Y\", comparison, alternatives | `comparison` |\n   | Broad topic, comprehensive guide | `pillar-page` |\n   | \"Is X worth it\", product evaluation | `product-review` |\n   | Opinion, prediction, industry take | `thought-leadership` |\n   | Expert quotes, multi-source collection | `roundup` |\n   | Code walkthrough, tool demo, technical | `tutorial` |\n   | Breaking news, algorithm update, event | `news-analysis` |\n   | Survey results, experiment, original data | `data-research` |\n   | Q&A, knowledge base, \"What is X\" | `faq-knowledge` |\n\n2. **Load the matching template**: Read from `skills\u002Fblog\u002Ftemplates\u002F\u003Ctype>.md`\n3. **Adapt the outline** - Use the template's section structure, heading patterns,\n   and word count guidance to shape Phase 3's outline\n4. **Fallback** - If no template clearly fits, use the generic outline structure\n   in Phase 3 below. Inform the user which template was selected (or that none matched).\n\nSee `skills\u002Fblog\u002Freferences\u002Fcontent-templates.md` for detailed selection criteria and intent mapping.\n\n### Phase 2: Research\n\nSpawn a `blog-researcher` agent (or do inline research with WebSearch):\n\n1. **Find 8-12 current statistics** (2025-2026 data preferred)\n   - Search: `[topic] study 2025 2026 data statistics`\n   - Prioritize tier 1-3 sources (see `skills\u002Fblog\u002Freferences\u002Fquality-scoring.md`)\n   - Record: statistic, source name, URL, date, methodology\n2. **Find a cover image** (wide, high-quality, topic-relevant):\n   - Prefer original screenshots, product visuals, diagrams, or data graphics when available\n   - For stock, use official APIs such as Openverse, Unsplash, Pexels, or Pixabay so license, creator, source URL, and download URL are captured\n   - Download approved assets into the draft folder, store attribution, and never hotlink arbitrary CDN URLs\n   - Reject `javascript:`, `data:`, and `file:` image URLs\n   - Target dimensions: 1200x630 (OG-compatible) or 1920x1080\n   - Or generate a custom SVG cover via `blog-chart` (text-on-gradient with key stat)\n   - Or generate a custom AI image via `blog-image`; prefer `gemini-3.1-flash-image`, then `gemini-3.1-flash-lite-image` or `gemini-3-pro-image` when available, and record the model ID\n   - See `skills\u002Fblog\u002Freferences\u002Fvisual-media.md` for cover image sizing details\n3. **Find 3-5 inline images** from open-source platforms:\n   - Use official APIs or Openverse search; keep license, creator, source URL, and retrieval date with each asset\n   - Download images locally and reference local paths in the draft\n   - Validate final URLs with the delivery contract SSRF rules before download\n4. **Plan 2-4 data visualizations** from researched statistics\n   - Select diverse chart types (see `skills\u002Fblog\u002Freferences\u002Fvisual-media.md`)\n   - Map data points to chart formats\n5. **AI image generation** (optional, if `blog-image` is available):\n   - If stock photo results are insufficient (\u003C 3 good matches) or topic is too niche\n   - Generate custom hero image and\u002For inline illustrations via `blog-image` sub-skill\n   - Record prompt, provider, and model ID; stock photos remain available, but original and data visuals are preferred when they better serve the topic\n6. **NotebookLM research** (optional, if user has relevant notebooks):\n   - If the user mentions a NotebookLM notebook or the topic aligns with a configured notebook\n   - Query via `blog-notebooklm` for source-grounded data from user-uploaded documents\n   - Inherit the source tier from the underlying document provenance; user's own primary documents can be Tier 1, while copied secondary sources keep their original tier\n   - Falls back silently if not configured or not authenticated\n7. **Find relevant YouTube videos** (2-3 per post):\n   - Use `blog-google` youtube command or WebSearch `site:youtube.com [topic] [year]`\n   - Apply quality criteria from `skills\u002Fblog\u002Freferences\u002Fvideo-embeds.md` (min score 50\u002F100)\n   - Select 2-3 best videos. Falls back silently if none found.\n\n### Phase 3: Outline Generation\n\nCreate a structured outline before writing. If a template was loaded in Phase 1.5,\nadapt this skeleton to match the template's section structure:\n\n```\n# [Title as Question - Include Primary Keyword]\n\n## Introduction (100-150 words)\n- Open with the reader's problem, a useful finding, a concrete example, or an\n  optional verified statistic when evidence makes that the strongest hook\n- Problem\u002Fopportunity statement\n- What the reader will learn\n\n> **Key Takeaways**\n> - [Core finding with statistic and source]\n> - [Second key insight or recommendation]\n> - [Third actionable takeaway]\n> (3-5 concise bullets when a summary helps this content type)\n\n## H2: [Intent-Matched Heading]\n- Clear section point with verified support where needed\n- Supporting evidence\n- [Image placement]\n- Practical advice\n- [EVIDENCE-BACKED EXPLANATION placeholder]\n- [INTERNAL-LINK: anchor text → target description]\n\n## H2: [Intent-Matched Heading]\n- Answer-first paragraph\n- [Chart: type + data description]\n- Analysis and implications\n- [EVIDENCE-BACKED EXPLANATION placeholder]\n- [INTERNAL-LINK: anchor text → target description]\n\n## H2: [Intent-Matched Heading]\n- Answer-first paragraph\n- Real-world example or case study\n- [Image placement]\n- [EVIDENCE-BACKED EXPLANATION placeholder]\n\n## H2: [Intent-Matched Heading]\n- Answer-first paragraph\n- [Chart: type + data description]\n- Step-by-step guidance\n- [EVIDENCE-BACKED EXPLANATION placeholder]\n- [INTERNAL-LINK: anchor text → target description]\n\n## H2: [Intent-Matched Heading]\n- Answer-first paragraph\n- Forward-looking analysis\n\n## [CTA Section or Inline Placement]\n- See `skills\u002Fblog\u002Freferences\u002Fcta-placement.md` for placement rules by content type\n- Place CTA after value delivery, not at arbitrary positions\n- Single focused CTA per post (266% more conversions)\n- [CTA: contextual call-to-action matching article topic]\n\n## Optional FAQ Section (only when real reader questions warrant it)\n- [INTERNAL-LINK: anchor text → detailed content]\n\n## Conclusion (100-150 words)\n- Key takeaways (bulleted)\n- Call to action\n- [INTERNAL-LINK: anchor text → next logical content]\n```\n\nPresent the outline to the user for approval before writing.\n\n**Visual element pacing**: Insert `[IMAGE]`, `[CHART]`, `[VIDEO]`, or `[CALLOUT]` markers\nevery 300-500 words. Alternate types (no consecutive same-type). See\n`skills\u002Fblog\u002Freferences\u002Fcontent-rules.md` Visual Rhythm section and\n`skills\u002Fblog\u002Freferences\u002Fcta-placement.md` for CTA positioning.\n\n### Phase 4: Chart Generation (Built-In)\n\nWhen the researcher identifies chart-worthy data (3+ comparable metrics, trend data,\nbefore\u002Fafter comparisons):\n\n1. Select chart type using the diversity rule (no repeated types per post)\n2. Invoke `blog-chart` sub-skill with: chart type, title, data values, source, platform format\n3. Embed the returned SVG directly in the post within a `\u003Cfigure>` wrapper\n4. Target 2-4 charts per 2,000-word post\n5. Distribute charts evenly - never cluster them\n\nSee `skills\u002Fblog\u002Freferences\u002Fvisual-media.md` for chart type selection and styling rules.\n\n### Phase 5: Content Writing\n\nWrite the full article following these rules:\n\n#### 5a. Frontmatter\n```yaml\n---\ntitle: \"[Clear title that identifies the page and matches search intent]\"\ndescription: \"[Accurate, page-specific summary of the visible content]\"\ncoverImage: \"[URL from Pixabay\u002FUnsplash\u002FPexels or generated SVG path]\"\ncoverImageAlt: \"[Descriptive sentence about the cover image]\"\nogImage: \"[Same as coverImage, or custom OG image URL]\"\ndate: \"YYYY-MM-DD\"\nlastUpdated: \"YYYY-MM-DD\"\nauthor: \"[Author name]\"\ntags: [\"keyword1\", \"keyword2\", \"keyword3\"]\n---\n```\n\nIf the platform uses a different field name (e.g., `image`, `hero`, `thumbnail`),\nadapt to match the project's existing frontmatter convention.\n\n#### 5b. Summary Box (Key Takeaways)\n\nImmediately after the introduction (before the first H2 body section), add a summary box:\n\n```markdown\n> **Key Takeaways**\n> - [Core finding with verified support when needed]\n> - [Second key insight or recommendation]\n> - [Third actionable takeaway]\n```\n\nRequirements:\n- 3-5 concise bullet points sized to the material\n- Must be self-contained - understandable without reading the article\n- Use statistics only when material to the summary and verified\n- State the key finding, recommendation, or answer\n- Default label: \"Key Takeaways\". If a persona is active, use the persona's summary_label\n- Backward compatible: accept existing TL;DR boxes during rewrites\n\n#### 5c. Purpose-First Formatting (Critical)\nState the point of important sections early, then supply the context and\nverified evidence the claim needs. Do not force statistics or fixed lengths.\n\nPattern:\n```markdown\n## How Does X Impact Y in 2026?\n\n[Stat from source] ([Source Name](url), year). [Direct answer to the heading\nquestion in 1-2 more sentences, explaining the implication and what this means\nfor the reader.]\n```\n\n**Source record for material public statistics:**\n\nRecord enough provenance for a reader or editor to verify the claim. Use the\npublication's citation style rather than forcing one sentence pattern.\n\n1. **Relevant date or study period.** Include it where recency or the measured\n   period changes the claim's meaning.\n\n2. **Identifiable source.** Name the publisher and document title when needed\n   to distinguish the source and place the citation close to the claim.\n\n3. **Retrievable support.** Keep a stable URL. Add a retrieval date for\n   changeable or undated sources, and record methodology or limitations when\n   they affect interpretation.\n\n**FLOW quality bar (drop or replace):**\nPublic claims must use verified sources OR stay qualitative. If a statistic\ncannot be verified, drop it. If it is contradicted by a more recent source,\nreplace it with the verified alternative. Do not soften vague language to\nkeep an unsourceable number.\n\nFor evidence-led optimization prompts (CTR audit, quality follow-up, schema,\nPAA rewording, ChatGPT visibility), see `\u002Fblog flow optimize`.\n\n#### 5d. Information Gain Markers\n\nUse information-gain markers as optional drafting annotations when the article\ncontains genuinely original data, transparent first-hand evidence, or\ndistinctive sourced synthesis. The evidence itself helps readers; the marker is\nnot a search-engine signal and earns no points by its presence.\n\nTag each with a comment or visible marker:\n\n- `[ORIGINAL DATA]` - Proprietary surveys, experiments, A\u002FB test results, case\n  study metrics the author collected first-hand\n- `[PERSONAL EXPERIENCE]` - First-hand observations, lessons learned from direct\n  involvement, \"when we tried X, Y happened\" narratives\n- `[UNIQUE INSIGHT]` - Analysis others haven't made, contrarian perspectives\n  backed by data, novel connections between existing research\n\nPlacement:\n- Weave into the body text naturally\n- Use as inline comments: `\u003C!-- [ORIGINAL DATA] -->` before the relevant paragraph\n- Or as visible callouts if the format supports it:\n  ```markdown\n  > **Our finding:** [original observation backed by specific data]\n  ```\n- Use only as many as the supported original material warrants.\n\n#### 5e. Evidence-Backed Explanations\n\nFor important reusable claims, create a self-contained, evidence-backed\nexplanation sized to the material.\n\nGuidance:\n- Self-contained and understandable in isolation\n- Contains a specific claim plus verified support when the claim needs it\n- Written in a declarative, quotable style\n- Placed within the H2 section body (not as a separate block)\n\nExample:\n```markdown\n[Verified source title], a [method or sample description] published on [date],\nfound [specific metric] for [audience or market] ([Source name](https:\u002F\u002Fexample.com\u002Ffull-report),\nretrieved YYYY-MM-DD). In practical terms, connect the evidence to one action\nthe reader should take before making a claim or changing a workflow.\n```\n\nDo not pad explanations to a fixed length or add them solely to earn readiness\npoints.\n\n#### 5f. Internal Linking Zones\n\nMark internal linking opportunities throughout the article using placeholder\nnotation. The user (or a follow-up pass) will resolve these to actual URLs.\n\nZone placement:\n- **Introduction** - Link to related pillar content or topic hub\n- **Each H2 section** - Link to supporting articles, deeper dives, related tools\n- **FAQ section** - Link answers to detailed content that expands on the answer\n- **Conclusion** - Link to the next logical piece of content the reader should consume\n\nFormat:\n```markdown\n[INTERNAL-LINK: anchor text → target description]\n```\n\nExample:\n```markdown\nFor a deeper dive into keyword clustering, see our\n[INTERNAL-LINK: complete guide to keyword clustering → pillar page on keyword research methodology].\n```\n\nTarget 5-10 internal link zones per 2,000-word post. Use descriptive anchor text\n(never \"click here\" or \"read more\"). See `skills\u002Fblog\u002Freferences\u002Finternal-linking.md` for\nanchor text rules and linking strategy.\n\n#### 5g. Paragraph Rules\n- Use paragraph and sentence lengths that fit the audience and material\n- Split passages when doing so improves comprehension, not to satisfy a quota\n- Start each paragraph with the most important information\n- Target Flesch Reading Ease: 60-70\n\n#### 5h. Heading Rules\n- One H1 (title only)\n- H2s for main sections; use question or declarative forms according to intent\n- H3s for subsections only - never skip levels\n- Keep heading terminology naturally consistent with the page topic; do not\n  enforce an exact-match keyword quota\n\n#### 5i. Image Embedding\n\nStandard markdown:\n```markdown\n![Descriptive alt text - topic keywords naturally](https:\u002F\u002Fcdn.pixabay.com\u002Fphoto\u002F...)\n```\n\nMDX with Next.js Image (if detected):\n```mdx\n![Descriptive alt text - topic keywords naturally](https:\u002F\u002Fcdn.pixabay.com\u002Fphoto\u002F...)\n```\n\n- Place images after H2 headings, before body text\n- Space evenly throughout the post (not clustered)\n- Alt text should be a full descriptive sentence\n\n#### 5j. Chart Embedding\n\nStandard markdown\u002FHTML:\n```html\n\u003Cfigure>\n  \u003Csvg viewBox=\"0 0 560 380\" ...>...\u003C\u002Fsvg>\n  \u003Cfigcaption>Source: [Source Name], [Year]\u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n```\n\nMDX format:\n```mdx\n\u003Cfigure className=\"chart-container\" style={{margin: '2.5rem 0', textAlign: 'center', padding: '1.5rem', borderRadius: '12px'}}>\n  \u003Csvg viewBox=\"0 0 560 380\" ...>...\u003C\u002Fsvg>\n\u003C\u002Ffigure>\n```\n\n#### 5k. Video Embedding\nEmbed YouTube videos using srcdoc lazy-loading pattern from `skills\u002Fblog\u002Freferences\u002Fvideo-embeds.md`.\nInclude aria-label, noscript fallback for AI crawlers. Place after relevant H2, 500+ words apart.\n\n#### 5l. Citation Format\nInline attribution (always):\n```markdown\nIn February 2026, Seer Interactive's AI Overview CTR tracker reported a 2.4% organic CTR on AI Overview SERPs ([Seer Interactive](https:\u002F\u002Fwww.seerinteractive.com\u002F), retrieved YYYY-MM-DD).\n```\n\n#### 5m. FAQ Section\nAdd FAQ items only when user questions warrant them. Answers should be complete\nand concise; include verified statistics only when relevant.\n\nFAQPage is optional entity markup only. Google FAQ rich results were fully retired for all sites on 2026-05-07, so do not make FAQ schema a core Google rich-result output or citation lever. Prioritize Article\u002FBlogPosting + Person + Organization + BreadcrumbList; emit FAQPage only when the platform already supports it and the questions genuinely help users.\n\nFor MDX with an optional FAQSchema component:\n```mdx\n\u003CFAQSchema faqs={[\n  { question: \"Question?\", answer: \"Complete answer with support where needed.\" },\n]} \u002F>\n```\n\nFor standard markdown:\n```markdown\n## Frequently Asked Questions\n\n### Question text here?\n\nAnswer completely, with source attribution where the claim needs it.\n```\n\n#### 5n. Internal Linking\n- 5-10 internal links per 2,000-word post\n- Link to relevant existing content naturally\n- Use descriptive anchor text (not \"click here\")\n\n### Phase 6: Quality Check\n\nBefore delivering, verify:\n\n#### Structure and Content\n1. Important claims state their point clearly and include verified support where needed\n2. Paragraph and sentence pacing suits the audience; length alone cannot block delivery\n3. All statistics have named tier 1-3 sources\n4. 2-4 charts with type diversity\n5. 3-5 inline images with descriptive alt text\n6. Cover image present in frontmatter (coverImage + ogImage)\n7. FAQ section present with 3-5 items when warranted by user questions\n8. Heading hierarchy is clean (H1 -> H2 -> H3)\n9. Meta description accurately and specifically summarizes the visible content\n\n#### New Element Verification\n10. Optional summary helps the reader and contains no unsupported claims\n11. Any information-gain markers point to supported original material\n12. Important reusable claims are self-contained and evidence-backed\n13. Internal linking zones marked in introduction, H2 sections, FAQ, and conclusion\n14. Project voice preferences reviewed where they improve clarity and fit\n\n#### Optional Editorial Voice Review\n15. **Sentence rhythm** - Vary sentence structure only where it improves clarity,\n    emphasis, or flow. Do not infer authorship from sentence patterns or enforce\n    fixed sentence-length bands.\n16. **Configured phrase review** - Review these project style-list terms in\n    context and replace them only when a clearer alternative fits:\n    - \"in today's digital landscape\", \"it's important to note\", \"dive into\"\n    - \"game-changer\", \"navigate the landscape\", \"revolutionize\", \"seamlessly\"\n    - \"cutting-edge\", \"harness the power of\", \"leverage\" (as verb)\n    - \"delve\", \"crucial\", \"elevate\", \"foster\", \"landscape\" (overused)\n    - \"multifaceted\", \"robust\", \"tapestry\", \"embark\"\n    - Full list in `agents\u002Fblog-writer.md`\n17. **Contractions** - Use contractions when they fit the selected voice. Their\n    presence or absence says nothing about authorship or Google performance.\n18. **Rhetorical questions** - Use them only when they help the reader reason\n    through a decision. There is no quota.\n19. **YouTube videos** - 2-3 embeds with lazy loading, aria-labels, and noscript fallback (see `skills\u002Fblog\u002Freferences\u002Fvideo-embeds.md`)\n\n### Phase 6.5: Delivery Contract Enforcement (v1.9.0)\nBefore Phase 7, run the 5-gate delivery contract (via `python3 scripts\u002Fblog_preflight.py` plus a BLOCKING `blog-reviewer` agent) per `skills\u002Fblog\u002Freferences\u002Fblog-delivery-contract.md` and the writer-specific checklist in `skills\u002Fblog-write\u002Freferences\u002Fdelivery.md`. Use `python3` for local scripts. The user is never the first reviewer; the gates are.\nOn any block, capture `\u003Cfolder>\u002Fpreflight-report.json`, re-dispatch the blog-writer agent with the diagnostic as input, and re-run the gated steps. Maximum 3 iterations. On the 3rd failure, stop and present the failure diagnostic instead of the draft.\n\n### Phase 7: Delivery\nPresent the completed article only after Phase 6.5 returns all gates passing. Include `\u003Cfolder>\u002Fpreview\u002F*.png` screenshots and the compact completion summary described in `skills\u002Fblog-write\u002Freferences\u002Fdelivery.md`.\n","# Blog Writer: New Article Generation\n\nWrites complete blog articles from a topic, brief, or outline. Every article\nfollows the 6 pillars of dual optimization (Google rankings + AI citations).\n\n**Key references** (paths relative to repo root; references live in the\nmain `blog` skill's references directory, not in `blog-write\u002F`):\n\n- `skills\u002Fblog\u002Freferences\u002Fsynthesis-contract.md`: 6 LAWs for synthesis output (v1.8.0; applies whenever the article embeds research-synthesis prose)\n- `skills\u002Fblog\u002Freferences\u002Fcontent-templates.md`: Template selection guide and usage\n- `skills\u002Fblog\u002Freferences\u002Fquality-scoring.md`: 5-category scoring (Content 30, SEO 25, E-E-A-T 15, Technical 15, AI Citation 15)\n- `skills\u002Fblog\u002Freferences\u002Feeat-signals.md`: Experience, expertise, authority, trust markers\n- `skills\u002Fblog\u002Freferences\u002Finternal-linking.md`: Linking strategy and anchor text rules\n- `skills\u002Fblog\u002Freferences\u002Fvisual-media.md`: Image sourcing and chart styling\n- `skills\u002Fblog-write\u002Freferences\u002Fdelivery.md`: delivery contract steps and summary template for this sub-skill\n\n## Workflow\n\n### Phase 0: Surface Targeting (do this BEFORE research)\n\nDecide which of the FLOW 5 surfaces this post is meant to win. The choice\nshapes structure, length, citation density, and call-to-action. The 5 surfaces\nin 2026:\n\n1. Owned site (organic Google ranking)\n2. SERP including AI Overviews\n3. AI assistant citations (ChatGPT, Perplexity, Claude, Gemini, Copilot, You.com)\n4. Local pack (out of scope for blog content; use claude-seo for local)\n5. Communities and video (Reddit, YouTube, LinkedIn, Quora, niche forums)\n\nMost posts target surfaces 1, 2, and 3 by default. If the same query also\nsurfaces in a community (Reddit thread, YouTube comment), apply dual-surface\nthinking: optimize the post for extraction AND plan a community echo (covered\nin `\u002Fblog repurpose`).\n\nFor a deeper surface-by-surface workflow, see\n`skills\u002Fblog\u002Freferences\u002Fflow-alignment.md` and `\u002Fblog flow find`.\n\n### Phase 1: Topic Understanding\n\n1. **Clarify the topic** - If the user provides just a topic, ask:\n   - Target audience (who is this for?)\n   - Primary keyword \u002F search intent\n   - Desired word count (default: 2,000-2,500 words)\n   - Platform\u002Fformat (MDX, markdown, HTML - auto-detect if in a project)\n2. **If a brief exists** - Load it and skip to Phase 1.5\n\n### Phase 1.5: Template Selection\n\nSelect the appropriate content template from the 12 templates in\n`skills\u002Fblog\u002Ftemplates\u002F` (the main `blog` skill owns the templates directory).\n\n1. **Auto-detect content type** from the topic and search intent:\n   | Signal | Template |\n   |--------|----------|\n   | \"How to...\", process, steps | `how-to-guide` |\n   | \"Best X\", \"Top N\", list format | `listicle` |\n   | Client result, before\u002Fafter, metrics | `case-study` |\n   | \"X vs Y\", comparison, alternatives | `comparison` |\n   | Broad topic, comprehensive guide | `pillar-page` |\n   | \"Is X worth it\", product evaluation | `product-review` |\n   | Opinion, prediction, industry take | `thought-leadership` |\n   | Expert quotes, multi-source collection | `roundup` |\n   | Code walkthrough, tool demo, technical | `tutorial` |\n   | Breaking news, algorithm update, event | `news-analysis` |\n   | Survey results, experiment, original data | `data-research` |\n   | Q&A, knowledge base, \"What is X\" | `faq-knowledge` |\n\n2. **Load the matching template**: Read from `skills\u002Fblog\u002Ftemplates\u002F\u003Ctype>.md`\n3. **Adapt the outline** - Use the template's section structure, heading patterns,\n   and word count guidance to shape Phase 3's outline\n4. **Fallback** - If no template clearly fits, use the generic outline structure\n   in Phase 3 below. Inform the user which template was selected (or that none matched).\n\nSee `skills\u002Fblog\u002Freferences\u002Fcontent-templates.md` for detailed selection criteria and intent mapping.\n\n### Phase 2: Research\n\nSpawn a `blog-researcher` agent (or do inline research with WebSearch):\n\n1. **Find 8-12 current statistics** (2025-2026 data preferred)\n   - Search: `[topic] study 2025 2026 data statistics`\n   - Prioritize tier 1-3 sources (see `skills\u002Fblog\u002Freferences\u002Fquality-scoring.md`)\n   - Record: statistic, source name, URL, date, methodology\n2. **Find a cover image** (wide, high-quality, topic-relevant):\n   - Prefer original screenshots, product visuals, diagrams, or data graphics when available\n   - For stock, use official APIs such as Openverse, Unsplash, Pexels, or Pixabay so license, creator, source URL, and download URL are captured\n   - Download approved assets into the draft folder, store attribution, and never hotlink arbitrary CDN URLs\n   - Reject `javascript:`, `data:`, and `file:` image URLs\n   - Target dimensions: 1200x630 (OG-compatible) or 1920x1080\n   - Or generate a custom SVG cover via `blog-chart` (text-on-gradient with key stat)\n   - Or generate a custom AI image via `blog-image`; prefer `gemini-3.1-flash-image`, then `gemini-3.1-flash-lite-image` or `gemini-3-pro-image` when available, and record the model ID\n   - See `skills\u002Fblog\u002Freferences\u002Fvisual-media.md` for cover image sizing details\n3. **Find 3-5 inline images** from open-source platforms:\n   - Use official APIs or Openverse search; keep license, creator, source URL, and retrieval date with each asset\n   - Download images locally and reference local paths in the draft\n   - Validate final URLs with the delivery contract SSRF rules before download\n4. **Plan 2-4 data visualizations** from researched statistics\n   - Select diverse chart types (see `skills\u002Fblog\u002Freferences\u002Fvisual-media.md`)\n   - Map data points to chart formats\n5. **AI image generation** (optional, if `blog-image` is available):\n   - If stock photo results are insufficient (\u003C 3 good matches) or topic is too niche\n   - Generate custom hero image and\u002For inline illustrations via `blog-image` sub-skill\n   - Record prompt, provider, and model ID; stock photos remain available, but original and data visuals are preferred when they better serve the topic\n6. **NotebookLM research** (optional, if user has relevant notebooks):\n   - If the user mentions a NotebookLM notebook or the topic aligns with a configured notebook\n   - Query via `blog-notebooklm` for source-grounded data from user-uploaded documents\n   - Inherit the source tier from the underlying document provenance; user's own primary documents can be Tier 1, while copied secondary sources keep their original tier\n   - Falls back silently if not configured or not authenticated\n7. **Find relevant YouTube videos** (2-3 per post):\n   - Use `blog-google` youtube command or WebSearch `site:youtube.com [topic] [year]`\n   - Apply quality criteria from `skills\u002Fblog\u002Freferences\u002Fvideo-embeds.md` (min score 50\u002F100)\n   - Select 2-3 best videos. Falls back silently if none found.\n\n### Phase 3: Outline Generation\n\nCreate a structured outline before writing. If a template was loaded in Phase 1.5,\nadapt this skeleton to match the template's section structure:\n\n```\n# [Title as Question - Include Primary Keyword]\n\n## Introduction (100-150 words)\n- Open with the reader's problem, a useful finding, a concrete example, or an\n  optional verified statistic when evidence makes that the strongest hook\n- Problem\u002Fopportunity statement\n- What the reader will learn\n\n> **Key Takeaways**\n> - [Core finding with statistic and source]\n> - [Second key insight or recommendation]\n> - [Third actionable takeaway]\n> (3-5 concise bullets when a summary helps this content type)\n\n## H2: [Intent-Matched Heading]\n- Clear section point with verified support where needed\n- Supporting evidence\n- [Image placement]\n- Practical advice\n- [EVIDENCE-BACKED EXPLANATION placeholder]\n- [INTERNAL-LINK: anchor text → target description]\n\n## H2: [Intent-Matched Heading]\n- Answer-first paragraph\n- [Chart: type + data description]\n- Analysis and implications\n- [EVIDENCE-BACKED EXPLANATION placeholder]\n- [INTERNAL-LINK: anchor text → target description]\n\n## H2: [Intent-Matched Heading]\n- Answer-first paragraph\n- Real-world example or case study\n- [Image placement]\n- [EVIDENCE-BACKED EXPLANATION placeholder]\n\n## H2: [Intent-Matched Heading]\n- Answer-first paragraph\n- [Chart: type + data description]\n- Step-by-step guidance\n- [EVIDENCE-BACKED EXPLANATION placeholder]\n- [INTERNAL-LINK: anchor text → target description]\n\n## H2: [Intent-Matched Heading]\n- Answer-first paragraph\n- Forward-looking analysis\n\n## [CTA Section or Inline Placement]\n- See `skills\u002Fblog\u002Freferences\u002Fcta-placement.md` for placement rules by content type\n- Place CTA after value delivery, not at arbitrary positions\n- Single focused CTA per post (266% more conversions)\n- [CTA: contextual call-to-action matching article topic]\n\n## Optional FAQ Section (only when real reader questions warrant it)\n- [INTERNAL-LINK: anchor text → detailed content]\n\n## Conclusion (100-150 words)\n- Key takeaways (bulleted)\n- Call to action\n- [INTERNAL-LINK: anchor text → next logical content]\n```\n\nPresent the outline to the user for approval before writing.\n\n**Visual element pacing**: Insert `[IMAGE]`, `[CHART]`, `[VIDEO]`, or `[CALLOUT]` markers\nevery 300-500 words. Alternate types (no consecutive same-type). See\n`skills\u002Fblog\u002Freferences\u002Fcontent-rules.md` Visual Rhythm section and\n`skills\u002Fblog\u002Freferences\u002Fcta-placement.md` for CTA positioning.\n\n### Phase 4: Chart Generation (Built-In)\n\nWhen the researcher identifies chart-worthy data (3+ comparable metrics, trend data,\nbefore\u002Fafter comparisons):\n\n1. Select chart type using the diversity rule (no repeated types per post)\n2. Invoke `blog-chart` sub-skill with: chart type, title, data values, source, platform format\n3. Embed the returned SVG directly in the post within a `\u003Cfigure>` wrapper\n4. Target 2-4 charts per 2,000-word post\n5. Distribute charts evenly - never cluster them\n\nSee `skills\u002Fblog\u002Freferences\u002Fvisual-media.md` for chart type selection and styling rules.\n\n### Phase 5: Content Writing\n\nWrite the full article following these rules:\n\n#### 5a. Frontmatter\n```yaml\n---\ntitle: \"[Clear title that identifies the page and matches search intent]\"\ndescription: \"[Accurate, page-specific summary of the visible content]\"\ncoverImage: \"[URL from Pixabay\u002FUnsplash\u002FPexels or generated SVG path]\"\ncoverImageAlt: \"[Descriptive sentence about the cover image]\"\nogImage: \"[Same as coverImage, or custom OG image URL]\"\ndate: \"YYYY-MM-DD\"\nlastUpdated: \"YYYY-MM-DD\"\nauthor: \"[Author name]\"\ntags: [\"keyword1\", \"keyword2\", \"keyword3\"]\n---\n```\n\nIf the platform uses a different field name (e.g., `image`, `hero`, `thumbnail`),\nadapt to match the project's existing frontmatter convention.\n\n#### 5b. Summary Box (Key Takeaways)\n\nImmediately after the introduction (before the first H2 body section), add a summary box:\n\n```markdown\n> **Key Takeaways**\n> - [Core finding with verified support when needed]\n> - [Second key insight or recommendation]\n> - [Third actionable takeaway]\n```\n\nRequirements:\n- 3-5 concise bullet points sized to the material\n- Must be self-contained - understandable without reading the article\n- Use statistics only when material to the summary and verified\n- State the key finding, recommendation, or answer\n- Default label: \"Key Takeaways\". If a persona is active, use the persona's summary_label\n- Backward compatible: accept existing TL;DR boxes during rewrites\n\n#### 5c. Purpose-First Formatting (Critical)\nState the point of important sections early, then supply the context and\nverified evidence the claim needs. Do not force statistics or fixed lengths.\n\nPattern:\n```markdown\n## How Does X Impact Y in 2026?\n\n[Stat from source] ([Source Name](url), year). [Direct answer to the heading\nquestion in 1-2 more sentences, explaining the implication and what this means\nfor the reader.]\n```\n\n**Source record for material public statistics:**\n\nRecord enough provenance for a reader or editor to verify the claim. Use the\npublication's citation style rather than forcing one sentence pattern.\n\n1. **Relevant date or study period.** Include it where recency or the measured\n   period changes the claim's meaning.\n\n2. **Identifiable source.** Name the publisher and document title when needed\n   to distinguish the source and place the citation close to the claim.\n\n3. **Retrievable support.** Keep a stable URL. Add a retrieval date for\n   changeable or undated sources, and record methodology or limitations when\n   they affect interpretation.\n\n**FLOW quality bar (drop or replace):**\nPublic claims must use verified sources OR stay qualitative. If a statistic\ncannot be verified, drop it. If it is contradicted by a more recent source,\nreplace it with the verified alternative. Do not soften vague language to\nkeep an unsourceable number.\n\nFor evidence-led optimization prompts (CTR audit, quality follow-up, schema,\nPAA rewording, ChatGPT visibility), see `\u002Fblog flow optimize`.\n\n#### 5d. Information Gain Markers\n\nUse information-gain markers as optional drafting annotations when the article\ncontains genuinely original data, transparent first-hand evidence, or\ndistinctive sourced synthesis. The evidence itself helps readers; the marker is\nnot a search-engine signal and earns no points by its presence.\n\nTag each with a comment or visible marker:\n\n- `[ORIGINAL DATA]` - Proprietary surveys, experiments, A\u002FB test results, case\n  study metrics the author collected first-hand\n- `[PERSONAL EXPERIENCE]` - First-hand observations, lessons learned from direct\n  involvement, \"when we tried X, Y happened\" narratives\n- `[UNIQUE INSIGHT]` - Analysis others haven't made, contrarian perspectives\n  backed by data, novel connections between existing research\n\nPlacement:\n- Weave into the body text naturally\n- Use as inline comments: `\u003C!-- [ORIGINAL DATA] -->` before the relevant paragraph\n- Or as visible callouts if the format supports it:\n  ```markdown\n  > **Our finding:** [original observation backed by specific data]\n  ```\n- Use only as many as the supported original material warrants.\n\n#### 5e. Evidence-Backed Explanations\n\nFor important reusable claims, create a self-contained, evidence-backed\nexplanation sized to the material.\n\nGuidance:\n- Self-contained and understandable in isolation\n- Contains a specific claim plus verified support when the claim needs it\n- Written in a declarative, quotable style\n- Placed within the H2 section body (not as a separate block)\n\nExample:\n```markdown\n[Verified source title], a [method or sample description] published on [date],\nfound [specific metric] for [audience or market] ([Source name](https:\u002F\u002Fexample.com\u002Ffull-report),\nretrieved YYYY-MM-DD). In practical terms, connect the evidence to one action\nthe reader should take before making a claim or changing a workflow.\n```\n\nDo not pad explanations to a fixed length or add them solely to earn readiness\npoints.\n\n#### 5f. Internal Linking Zones\n\nMark internal linking opportunities throughout the article using placeholder\nnotation. The user (or a follow-up pass) will resolve these to actual URLs.\n\nZone placement:\n- **Introduction** - Link to related pillar content or topic hub\n- **Each H2 section** - Link to supporting articles, deeper dives, related tools\n- **FAQ section** - Link answers to detailed content that expands on the answer\n- **Conclusion** - Link to the next logical piece of content the reader should consume\n\nFormat:\n```markdown\n[INTERNAL-LINK: anchor text → target description]\n```\n\nExample:\n```markdown\nFor a deeper dive into keyword clustering, see our\n[INTERNAL-LINK: complete guide to keyword clustering → pillar page on keyword research methodology].\n```\n\nTarget 5-10 internal link zones per 2,000-word post. Use descriptive anchor text\n(never \"click here\" or \"read more\"). See `skills\u002Fblog\u002Freferences\u002Finternal-linking.md` for\nanchor text rules and linking strategy.\n\n#### 5g. Paragraph Rules\n- Use paragraph and sentence lengths that fit the audience and material\n- Split passages when doing so improves comprehension, not to satisfy a quota\n- Start each paragraph with the most important information\n- Target Flesch Reading Ease: 60-70\n\n#### 5h. Heading Rules\n- One H1 (title only)\n- H2s for main sections; use question or declarative forms according to intent\n- H3s for subsections only - never skip levels\n- Keep heading terminology naturally consistent with the page topic; do not\n  enforce an exact-match keyword quota\n\n#### 5i. Image Embedding\n\nStandard markdown:\n```markdown\n![Descriptive alt text - topic keywords naturally](https:\u002F\u002Fcdn.pixabay.com\u002Fphoto\u002F...)\n```\n\nMDX with Next.js Image (if detected):\n```mdx\n![Descriptive alt text - topic keywords naturally](https:\u002F\u002Fcdn.pixabay.com\u002Fphoto\u002F...)\n```\n\n- Place images after H2 headings, before body text\n- Space evenly throughout the post (not clustered)\n- Alt text should be a full descriptive sentence\n\n#### 5j. Chart Embedding\n\nStandard markdown\u002FHTML:\n```html\n\u003Cfigure>\n  \u003Csvg viewBox=\"0 0 560 380\" ...>...\u003C\u002Fsvg>\n  \u003Cfigcaption>Source: [Source Name], [Year]\u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n```\n\nMDX format:\n```mdx\n\u003Cfigure className=\"chart-container\" style={{margin: '2.5rem 0', textAlign: 'center', padding: '1.5rem', borderRadius: '12px'}}>\n  \u003Csvg viewBox=\"0 0 560 380\" ...>...\u003C\u002Fsvg>\n\u003C\u002Ffigure>\n```\n\n#### 5k. Video Embedding\nEmbed YouTube videos using srcdoc lazy-loading pattern from `skills\u002Fblog\u002Freferences\u002Fvideo-embeds.md`.\nInclude aria-label, noscript fallback for AI crawlers. Place after relevant H2, 500+ words apart.\n\n#### 5l. Citation Format\nInline attribution (always):\n```markdown\nIn February 2026, Seer Interactive's AI Overview CTR tracker reported a 2.4% organic CTR on AI Overview SERPs ([Seer Interactive](https:\u002F\u002Fwww.seerinteractive.com\u002F), retrieved YYYY-MM-DD).\n```\n\n#### 5m. FAQ Section\nAdd FAQ items only when user questions warrant them. Answers should be complete\nand concise; include verified statistics only when relevant.\n\nFAQPage is optional entity markup only. Google FAQ rich results were fully retired for all sites on 2026-05-07, so do not make FAQ schema a core Google rich-result output or citation lever. Prioritize Article\u002FBlogPosting + Person + Organization + BreadcrumbList; emit FAQPage only when the platform already supports it and the questions genuinely help users.\n\nFor MDX with an optional FAQSchema component:\n```mdx\n\u003CFAQSchema faqs={[\n  { question: \"Question?\", answer: \"Complete answer with support where needed.\" },\n]} \u002F>\n```\n\nFor standard markdown:\n```markdown\n## Frequently Asked Questions\n\n### Question text here?\n\nAnswer completely, with source attribution where the claim needs it.\n```\n\n#### 5n. Internal Linking\n- 5-10 internal links per 2,000-word post\n- Link to relevant existing content naturally\n- Use descriptive anchor text (not \"click here\")\n\n### Phase 6: Quality Check\n\nBefore delivering, verify:\n\n#### Structure and Content\n1. Important claims state their point clearly and include verified support where needed\n2. Paragraph and sentence pacing suits the audience; length alone cannot block delivery\n3. All statistics have named tier 1-3 sources\n4. 2-4 charts with type diversity\n5. 3-5 inline images with descriptive alt text\n6. Cover image present in frontmatter (coverImage + ogImage)\n7. FAQ section present with 3-5 items when warranted by user questions\n8. Heading hierarchy is clean (H1 -> H2 -> H3)\n9. Meta description accurately and specifically summarizes the visible content\n\n#### New Element Verification\n10. Optional summary helps the reader and contains no unsupported claims\n11. Any information-gain markers point to supported original material\n12. Important reusable claims are self-contained and evidence-backed\n13. Internal linking zones marked in introduction, H2 sections, FAQ, and conclusion\n14. Project voice preferences reviewed where they improve clarity and fit\n\n#### Optional Editorial Voice Review\n15. **Sentence rhythm** - Vary sentence structure only where it improves clarity,\n    emphasis, or flow. Do not infer authorship from sentence patterns or enforce\n    fixed sentence-length bands.\n16. **Configured phrase review** - Review these project style-list terms in\n    context and replace them only when a clearer alternative fits:\n    - \"in today's digital landscape\", \"it's important to note\", \"dive into\"\n    - \"game-changer\", \"navigate the landscape\", \"revolutionize\", \"seamlessly\"\n    - \"cutting-edge\", \"harness the power of\", \"leverage\" (as verb)\n    - \"delve\", \"crucial\", \"elevate\", \"foster\", \"landscape\" (overused)\n    - \"multifaceted\", \"robust\", \"tapestry\", \"embark\"\n    - Full list in `agents\u002Fblog-writer.md`\n17. **Contractions** - Use contractions when they fit the selected voice. Their\n    presence or absence says nothing about authorship or Google performance.\n18. **Rhetorical questions** - Use them only when they help the reader reason\n    through a decision. There is no quota.\n19. **YouTube videos** - 2-3 embeds with lazy loading, aria-labels, and noscript fallback (see `skills\u002Fblog\u002Freferences\u002Fvideo-embeds.md`)\n\n### Phase 6.5: Delivery Contract Enforcement (v1.9.0)\nBefore Phase 7, run the 5-gate delivery contract (via `python3 scripts\u002Fblog_preflight.py` plus a BLOCKING `blog-reviewer` agent) per `skills\u002Fblog\u002Freferences\u002Fblog-delivery-contract.md` and the writer-specific checklist in `skills\u002Fblog-write\u002Freferences\u002Fdelivery.md`. Use `python3` for local scripts. The user is never the first reviewer; the gates are.\nOn any block, capture `\u003Cfolder>\u002Fpreflight-report.json`, re-dispatch the blog-writer agent with the diagnostic as input, and re-run the gated steps. Maximum 3 iterations. On the 3rd failure, stop and present the failure diagnostic instead of the draft.\n\n### Phase 7: Delivery\nPresent the completed article only after Phase 6.5 returns all gates passing. Include `\u003Cfolder>\u002Fpreview\u002F*.png` screenshots and the compact completion summary described in `skills\u002Fblog-write\u002Freferences\u002Fdelivery.md`.\n",{"name":5,"license":15,"description":24,"argument-hint":25,"user-invokable":26},"Write new blog articles from scratch optimized for Google rankings and AI citations. Generates full articles with template selection, answer-first formatting, Key Takeaways summary box, information gain markers, evidence-backed explanations, sourced statistics, Pixabay\u002FUnsplash images, built-in SVG chart generation, optional FAQ sections, internal linking zones, and proper heading hierarchy. Supports MDX, markdown, and HTML output. Use when user says \"write blog\", \"new blog post\", \"create article\", \"write about\", \"draft blog\", \"generate blog post\".\n","\u003Ctopic>",true,"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-imp-blog-write",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":26},[37,40,43],{"tool":38,"command":39},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill blog-write",{"tool":41,"command":42},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill blog-write",{"tool":44,"command":45},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill blog-write","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-imp-blog-write\u002FSKILL.md",[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fdelivery.md","REFERENCE","参考文档",2867,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-imp-blog-write\u002Freferences\u002Fdelivery.md",[55,62,70,77,84,91],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\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":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]