blog-post

langchain-ai/deepagents · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/langchain-ai/deepagents --skill blog-post
0 commentsdiscussion
summary

Long-form blog post writing with research delegation, structured content templates, and AI-generated cover images.

  • Delegates research to subagents before writing, storing findings in markdown for reference and context
  • Enforces a five-part post structure: hook, context, main content (3–5 sections), practical application, and conclusion with call-to-action
  • Generates SEO-optimized cover images using detailed prompts covering subject, style, composition, color, and lighting
  • Outputs po
skill.md

Blog Post Writing Skill

Research First (Required)

Before writing any blog post, you MUST delegate research:

  1. Use the task tool with subagent_type: "researcher"
  2. In the description, specify BOTH the topic AND where to save:
task(
    subagent_type="researcher",
    description="Research [TOPIC]. Save findings to research/[slug].md"
)

Example:

task(
    subagent_type="researcher",
    description="Research the current state of AI agents in 2025. Save findings to research/ai-agents-2025.md"
)
  1. After research completes, read the findings file before writing

Output Structure (Required)

Every blog post MUST have both a post AND a cover image:

blogs/
└── <slug>/
    ├── post.md        # The blog post content
    └── hero.png       # REQUIRED: Generated cover image

Example: A post about "AI Agents in 2025" → blogs/ai-agents-2025/

You MUST complete both steps:

  1. Write the post to blogs/<slug>/post.md
  2. Generate a cover image using generate_image and save to blogs/<slug>/hero.png

A blog post is NOT complete without its cover image.

Blog Post Structure

Every blog post should follow this structure:

1. Hook (Opening)

  • Start with a compelling question, statistic, or statement
  • Make the reader want to continue
  • Keep it to 2-3 sentences

2. Context (The Problem)

  • Explain why this topic matters
  • Describe the problem or opportunity
  • Connect to the reader's experience

3. Main Content (The Solution)

  • Break into 3-5 main sections with H2 headers
  • Each section covers one key point
  • Include code examples, diagrams, or screenshots where helpful
  • Use bullet points for lists

4. Practical Application

  • Show how to apply the concepts
  • Include step-by-step instructions if applicable
  • Provide code snippets or templates

5. Conclusion & CTA

  • Summarize key takeaways (3 bullets max)
  • End with a clear call-to-action
  • Link to related resources

Cover Image Generation

After writing the post, generate a cover image using the generate_cover tool:

generate_cover(prompt="A detailed description of the image...", slug="your-blog-slug")

The tool saves the image to blogs/<slug>/hero.png.

Writing Effective Image Prompts

Structure your prompt with these elements:

  1. Subject: What is the main focus? Be specific and concrete.
  2. Style: Art direction (minimalist, isometric, flat design, 3D render, watercolor, etc.)
  3. Composition: How elements are arranged (centered, rule of thirds, symmetrical)
  4. Color palette: Specific colors or mood (warm earth tones, cool blues and purples, high contrast)
  5. Lighting/Atmosphere: Soft diffused light, dramatic shadows, golden hour, neon glow
  6. Technical details: Aspect ratio considerations, negative space for text overlay

Example Prompts

For a technical blog post:

Isometric 3D illustration of interconnected glowing cubes representing AI agents, each cube has subtle circuit patterns. Cubes connected by luminous data streams. Deep navy background (#0a192f) with electric blue (#64ffda) and soft purple (#c792ea) accents. Clean minimal style, lots of negative space at top for title. Professional tech aesthetic.

For a tutorial/how-to:

Clean flat illustration of hands typing on a keyboard with abstract code symbols floating upward, transforming into lightbulbs and gears. Warm gradient background from soft coral to light peach. Friendly, approachable style. Centered composition with space for text overlay.

For thought leadership:

Abstract visualization of a human silhouette profile merging with geometric neural network patterns. Split composition - organic watercolor texture on left transitioning to clean vector lines on right. Muted sage green and warm terracotta color scheme. Contemplative, forward-thinking mood.

SEO Considerations

  • Include the main keyword in the title and first paragraph
  • Use the keyword naturally 3-5 times throughout
  • Keep the title under 60 characters
  • Write a meta description (150-160 characters)

Quality Checklist

Before finishing:

  • Post saved to blogs/<slug>/post.md
  • Hero image generated at blogs/<slug>/hero.png
  • Hook grabs attention in first 2 sentences
  • Each section has a clear purpose
  • Conclusion summarizes key points
  • CTA tells reader what to do next
how to use blog-post

How to use blog-post on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add blog-post
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/langchain-ai/deepagents --skill blog-post

The skills CLI fetches blog-post from GitHub repository langchain-ai/deepagents and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/blog-post

Reload or restart Cursor to activate blog-post. Access the skill through slash commands (e.g., /blog-post) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.656 reviews
  • Arya Gonzalez· Dec 24, 2024

    Keeps context tight: blog-post is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Layla Farah· Dec 24, 2024

    Solid pick for teams standardizing on skills: blog-post is focused, and the summary matches what you get after install.

  • Pratham Ware· Dec 20, 2024

    blog-post has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Hiroshi Srinivasan· Dec 20, 2024

    blog-post reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Layla Sanchez· Dec 16, 2024

    I recommend blog-post for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Mei Mehta· Nov 19, 2024

    blog-post is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Amina Dixit· Nov 15, 2024

    We added blog-post from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Mateo Shah· Nov 15, 2024

    blog-post has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Yash Thakker· Nov 11, 2024

    Solid pick for teams standardizing on skills: blog-post is focused, and the summary matches what you get after install.

  • Diego Zhang· Nov 11, 2024

    Registry listing for blog-post matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 56

1 / 6