Token导航 LogoToken导航

Agent Skill · 研究检索

pseo-engine(伪引擎)

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

pseo-engine 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 70,834。

总安装 198周安装 8GitHub Stars 公开资料未说明下载 62核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/leoli77521/portfolio-starter-kit --skill pseo-engine

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于信息检索与筛选,支持基于关键词的任务导向搜索。适合在需要快速定位文档、代码或知识片段的场景中使用。通过 GitHub 仓库安装,需关注其是否执行外部命令或访问网络。

安装命令:npx skills add https://github.com/leoli77521/portfolio-starter-kit --skill pseo-engine。建议核实维护状态与 API 调用限制后再投入生产使用。

来源仓库内路径:skills/pseo-engine

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/leoli77521/portfolio-starter-kit --skill pseo-…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

pseo-engine 怎么安装?

在终端执行 npx skills add https://github.com/leoli77521/portfolio-starter-kit --skill pseo-engine。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

pseo-engine 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

pseo-engine 需要什么权限?

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

pseo-engine 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

pseo-engine 用的人多吗?

公开数据是累计安装 198 次,近一周安装 8 次,下载 62 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

pseo-engine 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
pseo-engine

伪引擎 · 本页

198—需要联网未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

pSEO Automation Engine

高度自动化的程序化SEO引擎,具备完整的SEO能力矩阵。

Capabilities Overview

ModuleTrigger CommandsFunction
Keyword Researchkeyword research [topic], 分析关键词 [topic]SERP analysis, long-tail discovery, intent classification
Content Optimizeroptimize content [path], 优化文章 [path]Score content, suggest improvements, auto-fix safe issues
Technical Auditseo audit, SEO诊断Full site technical SEO health check
Competitor Analysisanalyze competitor [url], 分析竞争对手 [url]Gap analysis, content comparison, opportunity identification
pSEO Generatorgenerate pseo, 生成pSEO页面Batch generate programmatic SEO pages
Internal Linkingbuild internal links, 构建内链Build site-wide internal link graph
Full Analysisseo analysis, SEO分析Comprehensive site analysis with prioritized recommendations

Module 1: Keyword Research

Trigger: keyword research [topic] / 分析关键词 [主题]

Workflow

  1. Search SERP Data - Use WebSearch to get real-time results for target keywords
  2. Long-tail Discovery - Generate variations: [topic] + tutorial/guide/for [role]/best practices
  3. Intent Classification - Categorize as Informational/Navigational/Transactional
  4. Competition Analysis - Assess difficulty based on SERP results
  5. PAA Extraction - Identify "People Also Ask" opportunities
  6. Featured Snippet Opportunities - Identify featured snippet potential

Output Format

## Keyword Research Report: [Topic]

### Primary Keywords
| Keyword | Intent | Difficulty | Opportunity Score |
|---------|--------|------------|-------------------|

### Long-tail Variations
- [keyword variation 1]
- [keyword variation 2]

### Content Recommendations
1. [Recommended article topic and angle]
2. [Recommended article topic and angle]

### PAA Questions to Target
- [Question 1]
- [Question 2]

Module 2: Content Optimization

Trigger: optimize content [path] / 优化文章 [路径]

Analysis Criteria

  1. Title Optimization (50-60 chars, includes power words)
  2. Meta Description (150-160 chars, compelling CTA)
  3. Heading Hierarchy (H1 → H2 → H3 logical flow)
  4. Keyword Density (Primary keyword in first paragraph, natural distribution)
  5. Internal Links (2-3 related posts, descriptive anchor text)
  6. Image Optimization (Alt text present, descriptive)
  7. Schema Opportunity (FAQ, HowTo, Article schema)
  8. Content Freshness (Outdated references, version numbers)

Auto-Fix (Safe Modifications)

  • Add missing alt text
  • Adjust meta description length
  • Add missing Schema markup
  • Insert internal links to related content

Manual Review Queue

  • Title changes (require user confirmation)
  • Content restructuring
  • Major rewrite suggestions

Output Format

## Content Optimization Report: [filename]

### SEO Score: [X]/100

### Quick Wins (Auto-fixable)
- [ ] [Issue 1] → [Fix]
- [ ] [Issue 2] → [Fix]

### Manual Review Required
- [ ] [Issue with explanation]

### Internal Link Suggestions
Link from: "[anchor text]" → /blog/[related-post]

Module 3: Technical SEO Audit

Trigger: seo audit / SEO诊断

Checks Performed

  1. Core Checks (via /api/seo-health)

- Sitemap accessibility - Robots.txt configuration - Homepage meta tags - Structured data validation - Page speed basics - Mobile friendliness

  1. Extended Checks

- Schema coverage (BlogPosting/Course/HowTo/FAQ) - Canonical tags consistency - Internal link health - Orphan page detection - Redirect chain analysis - Core Web Vitals indicators

Output Format

## Technical SEO Audit Report

### Overall Score: [X]/100 [Status Badge]

### Critical Issues (Fix Immediately)
- [Issue with impact and fix instructions]

### Warnings (Should Fix)
- [Issue with impact]

### Passed Checks
- [X] [Check name]

### Recommendations Priority Queue
1. [Highest impact fix]
2. [Second priority]

Module 4: Competitor Analysis

Trigger: analyze competitor [url] / 分析竞争对手 [URL]

Analysis Points

  1. Content Structure - Length, headings, media usage
  2. Keyword Coverage - What keywords they rank for that we don't
  3. Schema Implementation - Their structured data strategy
  4. SERP Features - Featured snippets, PAA presence
  5. Internal Linking - Their link architecture

Output Format

## Competitor Analysis: [URL]

### Content Comparison
| Metric | Competitor | Our Site | Gap |
|--------|------------|----------|-----|
| Avg. Content Length | | | |
| Schema Types | | | |

### Keyword Gap (They Rank, We Don't)
- [keyword 1]
- [keyword 2]

### Actionable Opportunities
1. [Opportunity with implementation suggestion]

Module 5: pSEO Page Generator

Trigger: generate pseo / 生成pSEO页面

Workflow

  1. Load/Create Data Source - data/pseo_data.json
  2. Generate Tech+Role Pages - app/templates/[tech]/[role]/page.tsx
  3. Generate Feature Pages - app/solutions/[feature]/page.tsx
  4. Ensure Content Uniqueness - Unique titles, descriptions, FAQs
  5. Update Sitemap - Add new routes to sitemap.ts
  6. Build Verification - Run npm run build to validate

Data Structure (pseo_data.json)

{
  "technologies": [
    {
      "slug": "nextjs",
      "name": "Next.js",
      "description": "The React Framework for the Web",
      "features": ["SSR", "SSG", "API Routes"],
      "relatedPosts": []
    }
  ],
  "roles": [
    {
      "slug": "frontend-developer",
      "name": "Frontend Developer",
      "keywords": ["React", "CSS", "JavaScript"],
      "challenges": ["responsive design", "performance"]
    }
  ],
  "features": [
    {
      "slug": "dark-mode",
      "name": "Dark Mode",
      "description": "Eye-friendly dark theme support",
      "benefits": ["reduced eye strain", "battery saving"]
    }
  ],
  "templates": {
    "techRole": {
      "titlePattern": "Best {tech} Portfolio for {role}s | Build Your Developer Portfolio",
      "descriptionPattern": "Create a stunning {role} portfolio with {tech}. Features include {features}."
    }
  }
}

Generated Page Structure

// app/templates/[tech]/[role]/page.tsx
export async function generateStaticParams() {
  // Returns all tech × role combinations
}

export async function generateMetadata({ params }) {
  // Dynamic meta tags based on tech + role
}

export default function TemplatePage({ params }) {
  // Unique content for each combination
  // - Hero section
  // - Features grid
  // - Related blog posts
  // - FAQ section with Schema
  // - CTA
}

Module 6: Internal Link Builder

Trigger: build internal links / 构建内链

Strategy

  1. Hub-and-Spoke Model

- Topic Hubs as central nodes - Blog posts as spokes - Guides as deep-dive connections

  1. Natural Anchor Text

- Identify keyword-rich phrases in content - Match with relevant target pages - Avoid over-optimization

  1. Link Distribution

- New posts → 2-3 internal links - Orphan pages → Add incoming links - High-authority pages → Use as link sources

Output

## Internal Link Report

### Site Link Graph Summary
- Total pages: X
- Average links per page: X
- Orphan pages: X

### Recommended Link Insertions
| Source | Anchor Text | Target | Reason |
|--------|-------------|--------|--------|

### Orphan Page Rescue
- [page] → Suggested link from [source]

Module 7: Full SEO Analysis

Trigger: seo analysis / SEO分析

Comprehensive Workflow

Step 1: Technical Health Check
    ↓
Step 2: Content Batch Scoring (all blog posts)
    ↓
Step 3: Keyword Gap Analysis (WebSearch for core topics)
    ↓
Step 4: Generate Prioritized Improvements
    ↓
Output: Comprehensive Report + Executable Fix List

Output

## Comprehensive SEO Analysis Report

Generated: [timestamp]

### Executive Summary
- Overall Health Score: [X]/100
- Critical Issues: X
- Quick Wins Available: X
- Estimated Impact: [High/Medium/Low]

### Technical Health
[Technical audit results]

### Content Analysis
[Batch content scoring]

### Keyword Opportunities
[Gap analysis results]

### Prioritized Action Items
1. [Highest impact, easiest fix]
2. [High impact]
3. ...

### One-Click Fixes Available
Run `apply seo fixes` to automatically fix X issues.

Integration with Existing Infrastructure

Leveraged Components

ComponentUsage
/api/seo-healthBase for technical audit
lib/schemas.tsSchema generation (if exists)
lib/content-similarity.tsRelated content for internal links
lib/topic-hubs.tsHub pages for pSEO
lib/guides.tsGuide data for link building
sitemap.tsAdd pSEO routes

Collaboration with ai-blog-writer

ai-blog-writer creates content
        ↓
pseo-engine optimizes content
        ↓
Publish optimized article

Safety Guidelines

Auto-Apply (Safe)

  • Meta description length adjustments
  • Missing alt text additions
  • Schema markup insertions
  • Sitemap updates

Require Confirmation

  • Title changes
  • Content restructuring
  • Deleting/replacing content
  • Creating new pages

Never Auto-Apply

  • Removing existing links
  • Changing URLs
  • Modifying canonical tags

Reference Files


Quick Commands Reference

CommandDescription
seo auditRun technical SEO health check
keyword research [topic]Research keywords for a topic
optimize content [path]Analyze and optimize a specific article
optimize all contentBatch analyze all blog posts
generate pseoGenerate programmatic SEO pages
build internal linksAnalyze and suggest internal links
analyze competitor [url]Analyze competitor page
seo analysisFull comprehensive SEO analysis
apply seo fixesApply all safe auto-fixes

平台分布

Codex

37.68%
按下载量换算23

Claude

32.45%
按下载量换算20

Cursor

17.34%
按下载量换算11

Gemini CLI

8.88%
按下载量换算6

安全审计

Gen Agent Trust Hub

可疑

Socket

通过

Snyk

可疑

权限和风险

需要联网

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills