web-content by alinaqi/claude-bootstrap
npx skills add https://github.com/alinaqi/claude-bootstrap --skill web-content加载方式:base.md + ui-web.md
用于创建同时针对传统 SEO 和 AI 发现(ChatGPT、Perplexity、Claude、Gemini)优化的网页内容。
来源: GEO 完整指南 | AI 搜索 SEO | LLM 优化 | 生成引擎优化
SEO 获取点击。GEO 获取引用。
传统 SEO 针对 Google 排名进行优化。生成引擎优化(GEO)则针对被 AI 助手引用进行优化。现代内容需要两者兼顾:
在 2024 年 7 月至 2025 年 2 月期间,AI 流量增长了 1200%。Google 的搜索份额十年来首次跌破 90%。请同时为两者进行优化。
为人而写,为机器而结构。
AI 系统偏好:
## 主页结构
### 首屏区域
- **标题**:清晰的价值主张(你做什么 + 为谁服务)
- **副标题**:你如何交付该价值
- **主要行动号召**:一个明确的行动
- **信任信号**:徽标、推荐语、统计数据
### 内容区块
1. **问题陈述**:你解决的痛点
2. **解决方案概述**:你如何解决它(3-4 个关键特性)
3. **社会证明**:推荐语、案例研究、徽标
4. **工作原理**:3 步流程(简单)
5. **价格预览**:或链接到定价页面
6. **常见问题解答区块**:5-7 个常见问题(GEO 黄金区)
7. **最终行动号召**:重复主要行动
### 必需的结构化数据
- 组织架构数据(名称、徽标、成立日期、社交媒体链接)
- 带有 SearchAction 的网站架构数据
- 问题区块的 FAQ 架构数据
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
## 产品页面结构
### 顶部横幅区
- **产品名称**:清晰、描述性强
- **一句话描述**:用 10 个或更少的词说明它做什么
- **关键优势**:主要价值主张
- **行动号召**:购买/试用/演示
### 内容区块
1. **TL;DR 摘要框**:3-5 个要点总结(可供 AI 引用)
2. **问题 → 解决方案**:什么问题,如何解决
3. **功能网格**:4-6 个带图标的功能
4. **对比表格**:与替代方案的对比(GEO 偏爱此类)
5. **使用场景**:谁使用它以及如何使用
6. **推荐语**:真实姓名、照片、公司
7. **定价**:清晰的层级(如适用)
8. **常见问题解答**:产品特定问题
### 必需的结构化数据
- 产品架构数据(名称、描述、价格、可用性)
- 评价架构数据(综合评分)
- FAQ 架构数据
- 面包屑导航列表架构数据
## 博客文章结构
### 开头(前 100 词)
- **TL;DR**:对标题问题的直接回答
- **你将学到什么**:要点列表
- 此部分应可作为独立引用
### 正文结构
- **H2 章节**:主要主题(每篇文章 5-7 个)
- **H3 子章节**:支持性论点
- **项目符号列表**:便于浏览
- **数据框**:突出关键数字
- **对比表格**:比较选项时使用
### 内容元素
- 定义框("什么是 X?")
- 分步说明
- 代码示例(如果是技术性的)
- 原始统计数据/研究
- 带有署名的专家引述
### 结尾
- **总结**:关键要点(项目符号)
- **后续步骤**:读者应该做什么
- **相关内容**:内部链接
### 必需的元数据
- 作者姓名 + 简介 + 照片
- 发布日期
- 最后更新日期(可见!)
- 阅读时间
- 带有作者信息的文章架构数据
## 常见问题解答页面结构
### 组织方式
- 按类别分组问题
- 最常见的问题放在前面
- 直接、简洁的答案
- 链接到详细页面获取更多信息
### 问题格式
问:[用户提出的确切问题]
答:[第一句直接回答,然后详细说明]
### 必需的结构化数据
- FAQPage 架构数据(对 AI 发现至关重要)
- 每个问答都作为 Question/Answer 架构数据
## 着陆页结构
### 单一焦点
- 一个产品/服务
- 一个受众群体
- 一个行动号召(重复)
### 区块
1. **标题**:以利益为中心,具体明确
2. **问题激发**:痛点
3. **解决方案**:你的产品/服务
4. **证明**:推荐语、统计数据、徽标
5. **功能**:3-5 个关键优势
6. **异议处理**:常见问题解答或保证
7. **行动号召**:清晰、紧迫
### 无导航
- 移除顶部导航(减少跳出)
- 单一路径:阅读 → 转化
<div class="tldr-box">
<h3>TL;DR</h3>
<ul>
<li>关键点 1 附带具体细节</li>
<li>关键点 2 附带数字/统计</li>
<li>关键点 3 附带可操作的见解</li>
</ul>
</div>
放置在文章顶部。AI 系统提取这些内容用于摘要。
## 什么是 [术语]?
[术语] 是 [一句话的简洁定义]。它通过 [工作原理] 来 [实现什么功能]。
**关键特征:**
- 特征 1
- 特征 2
- 特征 3
以 "什么是 X?" 开头 - AI 系统会寻找这种模式。
| 功能 | 产品 A | 产品 B | 我们的产品 |
|---------|-----------|-----------|-------------|
| 价格 | $99/月 | $149/月 | $79/月 |
| 功能 1 | ✓ | ✗ | ✓ |
| 功能 2 | ✗ | ✓ | ✓ |
| 最适合 | 企业 | 初创公司 | 中小企业 |
AI 偏爱结构化对比。在产品页面和评测页面中包含。
<div class="stat-box">
<span class="stat-number">73%</span>
<span class="stat-label">的用户在复杂查询时偏好使用 AI 搜索</span>
<span class="stat-source">来源:Adobe Analytics,2024</span>
</div>
带有来源的原始统计数据会被 AI 引用。
## 如何 [做某事]
### 步骤 1:[动作动词] [对象]
[解释要做什么]
**示例:**
[具体示例]
### 步骤 2:[动作动词] [对象]
[解释]
### 步骤 3:[动作动词] [对象]
[解释]
**结果:** [用户实现的目标]
对这些内容使用 HowTo 结构化数据标记。
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "你的公司",
"url": "https://yoursite.com",
"logo": "https://yoursite.com/logo.png",
"foundingDate": "2020",
"description": "一句话描述",
"sameAs": [
"https://twitter.com/yourcompany",
"https://linkedin.com/company/yourcompany",
"https://github.com/yourcompany"
],
"contactPoint": {
"@type": "ContactPoint",
"email": "hello@yoursite.com",
"contactType": "customer service"
}
}
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "文章标题",
"description": "元描述",
"image": "https://yoursite.com/article-image.jpg",
"author": {
"@type": "Person",
"name": "作者姓名",
"url": "https://yoursite.com/team/author-name",
"jobTitle": "在公司中的角色",
"sameAs": [
"https://linkedin.com/in/author",
"https://twitter.com/author"
]
},
"publisher": {
"@type": "Organization",
"name": "你的公司",
"logo": {
"@type": "ImageObject",
"url": "https://yoursite.com/logo.png"
}
},
"datePublished": "2025-01-15",
"dateModified": "2025-01-20"
}
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "你的产品是什么?",
"acceptedAnswer": {
"@type": "Answer",
"text": "直接回答放在这里。保持简洁但完整。"
}
},
{
"@type": "Question",
"name": "它要多少钱?",
"acceptedAnswer": {
"@type": "Answer",
"text": "基础计划起价为每月 $X..."
}
}
]
}
{
"@context": "https://schema.org",
"@type": "Product",
"name": "产品名称",
"description": "产品描述",
"image": "https://yoursite.com/product.jpg",
"brand": {
"@type": "Brand",
"name": "你的公司"
},
"offers": {
"@type": "Offer",
"price": "29.99",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.8",
"reviewCount": "127"
}
}
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "如何设置你的账户",
"description": "入门分步指南",
"step": [
{
"@type": "HowToStep",
"name": "创建账户",
"text": "前往注册页面并输入你的邮箱"
},
{
"@type": "HowToStep",
"name": "验证邮箱",
"text": "点击验证邮件中的链接"
}
]
}
✅ 要做:
- 文章顶部的 TL;DR 区块
- 一致的格式(标题、项目符号)
- 带有资质的具名作者
- 原创研究和统计数据
- 多意图内容(涵盖相关问题)
❌ 避免:
- 没有实质内容的单薄内容
- 缺少作者署名
- 过时信息(没有日期)
✅ 要做:
- 带有来源的原始统计数据
- 对比表格和结构化数据
- 干净的 URL 别名(/主题名称 而非 /p=123)
- 简短、陈述性的语句
- 图片、图表、示意图
- YouTube 视频(Perplexity 会显示这些)
❌ 避免:
- 没有独特见解的通用内容
- 缺少引用/来源
- 糟糕的 URL 结构
✅ 要做:
- 结构良好、逻辑清晰的内容
- 清晰的定义和解释
- 技术准确性
- 平衡的观点
- 恰当的引用
❌ 避免:
- 误导性或耸人听闻的内容
- 缺少上下文
- 过时的技术信息
✅ 要做:
- 丰富的结构化数据标记
- 详细的图片替代文本
- YouTube 内容(Google 旗下)
- 多媒体(视频、带转录的音频)
❌ 避免:
- 缺少结构化数据
- 没有替代文本的图片
- 纯文本内容
<article>
<header>
<h1>文章标题</h1>
<div class="meta">
<span class="author">作者:John Smith</span>
<span class="published">发布日期:2025年1月15日</span>
<span class="updated">最后更新:2025年1月20日</span>
</div>
</header>
</article>
AI 系统偏好近期内容。显著显示日期。
| 内容类型 | 更新频率 |
|---|---|
| 产品页面 | 功能变更时 |
| 定价 | 变更时立即更新 |
| 博客文章 | 季度审查 |
| 统计数据 | 新数据可用时 |
| 指南 | 每半年一次 |
.*chatgpt\.com.*|.*perplexity\.ai.*|.*gemini\.google\.com.*|.*copilot\.microsoft\.com.*|.*openai\.com.*|.*claude\.ai.*|.*poe\.com.*|.*you\.com.*|.*phind\.com.*
// 检查是否为 AI 引荐来源
const aiReferrers = [
'chatgpt.com',
'chat.openai.com',
'perplexity.ai',
'claude.ai',
'gemini.google.com',
'copilot.microsoft.com',
'poe.com',
'you.com',
'phind.com'
];
const referrer = document.referrer;
const isAIReferral = aiReferrers.some(ai => referrer.includes(ai));
if (isAIReferral) {
analytics.track('ai_referral', {
source: referrer,
page: window.location.pathname
});
}
添加到表单中:
你是如何知道我们的?
- [ ] Google 搜索
- [ ] ChatGPT
- [ ] Perplexity
- [ ] Claude
- [ ] 社交媒体
- [ ] 推荐
- [ ] 其他
## SEO 检查清单
- [ ] 标题标签(50-60 字符)包含主要关键词
- [ ] 元描述(150-160 字符)包含行动号召
- [ ] URL 别名干净且具有描述性
- [ ] H1 与标题意图匹配
- [ ] H2/H3 层级结构逻辑清晰
- [ ] 图片具有描述性替代文本
- [ ] 内部链接到相关内容
- [ ] 外部链接到权威来源
## GEO 检查清单
- [ ] 顶部的 TL;DR 或摘要
- [ ] 第一段对主要问题的直接回答
- [ ] 带有来源的数据框
- [ ] 对比表格(如适用)
- [ ] 带有结构化数据的常见问题解答区块
- [ ] 作者姓名、简介和资质
- [ ] 发布日期和最后更新日期可见
- [ ] 结构化数据标记已验证
- [ ] 内容可以独立引用
- [ ] 包含原创见解或数据
# 验证结构化数据标记
# 使用:https://validator.schema.org/
# 或:https://search.google.com/test/rich-results
project/
├── content/
│ ├── pages/
│ │ ├── home.md
│ │ ├── about.md
│ │ ├── pricing.md
│ │ └── contact.md
│ ├── blog/
│ │ ├── post-1.md
│ │ └── post-2.md
│ └── legal/
│ ├── privacy.md
│ └── terms.md
├── components/
│ ├── SchemaMarkup.tsx
│ ├── TLDRBox.tsx
│ ├── StatBox.tsx
│ ├── FAQSection.tsx
│ └── AuthorBio.tsx
└── lib/
└── schema.ts # 结构化数据生成器
| 页面类型 | 结构化数据 |
|---|---|
| 主页 | Organization, WebSite |
| 博客文章 | Article, Author, FAQ |
| 产品 | Product, Review, FAQ |
| 常见问题解答 | FAQPage |
| 操作指南 | HowTo |
| 关于 | Organization, Person |
每周安装量
87
代码仓库
GitHub 星标数
529
首次出现
2026年1月20日
安全审计
安装于
opencode71
gemini-cli67
codex63
cursor62
claude-code61
github-copilot55
Load with: base.md + ui-web.md
For creating web content optimized for both traditional SEO and AI discovery (ChatGPT, Perplexity, Claude, Gemini).
Sources: GEO Complete Guide | AI Search SEO | LLM Optimization | Generative Engine Optimization
SEO gets clicks. GEO gets citations.
Traditional SEO optimizes for Google rankings. Generative Engine Optimization (GEO) optimizes for being cited by AI assistants. Modern content needs both:
AI traffic grew 1,200% between July 2024 and February 2025. Google's search share dropped below 90% for the first time in a decade. Optimize for both.
Write for humans, structure for machines.
AI systems prefer:
## Homepage Structure
### Above the Fold
- **Headline**: Clear value proposition (what you do + for whom)
- **Subheadline**: How you deliver that value
- **Primary CTA**: One clear action
- **Trust signals**: Logos, testimonials, stats
### Content Sections
1. **Problem Statement**: Pain point you solve
2. **Solution Overview**: How you solve it (3-4 key features)
3. **Social Proof**: Testimonials, case studies, logos
4. **How It Works**: 3-step process (simple)
5. **Pricing Preview**: Or link to pricing page
6. **FAQ Section**: 5-7 common questions (GEO gold)
7. **Final CTA**: Repeat primary action
### Schema Required
- Organization schema (name, logo, founding date, social links)
- WebSite schema with SearchAction
- FAQ schema for questions section
## Product Page Structure
### Hero Section
- **Product Name**: Clear, descriptive
- **One-line Description**: What it does in 10 words or less
- **Key Benefit**: Primary value proposition
- **CTA**: Buy/Try/Demo
### Content Sections
1. **TL;DR Box**: 3-5 bullet summary (AI-quotable)
2. **Problem → Solution**: What problem, how solved
3. **Features Grid**: 4-6 features with icons
4. **Comparison Table**: vs. alternatives (GEO loves these)
5. **Use Cases**: Who uses it and how
6. **Testimonials**: Real names, photos, companies
7. **Pricing**: Clear tiers if applicable
8. **FAQ**: Product-specific questions
### Schema Required
- Product schema (name, description, price, availability)
- Review schema (aggregate rating)
- FAQ schema
- BreadcrumbList schema
## Blog Post Structure
### Opening (First 100 words)
- **TL;DR**: Direct answer to the title's question
- **What you'll learn**: Bullet list of takeaways
- This section should be quotable standalone
### Body Structure
- **H2 sections**: Main topics (5-7 per article)
- **H3 subsections**: Supporting points
- **Bullet lists**: For scanability
- **Stat boxes**: Highlight key numbers
- **Comparison tables**: When comparing options
### Content Elements
- Definition boxes ("What is X?")
- Step-by-step instructions
- Code examples (if technical)
- Original statistics/research
- Expert quotes with attribution
### Closing
- **Summary**: Key takeaways (bulleted)
- **Next steps**: What reader should do
- **Related content**: Internal links
### Metadata Required
- Author name + bio + photo
- Publication date
- Last updated date (visible!)
- Reading time
- Article schema with author
## FAQ Page Structure
### Organization
- Group questions by category
- Most common questions first
- Direct, concise answers
- Link to detailed pages for more info
### Question Format
Q: [Exact question users ask]
A: [Direct answer in first sentence, then elaboration]
### Schema Required
- FAQPage schema (critical for AI discovery)
- Each Q&A as Question/Answer schema
## Landing Page Structure
### Single Focus
- One offer
- One audience
- One CTA (repeated)
### Sections
1. **Headline**: Benefit-focused, specific
2. **Problem Agitation**: Pain points
3. **Solution**: Your offer
4. **Proof**: Testimonials, stats, logos
5. **Features**: 3-5 key benefits
6. **Objection Handling**: FAQ or guarantee
7. **CTA**: Clear, urgent
### No Navigation
- Remove header nav (reduce exits)
- Single path: read → convert
<div class="tldr-box">
<h3>TL;DR</h3>
<ul>
<li>Key point 1 with specific detail</li>
<li>Key point 2 with number/stat</li>
<li>Key point 3 with actionable insight</li>
</ul>
</div>
Place at top of articles. AI systems extract these for summaries.
## What is [Term]?
[Term] is [concise definition in one sentence]. It [what it does] by [how it works].
**Key characteristics:**
- Characteristic 1
- Characteristic 2
- Characteristic 3
Start with "What is X?" - AI systems look for this pattern.
| Feature | Product A | Product B | Our Product |
|---------|-----------|-----------|-------------|
| Price | $99/mo | $149/mo | $79/mo |
| Feature 1 | ✓ | ✗ | ✓ |
| Feature 2 | ✗ | ✓ | ✓ |
| Best For | Enterprise | Startups | SMBs |
AI loves structured comparisons. Include in product and review pages.
<div class="stat-box">
<span class="stat-number">73%</span>
<span class="stat-label">of users prefer AI search for complex queries</span>
<span class="stat-source">Source: Adobe Analytics, 2024</span>
</div>
Original statistics with sources get cited by AI.
## How to [Do Thing]
### Step 1: [Action Verb] [Object]
[Explanation of what to do]
**Example:**
[Concrete example]
### Step 2: [Action Verb] [Object]
[Explanation]
### Step 3: [Action Verb] [Object]
[Explanation]
**Result:** [What user achieves]
Use HowTo schema markup for these.
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Company",
"url": "https://yoursite.com",
"logo": "https://yoursite.com/logo.png",
"foundingDate": "2020",
"description": "One sentence description",
"sameAs": [
"https://twitter.com/yourcompany",
"https://linkedin.com/company/yourcompany",
"https://github.com/yourcompany"
],
"contactPoint": {
"@type": "ContactPoint",
"email": "hello@yoursite.com",
"contactType": "customer service"
}
}
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Article Title",
"description": "Meta description",
"image": "https://yoursite.com/article-image.jpg",
"author": {
"@type": "Person",
"name": "Author Name",
"url": "https://yoursite.com/team/author-name",
"jobTitle": "Role at Company",
"sameAs": [
"https://linkedin.com/in/author",
"https://twitter.com/author"
]
},
"publisher": {
"@type": "Organization",
"name": "Your Company",
"logo": {
"@type": "ImageObject",
"url": "https://yoursite.com/logo.png"
}
},
"datePublished": "2025-01-15",
"dateModified": "2025-01-20"
}
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is your product?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Direct answer here. Keep concise but complete."
}
},
{
"@type": "Question",
"name": "How much does it cost?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Pricing starts at $X/month for basic plan..."
}
}
]
}
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Product Name",
"description": "Product description",
"image": "https://yoursite.com/product.jpg",
"brand": {
"@type": "Brand",
"name": "Your Company"
},
"offers": {
"@type": "Offer",
"price": "29.99",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.8",
"reviewCount": "127"
}
}
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to Set Up Your Account",
"description": "Step-by-step guide to getting started",
"step": [
{
"@type": "HowToStep",
"name": "Create account",
"text": "Go to signup page and enter your email"
},
{
"@type": "HowToStep",
"name": "Verify email",
"text": "Click the link in the verification email"
}
]
}
✅ DO:
- TL;DR sections at top of articles
- Consistent formatting (headers, bullets)
- Named authors with credentials
- Original research and statistics
- Multi-intent content (covers related questions)
❌ AVOID:
- Thin content without substance
- Missing author attribution
- Outdated information (no dates)
✅ DO:
- Original statistics with sources
- Comparison tables and structured data
- Clean URL slugs (/topic-name not /p=123)
- Short, declarative statements
- Images, charts, diagrams
- YouTube videos (Perplexity shows these)
❌ AVOID:
- Generic content without unique insights
- Missing citations/sources
- Poor URL structure
✅ DO:
- Well-structured, logical content
- Clear definitions and explanations
- Technical accuracy
- Balanced perspectives
- Proper citations
❌ AVOID:
- Misleading or sensational content
- Missing context
- Outdated technical information
✅ DO:
- Rich schema markup
- Detailed image alt-text
- YouTube content (Google-owned)
- Multimedia (video, audio with transcripts)
❌ AVOID:
- Missing structured data
- Images without alt-text
- Text-only content
<article>
<header>
<h1>Article Title</h1>
<div class="meta">
<span class="author">By John Smith</span>
<span class="published">Published: January 15, 2025</span>
<span class="updated">Last updated: January 20, 2025</span>
</div>
</header>
</article>
AI systems prefer recent content. Show dates prominently.
| Content Type | Update Frequency |
|---|---|
| Product pages | On feature changes |
| Pricing | Immediately on change |
| Blog posts | Quarterly review |
| Statistics | When new data available |
| Guides | Semi-annually |
.*chatgpt\.com.*|.*perplexity\.ai.*|.*gemini\.google\.com.*|.*copilot\.microsoft\.com.*|.*openai\.com.*|.*claude\.ai.*|.*poe\.com.*|.*you\.com.*|.*phind\.com.*
// Check for AI referrer
const aiReferrers = [
'chatgpt.com',
'chat.openai.com',
'perplexity.ai',
'claude.ai',
'gemini.google.com',
'copilot.microsoft.com',
'poe.com',
'you.com',
'phind.com'
];
const referrer = document.referrer;
const isAIReferral = aiReferrers.some(ai => referrer.includes(ai));
if (isAIReferral) {
analytics.track('ai_referral', {
source: referrer,
page: window.location.pathname
});
}
Add to forms:
How did you hear about us?
- [ ] Google Search
- [ ] ChatGPT
- [ ] Perplexity
- [ ] Claude
- [ ] Social Media
- [ ] Referral
- [ ] Other
## SEO Checklist
- [ ] Title tag (50-60 chars) with primary keyword
- [ ] Meta description (150-160 chars) with CTA
- [ ] URL slug is clean and descriptive
- [ ] H1 matches title intent
- [ ] H2/H3 hierarchy is logical
- [ ] Images have descriptive alt-text
- [ ] Internal links to related content
- [ ] External links to authoritative sources
## GEO Checklist
- [ ] TL;DR or summary at top
- [ ] Direct answer to main question in first paragraph
- [ ] Stat boxes with sources
- [ ] Comparison tables where applicable
- [ ] FAQ section with schema
- [ ] Author name, bio, and credentials
- [ ] Publication and last-updated dates visible
- [ ] Schema markup validated
- [ ] Content can be quoted standalone
- [ ] Original insights or data included
# Validate schema markup
# Use: https://validator.schema.org/
# Or: https://search.google.com/test/rich-results
project/
├── content/
│ ├── pages/
│ │ ├── home.md
│ │ ├── about.md
│ │ ├── pricing.md
│ │ └── contact.md
│ ├── blog/
│ │ ├── post-1.md
│ │ └── post-2.md
│ └── legal/
│ ├── privacy.md
│ └── terms.md
├── components/
│ ├── SchemaMarkup.tsx
│ ├── TLDRBox.tsx
│ ├── StatBox.tsx
│ ├── FAQSection.tsx
│ └── AuthorBio.tsx
└── lib/
└── schema.ts # Schema generators
| Page Type | Schema |
|---|---|
| Homepage | Organization, WebSite |
| Blog Post | Article, Author, FAQ |
| Product | Product, Review, FAQ |
| FAQ | FAQPage |
| How-to | HowTo |
| About | Organization, Person |
Weekly Installs
87
Repository
GitHub Stars
529
First Seen
Jan 20, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode71
gemini-cli67
codex63
cursor62
claude-code61
github-copilot55
超能力技能使用指南:AI助手技能调用优先级与工作流程详解
52,100 周安装