These skills work together as a content + web pipeline. A typical flow: pull real data → set the brand system → build the site & location pages → write articles → audit before publishing.

data (ambrose-insurance-data) → brand (brand-design-kit) → site (insurance-website-builder + location-page-factory) → articles (medicare / aca / life / generic blog-post-writer) → audit (seo-aeo-page-audit).

medicare-blog-writer

What it does: Researches, writes, verifies and tests a complete Medicare blog article — Original Medicare (Parts A/B), Medicare Advantage (Part C), Medigap/Supplement, Part D, eligibility, enrollment periods, costs. Answer-first long-form (3,000–8,000 words), with TL;DR, table of contents, verified statistics, charts, FAQ, author bio, sources, related articles, meta/canonical/Open Graph, JSON-LD schema, image alt — in your brand colors. Self-reviews, builds/previews to confirm charts render, then runs an embedded SEO+AEO checklist.

Compliance: YMYL — never guesses a number, cites primary sources, enforces CMS Medicare marketing rules (TPMO + non-affiliation, no prohibited superlatives), always states the plan year.

Use when: "write a Medicare article", "Medicare Advantage / Medigap / Part D / AEP / turning 65".

aca-blog-writer

What it does: The same complete article pipeline for ACA / Health Insurance Marketplace content — individual & family plans, metal tiers (Bronze/Silver/Gold/Platinum), premium tax credits/subsidies, cost-sharing reductions, eligibility, Open Enrollment & Special Enrollment, and alternatives (ICHRA; short-term caveats).

Compliance: YMYL — directs readers to HealthCare.gov / state Marketplaces, states income & plan-year caveats, no individualized advice.

Use when: "write an ACA / Marketplace / Obamacare article", "subsidies", "Open Enrollment", "metal tiers".

life-insurance-blog-writer

What it does: The same pipeline for life-insurance content — term, whole, universal/IUL, final expense/burial, group vs individual, riders, underwriting, beneficiaries, and how-much-coverage needs analysis.

Compliance: YMYL, state-regulated — no guaranteed-returns/investment claims, notes that underwriting varies.

Use when: "write a life insurance article", "term vs whole life", "final expense", "IUL", "how much life insurance".

blog-post-writer

What it does: The niche-agnostic master writer for any website or topic. Picks a trending/high-intent topic, rotates content categories (explainer, how-to, comparison, cost, timely, myths, news, data/trends), and produces answer-first long-form with TOC, TL;DR, verified stats, charts, FAQ, author bio, sources, related articles and a clear CTA — with full SEO+AEO (meta, canonical, Open Graph + Twitter Card, JSON-LD schema, alt text). The niche skills above defer to this for structure, length, SEO/AEO and testing.

Use when: "write a blog post", "draft an article", "write about X" (non-insurance or general topics).

ambrose-insurance-data

What it does: Fetches REAL, citable data from the Ambrose Insurance Brain MCP for content and research — Medicare, ACA/Healthcare.gov, life, ICHRA/HRA, Medicaid, county health figures, drug prices, provider counts, program rules. It maps each Brain tool to the blog use case it serves and turns results into cited stat callouts, charts and comparison tables.

Use when: you are writing or researching insurance content and need a real statistic, premium, plan count, or source — prefer this over inventing numbers. Pairs with the blog writers and the SEO/AEO audit.

brand-design-kit

What it does: Generates a complete brand + design system for an insurance agency website — brand-name treatment, an accessible color palette, typography (heading + body), logo direction, spacing scale, and the core UI component set (buttons, cards, stat row, chart, FAQ accordion, CTA band), plus a tone/voice guide. It writes a single source of truth (BRAND.md + design tokens) that the website builder and the blog writers all read. No image-generation dependency (logos/photos are bring-your-own).

Use when: "brand kit", "design system", "brand tokens", "colors and fonts for <brand>" — it's Step 0 before building the site.

insurance-website-builder

What it does: Designs and builds a complete, premium, multi-page insurance agency website (Medicare, ACA/health, life, final expense, ICHRA, P&C) on Astro, deploy-ready for Cloudflare Pages — home, about, service/plan pages, location pages, contact, blog index — with the generated design system, conversion-optimized compliant copy, the SAA Four-Pillar AI Citation Standard on every page (Article/Org "Data Desk" author + FAQPage + Dataset + llms.txt + WebMCP), GHL lead capture and accessibility.

Pairs with: brand-design-kit (visual system) and location-page-factory (local pages); run seo-aeo-page-audit before publishing. YMYL — cites authoritative/.gov sources, includes disclaimers.

Use when: "build an insurance website", "agency site", "new Medicare/ACA/life site", "website builder".

location-page-factory

What it does: Generates high-quality, compliant local-SEO location pages (one per city/county/service area) on Astro — each genuinely localized with REAL local data (county health, plan counts, demographics) from The Brain, the Four-Pillar AI Citation Standard, and the right geo schema stack (LocalBusiness + GovernmentService + Place + FAQPage + BreadcrumbList + Dataset). Built to avoid thin/doorway/near-duplicate pages.

Use when: "location pages", "city pages", "service-area pages", "local SEO pages for <brand>".

seo-aeo-page-audit

What it does: Audits a single web page or article for search (SEO) and answer-engine (AEO/GEO) readiness — title/meta, canonical, headings, content depth, internal/external links, images/alt, structured data, Core Web Vitals, indexability, duplicate-content risk, and search-engine spam-policy compliance. Produces a prioritized pass/fail report with concrete fixes. Works on any stack.

Use when: right after creating or editing a page — "check SEO", "audit this page", "is this ready to publish", "AEO check", "pre-publish review".

How to use them

1
See them on the Tools page — click Preview to read any skill's full playbook.
2
On an agent or team, open the Tools tab and tick the skills you want it to use.
3
Ask in chat (or via a sequence/routine, the team MCP, or the GHL webhook) — e.g. "Write a Medicare AEP article" — and the agent follows the skill's playbook.