Agent-Skills.md

Agent Skills: Blog Writer

Create category-aware, AEO-optimized blog posts for Lightfast. Use when writing technology deep-dives, company announcements, or product launches.

UncategorizedID: lightfastai/lightfast/blog-writer

Repository

lightfastai/lightfast
lightfastaiLicense: NOASSERTION
142

Install this agent skill to your local

pnpm dlx add-skill https://github.com/lightfastai/lightfast/tree/HEAD/.agents/skills/blog-writer

Skill Files

Browse the full folder contents for blog-writer.

Download Skill

Loading file tree…

.agents/skills/blog-writer/SKILL.md

Skill Metadata

Name
blog-writer
Description
Create category-aware, AEO-optimized blog posts for Lightfast. Use when writing technology deep-dives, company announcements, or product launches.

Blog Writer

Create clear, accurate blog posts that help developers understand Lightfast capabilities and industry trends.

Critical: Accuracy Over Marketing

Before writing anything:

  1. Verify every claim:

    • If you cite a number, confirm the source
    • If you mention a feature, confirm it exists in production
    • When uncertain, ask for clarification

  2. Never oversell:

    • Disclose limitations: "Currently supports X; Y coming in vZ"
    • Be honest about beta status and rollout timelines

  3. Match category voice:

    • Engineering: Technical authority, data-driven
    • Company: Visionary, category-defining
    • Product: Problem-solver, benefit-oriented
    • Tutorial: Step-by-step, practical
    • Research: Data-driven, methodology-first

Writing Guidelines

  1. Concise & scannable: Match category word counts
  2. Lead with value: Start with what readers gain
  3. Be transparent: Mention beta status, limitations
  4. Active voice: "You can now..." not "Users are able to..."
  5. No emoji: Professional tone
  6. Include TL;DR: 20-300 chars for AI citation (in frontmatter tldr field)
  7. FAQ section: 3-5 questions matching search queries (in frontmatter faq[])
  8. Code examples: Required for Engineering posts

Workflow

  1. Detect category from input or ask if unclear
  2. Load category style from resources/categories/{category}.md
  3. Research topic using web-search-researcher agent
  4. Draft following category template and templates
  5. Add AEO elements per aeo-requirements
  6. Review with checklist

Quick Reference

Category Selection

| Category | Use When | Audience | |----------|----------|----------| | Engineering | Technical deep-dives, architecture, research | Developers, engineers | | Company | Funding, partnerships, events, hiring | Executives, investors | | Product | Feature launches, updates, tutorials | Customers, prospects | | Tutorial | Step-by-step how-tos, guides | Developers learning | | Research | Data analysis, findings, benchmarks | Engineering leaders |

Do

  • Include code examples (Engineering/Tutorial)
  • Use "shift from/to" narratives (Company)
  • Lead with pain point (Product)
  • Link to 3-5 related docs

Don't

  • Marketing buzzwords without substance
  • Claims without verification
  • Long paragraphs (keep sections scannable)
  • Generic corporate speak

Output

Save drafts to: thoughts/blog/{YYYY-MM-DD-slug}.md

Required Frontmatter Fields

Every draft MUST include (maps to BlogPostSchema in apps/www/src/lib/content-schemas.ts):

  • title (core)
  • description (150-160 chars — this is the meta description)
  • keywords[] (min 3 — first entry is primary keyword)
  • ogTitle, ogDescription, ogImage (social/OG)
  • authors[] (structured array with name, url, twitterHandle)
  • publishedAt, updatedAt (ISO datetimes)
  • category (engineering | product | company | tutorial | research)
  • readingTimeMinutes (integer)
  • featured (boolean)
  • tldr (20-300 chars)
  • faq[] (min 1 entry)
  • _draft: true (traceability)

See resources/templates.md for complete frontmatter template.

Resources