Article Page Generator
Audit or design a single blog post URL for structure, metadata, schema, and UX—not the blog index and not long-form body drafting.
Overview
article-page-generator is an agent skill most often used in Launch (also Grow content, Build docs) that structures and optimizes single article pages for SEO, schema, and UX via a fixed research-to-recommendations workfl
Install
npx skills add https://github.com/kostja94/marketing-skills --skill article-page-generatorWhat is this skill?
- 4-step output workflow: 0 Research → 1 Intent → 2 Content Analysis → 3 Recommendations (do not skip)
- Four optimization inputs frame every article analysis and creation pass
- Covers layout, metadata, schema, and technical article-page concerns—not body prose
- Research phase includes keywords, search intent, and competitor review with shown web findings
- Explicit handoff: article-content for body copy; blog-page-generator for index/listing pages
- 4-step output workflow numbered 0–3 (Research → Intent → Content → Recommendations)
- 4 optimization foundation inputs for article analysis
Adoption & trust: 773 installs on skills.sh; 586 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a blog post URL live or planned but no ordered SEO and template checklist grounded in intent, competitors, and page-level technical requirements.
Who is it for?
Solo builders optimizing or launching individual posts who already separate page SEO from writing the article body.
Skip if: Teams that only need blog index pagination, category templates, or full article drafts without page-level SEO structure.
When should I use this skill?
User mentions article page, blog post page, single post, post template, article schema, competitor article analysis, or optimize article for SEO (not blog index).
What do I get? / Deliverables
You receive research-backed intent and content analysis plus actionable recommendations for one article page—then invoke article-content for body copy or blog-page-generator for the listing page.
- Research phase findings (keywords, intent, competitors)
- Intent and content analysis plus prioritized page-level recommendations
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Article URL templates and on-page SEO are canonical Launch SEO work before and right after you publish posts. The skill targets one article/post page shell and technical SEO, distinct from blog listing pages or body copy generation.
Where it fits
Before publishing a launch post, run the 0–3 workflow to lock title patterns, schema, and internal links for the post template.
Refresh a high-traffic article’s metadata and structure after competitor SERP shifts without rewriting the full body in one pass.
Apply the same single-page analysis to a long help doc URL that should rank like an article.
How it compares
Single-post SEO and template workflow, not the blog index generator or the article body writing skill.
Common Questions / FAQ
Who is article-page-generator for?
Indie founders and content-led SaaS builders who publish articles and want agent-guided structure, metadata, and schema for one post URL.
When should I use article-page-generator?
At Launch SEO when tuning post templates; in Grow when refreshing top posts; in Build docs when a help article needs the same single-page SEO treatment.
Is article-page-generator safe to install?
Use the Security Audits panel on this Prism page before enabling web research or project file reads in your agent environment.
Workflow Chain
Then invoke: article content, blog page generator
SKILL.md
READMESKILL.md - Article Page Generator
# Pages: Article (Single Post) Guides **structure, SEO, and UX** for individual article pages — layout, metadata, schema, technical. For **article body content** (intro, body, conclusion, writing), see **article-content**. Distinct from **blog-page-generator**, which covers the blog index/listing page. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. **Output workflow**: Always output in order: **0. Research Phase** (keywords, search intent, competitors) → **1. Intent Analysis** → **2. Content Analysis** → **3. Recommendations**. Do not skip steps. When Research Phase was performed via web search, show the search results and findings. ## Optimization Foundation: Four Inputs Article analysis and creation rest on **four inputs**. Gather or infer them before outputting recommendations: | Input | Purpose | Source | |-------|---------|--------| | **Product** | Product connection, features, use cases, CTA placement | project-context (Sections 1–4, 9–11); article content; web search | | **Keywords** | Target keyword, primary/secondary placement | project-context Section 6; keyword-research; article | | **Article intent** | Informational, commercial, transactional, navigational; drives structure, CTA, SEO depth | project-context Section 6 (target intent); article orientation; content type | | **Competitor articles** | Structure to adopt, content gaps, length target, keyword opportunities | User-provided URLs; project-context Section 11; web search | **When any input is missing**: Proactively ask or search. For article analysis: perform **Research Phase** (keyword search, search intent, competitor articles) by default — see Research Phase section. For product/keywords/intent, infer from article or prompt user to add project-context. ## Before Analysis: Gather Context **1. Product / company context** Use available context to give **tailored** analysis: | Source | Use for | |--------|---------| | **project-context.md** | Keywords (Section 6), competitors (Section 7), content strategy (Section 11), product connection | | **Article content** | Extract product name, features, URLs; infer target keyword and audience | | **Web search** | When analyzing a known brand: search for "[product] features", "[product] vs competitors", company positioning — use to validate product connection, suggest missing features/use cases, and improve competitor gap analysis | If no project-context exists, infer from the article and optionally search for company/product info to enrich recommendations. ## Research Phase: Keyword, Search Intent, Competitor (Required for Article Analysis) **Lightweight** research for article analysis. When **analyzing or auditing** an article, perform searches and **output the results** in Section 0. Skip only if user explicitly asks to skip (e.g. "skip search"). - **Keyword**: Extract from article (title, H1, H2s, first 100 words); search for opportunities — see **keyword-research** (extract from article method) - **Search intent**: Informational / Commercial / Transactional / Navigational — see **keyword-research** Search Intent - **Competitor articles**: Fetch 2–3 top-ranking pages; analyze structure, gaps, length target — see **competitor-research** (Competitor Article F