Token导航 LogoToken导航TokenDH.com
研究检索需要联网clawhub未标认证来源可访问clear审计通过

article-page-generator文章页面生成器

Agent Skill

article-page-generator 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

5,352

周安装

223

GitHub Stars

公开资料未说明

下载量

1,784
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:article-page-generator(文章页面生成器)
来源仓库:https://github.com/kostja94/article-page-generator
安装命令:
openclaw skills install article-page-generator
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install article-page-generator

简介

创建单篇文章页面而非索引页的设计方案。

  • 优化标题、摘要与元数据的呈现结构。article-page-generator 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 适用于独立博客文章或产品说明页制作。
  • 安装命令:openclaw skills install article-page-generator。
  • 需明确目标读者群体以调整语言风格与深度。

SKILL.md

name
article-page-generator
description
When the user wants to create, optimize, or audit a single article/post page (not the blog index). Also use when the user mentions "article page," "blog post page," "single post," "post template," "article structure," "post optimization," "competitor article analysis," "optimize based on top-ranking articles," "analyze ranking articles," "optimize article for SEO," or "article schema." For writing article body copy, use article-content. For blog listing/index page, use blog-page-generator.
metadata
version
1.3.0

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 Analysis2. Content Analysis3. 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:

InputPurposeSource
ProductProduct connection, features, use cases, CTA placementproject-context (Sections 1–4, 9–11); article content; web search
KeywordsTarget keyword, primary/secondary placementproject-context Section 6; keyword-research; article
Article intentInformational, commercial, transactional, navigational; drives structure, CTA, SEO depthproject-context Section 6 (target intent); article orientation; content type
Competitor articlesStructure to adopt, content gaps, length target, keyword opportunitiesUser-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:

SourceUse for
project-context.mdKeywords (Section 6), competitors (Section 7), content strategy (Section 11), product connection
Article contentExtract product name, features, URLs; infer target keyword and audience
Web searchWhen 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 Fetch Workflow)

Output format: See Output Format Section 0 below.

Scope

  • Single article page: One post, one URL (e.g. /blog/how-to-optimize-seo)
  • Not the blog index, category pages, or archive pages — see blog-page-generator for those

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for topics, audience, keywords, and Section 11 (Content/Blog/Article Strategy).

Identify:

  1. Product connection: How does this article support the product? (educate on problem, introduce features, nurture leads)
  2. Keyword basis: Target keyword from product context or keyword research — see keyword-research
  3. Content type: Blog post, guide, tutorial, news, evergreen
  4. Length: Short (<1,000 words), medium (1,000–2,500), long (2,500+)
  5. Intent: Informational, commercial, problem-aware

Product-linked content: Articles should tie to the product (problem it solves, features, use cases). Avoid purely generic content with no product relevance. Link to product/feature pages naturally in conclusion or when context fits.

Article Orientations

Choose structure, SEO depth, and schema based on orientation. See content-marketing for full Article Orientations (Funding/PR, Product update, Guide, News, Evergreen), SEO-driven vs non-SEO-driven, Evergreen vs Timely.

Intent Analysis output: Orientation, primary goal, SEO vs non-SEO, Evergreen vs timely — see Output Format Section 1.

Article Page Structure

SectionPurpose
Hero/HeaderTitle (H1), author, single date (see schema-markup Date display for CTR), reading time (word count ÷ 200; round up), featured image, share buttons
TL;DR or Key TakeawaysSee article-content for content; placed after intro; supports GEO/AI citation
IntroductionSee article-content for hook, length, keyword placement
BodySee article-content for QAE, paragraph length, scannability
ConclusionSee article-content for summary, CTA, product connection
Related posts3–6 contextual links; end-of-article recommendations
Author bioE-E-A-T; credentials, photo, link to author page — see eeat-signals

Featured Image

See image-optimization (Article / Blog hero). Same image for Schema, Open Graph, Twitter Cards; min 1200px wide, absolute URL. See open-graph, twitter-cards.

Social Sharing

  • Add share buttons (X, LinkedIn, Facebook, etc.) — see social-share-generator
  • Place after intro and/or end of article; sticky sidebar for long-form
  • Requires Open Graph and Twitter Cards for rich previews when shared

GEO / AI Optimization

See article-content for TL;DR, Key Takeaways, QAE pattern, answer-first; generative-engine-optimization for full GEO strategy.

Long-Form (1,000+ words)

  • Add table of contents (TOC) after intro — see toc-generator
  • Use jump links for major sections
  • Break text with images, lists, definition boxes, mini-FAQs

SEO Best Practices

Title & Meta

ElementGuideline
Title55 chars; primary keyword near start; power words
Meta description150–160 chars; CTA; primary keyword
H1One per page; matches title; primary keyword naturally

Keyword Placement

  • Title: 1× primary keyword
  • First 100 words: 1× primary keyword
  • Body: 2–3× naturally; avoid stuffing
  • At least one H2: Include primary or related keyword

Content Quality

See article-content for readability, depth, originality, word count by type. E-E-A-T: Author bio, citations, changelog, expert quotes — see eeat-signals.

Common Mistakes to Avoid

  • Multiple H1s; skipping heading levels (H2→H4); keyword stuffing in headings
  • Neglecting conclusion or CTA; no internal links to related content
  • Walls of text; generic "click here" anchors

URL

Use url-slug-generator for slug creation. Key rules:

  • Slug: 3–5 words; under 60 chars; primary keyword; lowercase, hyphens
  • Example: /blog/ai-people-search not /blog/ai-search-engine-finding-people-speed-discovery-outreach
  • Avoid: Date in path (/blog/2025/01/15/article-title); copy-pasting full title

Date Display

See schema-markup (Date display for CTR): show only one visible date; prefer dateModified.

Schema & Open Graph

See schema-markup for Article/BlogPosting/NewsArticle type selection, required properties, JSON-LD example, and date display. Validate with Rich Results Test.

Open Graph for Articles

Use og:type: article for article pages (not website):

<meta property="og:type" content="article">
<meta property="og:article:published_time" content="2025-01-15T09:00:00Z">
<meta property="og:article:modified_time" content="2025-02-01T14:30:00Z">
<meta property="og:article:author" content="https://example.com/author/jane">

Internal Linking

ElementGuideline
Volume3–5 contextual links in body + 3–6 in Related posts = 6–11 total per article
First paragraph1 link to pillar or key related content
Body2–4 contextual links; one per major section when relevant
Related posts3–6 end-of-article links; same topic cluster
Anchor textDescriptive (e.g. "SEO checklist for 2025", "how to optimize meta tags"); avoid "click here", "learn more", "read more"
VariationMix exact-match, partial-match, branded anchors; avoid over-optimization
Orphan preventionEvery article has ≥1 internal link from hub/pillar or nav

Outbound Links (External)

ElementGuideline
Volume2–5 external links per article; cite authoritative sources
When to useStatistics, research, definitions, tool comparisons, expert quotes
Anchor textDescriptive (e.g. "Google's Search Quality Guidelines", "SEO study"); link to source
Same URLCounts once per page for link equity; no need to repeat
E-E-A-TExternal links to reputable sources signal trust — see eeat-signals

References / Citations

See article-content for citation format; eeat-signals for E-E-A-T and when to include.

AI-Assisted Content

See article-content for AI-assisted content guidance; eeat-signals for E-E-A-T.

Technical

  • Core Web Vitals: LCP < 1.0s on mobile
  • Images: WebP, compressed; descriptive alt text; keyword in filename when natural
  • IndexNow: For fast indexing of new posts
  • Canonical: Self-referencing canonical on article page

Post-Publication

  • Refresh: Update every 6–12 months; refresh stats, add insights
  • Internal links: Add links from older posts to new articles
  • Monitor: GSC indexing, rankings, Core Web Vitals

Content Analysis

When auditing or optimizing an article, apply the Content Audit Checklist. See article-content for full dimensions.

Output Format

0. Research Phase (output first, when analysis/audit is performed)

When analyzing or auditing an article, output this section before Intent Analysis. Include search sources and findings. If user asked to skip search, note that and infer from article only.

SectionOutput
Keyword SearchPrimary keyword (from article or search), secondary keywords, keyword opportunities (from SERP/competitor analysis). If search was performed: query used, top results observed.
Search IntentIntent for primary keyword (Informational/Commercial/Transactional/Navigational), intent for 2–3 secondary keywords, whether article content matches intent. If search was performed: SERP snippet types observed.
Competitor ArticlesIf searched: 2–3 URLs, brief structure (word count, H2s), content gaps, length target. If user provided URLs: same. See competitor-research for full methodology. If skipped: "Competitor analysis skipped."

1. Intent Analysis (output second)

Before any recommendations, output a brief analysis:

DimensionOutput
OrientationFunding/PR, Product update, Guide, News, Evergreen
Primary goalBrand, PR, education, product adoption, organic traffic, …
SEO vs non-SEOSEO-driven / Non-SEO-driven / Hybrid
Evergreen vs timelyEvergreen / Timely
Implications1–2 sentences: e.g. "Low SEO priority → focus on clarity, shareability" or "SEO-driven → full keyword + GEO optimization"

2. Content Analysis (output third)

Apply the Content Analysis table above. Output a brief assessment per dimension (✅ / ⚠️ / ❌ + one-line note).

3. Recommendations (output fourth, tailored to intent)

Assign priority to each item: P0 (critical), P1 (high), P2 (medium), P3 (nice-to-have). Output as table or list with priority prefix.

PriorityUse when
P0Blocks GEO/SEO; missing core element (TL;DR or Key Takeaways, keyword in first 100 words, schema)
P1Significant impact on traffic, CTR, or conversion (title length, share buttons, CTA)
P2Improves UX or authority (related posts, author bio, internal links)
P3Polish (image optimization, readability tweaks)

Example: [P0] Add TL;DR or Key Takeaways — GEO, AI citation

  • Product connection (how article supports product; where to link) — see article-content
  • Keyword (target from product context or keyword research)
  • Structure for article template (hero, TL;DR or Key Takeaways, intro, body, conclusion, related, author) — content creation: article-content
  • Featured image (dimensions, alt, file size, og:image alignment)
  • GEO elements (TL;DR or Key Takeaways, QAE pattern) — *skip or minimal for non-SEO-driven*
  • SEO checklist (title, meta, H1, keyword placement) — *skip or minimal for non-SEO-driven*
  • Schema type and JSON-LD
  • Internal links (3–5 in body + 3–6 Related; anchor text suggestions; avoid "click here")
  • Outbound links (2–5 external; cite stats, research; anchor text for each)
  • References (inline citations vs Reference section; when to add for E-E-A-T)
  • Competitor analysis (when URLs provided or searched): content gaps vs top rankers, structure to adopt, length target, keyword opportunities — see competitor-research for methodology; Before Analysis to prompt user or search

Related Skills

  • article-content: Article body creation; intro, body, conclusion; writing frameworks; Content Audit Checklist
  • eeat-signals: E-E-A-T; author bio, citations, YMYL
  • competitor-research: Content gaps, structure, length target
  • blog-page-generator: Blog index/listing; article pages live within blog
  • keyword-research: Keyword basis for articles
  • schema-markup: Article/BlogPosting/NewsArticle schema
  • heading-structure: H1–H6 structure for article body
  • content-optimization: H2 keywords, tables, lists, multimedia; word count for articles → article-content
  • image-optimization: Article hero/featured image specs
  • internal-links: Related posts, contextual links
  • open-graph, twitter-cards: Social previews for articles
  • generative-engine-optimization: GEO strategy; AI citation optimization

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

97.14%
按下载量换算1,733

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills