Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

pages-blog页面博客

Agent Skill

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

总安装

222

周安装

9

GitHub Stars

409

下载量

70
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:pages-blog(页面博客)
来源仓库:https://github.com/kostja94/marketing-skills
仓库路径:skills/pages-blog
安装命令:
npx skills add https://github.com/kostja94/marketing-skills --skill pages-blog
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/kostja94/marketing-skills --skill pages-blog

简介

pages-blog 用于查找、检索和筛选相关信息,支持博客页面相关内容。

  • 适用于在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。
  • 可结合关键词、任务场景或来源线索进行信息筛选。
  • 建议通过原始 README 和仓库文档核验具体用法。
  • 安装前需确认权限范围,避免触发不必要的联网或命令执行。

SKILL.md

Pages: Blog

Guides blog page structure, SEO, and content marketing best practices.

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.

Initial Assessment

Check for product marketing context first: If .claude/product-marketing-context.md or .cursor/product-marketing-context.md exists, read it for topics, audience, and keywords.

Identify:

  1. Blog purpose: SEO traffic, thought leadership, product education
  2. Content mix: Pillar pages, cluster content, news
  3. Audience: Buyers, existing customers, developers

Best Practices

Blog Placement: Subdomain vs Subdirectory

OptionExampleSEO / Use
Subdirectoryexample.com/blogSEO weight flows to main domain; recommended for product blogs
Subdomainblog.example.comTreated as separate entity; consider for distinct brands or technical isolation

Choose based on SEO weight distribution, brand consistency, and technical architecture. See Alignify subdomain vs subdirectory guide for details.

Blog Index Page Structure

SectionPurpose
Featured/RecentHighlight newest or most important posts
Categories/TopicsHelp users find by theme
Editor's PicksCurate best content
Related postsPer-article recommendations
SearchHelp users find specific topics

Content Strategy

  • Topical authority: Topic clusters -> pillar page per core topic + 6-12 cluster articles
  • Intent mapping: Transactional, problem-aware, informational
  • EEAT signals: Author bios, Organization schema, citations, changelog
  • Refresh > new: For established sites, updating existing content often outperforms publishing new posts; avoid changing only the date without substantive edits
  • Quality > quantity: Fewer high-quality posts beat many mediocre ones; consider deleting, merging, or refreshing underperformers
  • Topic focus: Avoid blindly expanding topics; dilution can hurt authority on core topics
  • Conversion as north star: SEO KPIs should tie to leads, signups, or sales -> not just traffic

SEO

  • Title: 55 chars, power words, primary keyword
  • Meta: Clear CTA in description
  • Headers: H1-H3 hierarchy, table of contents
  • Content depth: 2,500+ words for pillars; Grade 8 readability
  • URL: Use components-url-slug -> clean slugs, 3-5 words, under 60 chars
  • Schema: Article, BlogPosting, FAQPage where relevant

Technical

  • Core Web Vitals: LCP < 1.0s on mobile
  • Images: WebP, compressed
  • IndexNow: For fast indexing of new posts

Design

  • Scannable: Preview copy, thumbnails, hero images
  • Social sharing: Share buttons on article pages -> see components-social-share
  • Quick answers: Definition boxes, mini-FAQs for AEO
  • TOC: Table of contents for Featured Snippets; jump links in long articles
  • CTA placement: Sidebar CTA or in-paragraph CTA at key conversion points
  • Related/Recent posts: Manual curation or plugin; same topic cluster

Output Format

  • Structure for blog index and post template
  • Content strategy (pillar + clusters)
  • SEO metadata and schema
  • Internal linking approach

Related Skills

  • pages-article: Single article/post page structure, SEO, schema -> use for individual post templates
  • components-url-slug: URL slug for blog posts; 3-5 words, primary keyword
  • seo-content-content-strategy: Content clusters, editorial calendar
  • seo-content-keyword-research: Keywords for blog topics
  • seo-on-page-title, seo-on-page-description, seo-on-page-metadata, seo-on-page-open-graph, seo-on-page-twitter-cards: Blog metadata and social previews
  • seo-on-page-schema: Article schema
  • pages-resources: Blog may be part of resources hub

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

33.79%
按下载量换算24

Claude

30.17%
按下载量换算21

Cursor

18.79%
按下载量换算13

Gemini CLI

10.62%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

来源信息

继续浏览同类 Skills