AI Agent Hub
Back to skills
AIM SEO Blog Generator icon

AIM SEO Blog Generator

Content Creation Updated 2026.08.29

Paste the following prompt into your AI chat to install this skill:

Please install @user_34d5ae4c/aim-blog-write by following the guide at https://skillhub.cn/install/skillhub.md.

About this skill

Problem

SEO blog generation often stalls across field confirmation, streaming response assembly, image download, and Word layout. aim-blog-write consolidates these steps into one fixed entrypoint: users provide theme, industry, and target language, while the skill assembles structured output and turns Markdown content, keywords, and images into a deliverable document.

How It Works

  • Required inputs: theme, industry, and language. If any field is missing, ask the user first instead of guessing defaults.
  • Generation flow: seo_agent.sh calls AEP /seo_agent, parses the SSE stream by code, and assembles {blog_content, keywords, images}.
  • Document rendering: blog_to_word.py downloads images[].image_url into a local images/ folder, renders blog_content into a .docx, and embeds rephraser_result as image captions.
  • Key check: env_guard.sh --check-config verifies aim-secret-key in the skill root .env before running generation.

Boundaries

  • It depends on the AEP gateway and aim-secret-key, without touching internal storage.
  • Images may come from intranet FFS links; the script uses --noproxy '*' for direct access, so do not add extra proxies.
  • A single image failure does not block the whole generation; missing images are logged to stderr, while the run still outputs .docx and raw.json.
  • For structured JSON only, use seo_agent.sh; the default entrypoint remains blog_to_word.py.

Use Cases

  • Write an English e-commerce promotion blog, generate theme, keywords, and images, then export an editable Word draft.
  • Draft a Chinese technical post with an industry tag, keep raw JSON for keyword review.
  • Produce cross-border content in English with captions and downloaded images in a local folder.
  • Call the AEP endpoint in a no-proxy environment, fetch FFS images, and output .docx with raw.json.

Best For

  • Content operations who need English SEO blogs for a chosen industry and a Word export.
  • Editors who need to package Markdown, keywords, and captions into a deliverable draft.
  • Technical operators who need AEP /seo_agent output plus raw JSON for review.
  • Localization leads who need no-proxy FFS image access and .docx generation.