Token导航 LogoToken导航

Agent Skill · 研究检索

harvest(harvest 搜索)

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

harvest 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 47,935。

总安装 710周安装 29GitHub Stars 公开资料未说明下载 230核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/shihyuho/skills --skill harvest

这个 Skill 是做什么的

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

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

当前尚无详细功能描述,需查阅原始 SKILL.md 获取更多信息。

来源仓库内路径:skills/harvest

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

harvest 怎么安装?

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

harvest 支持哪些 AI 工具?

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

harvest 需要什么权限?

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

harvest 是免费的吗?

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

harvest 用的人多吗?

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

harvest 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

  • 同时适配 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调用外部服务未明确有提醒
harvest

harvest 搜索 · 本页

710—只读未明确通过

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

SKILL.md 原文

Planning Second Brain

Create and maintain a project second brain without replacing source-of-truth planning files.

Core Contract

  • Treat task_plan.md, findings.md, and progress.md as the only source of truth (SOT).
  • Write second-brain outputs into docs/notes using Obsidian-compatible Markdown.
  • Never let docs/notes overwrite or redefine source-of-truth files.
  • Route all entrypoints through one deterministic capture workflow.

Required Skill Composition

  1. Invoke planning-with-files first for primary planning workflow.
  2. Invoke obsidian-markdown when writing or updating second-brain Markdown.

Trigger Contract

Use this skill when users ask to:

  • keep project memory over time
  • summarize milestones into reusable notes
  • record stable decisions and knowledge
  • build an Obsidian-friendly project knowledge base
  • read intents: find prior decision, look up past context, trace project timeline, retrieve existing second-brain note

Do not use this skill for unrelated implementation work that does not involve capture, summarization, or project memory publishing.

Output Locations

  • docs/notes/index.md
  • docs/notes/projects.md
  • docs/notes/decisions.md
  • docs/notes/knowledge.md
  • docs/notes/harvest-quality.md
  • docs/notes/projects/<project>/timeline/YYYY-MM-DD.md
  • docs/notes/decisions/*.md
  • docs/notes/knowledge/*.md
  • docs/notes/harvest-quality/YYYY-MM-DD-<project-slug>-harvest-review.md
  • docs/notes/harvest-quality/rollups/YYYY-MM-<project-slug>-harvest-optimization.md

Create missing folders/files when absent.

Progressive Disclosure Read Workflow (Required)

Follow this read order before any retrieval or context lookup:

  1. Read docs/notes/index.md to discover available hubs.
  2. Read the intent hub: docs/notes/projects.md, docs/notes/decisions.md, or docs/notes/knowledge.md.
  3. Read only targeted leaf notes that match the intent.

Stop condition:

  • Stop when the target note is found, or after two consecutive reads that add no novel information.

Hard constraints:

  • Never start from deep leaves unless the user provides an exact path.
  • Treat docs/notes as retrieval-only; never capture or summarize docs/notes back into docs/notes.
  • Preserve the anti-recursion guard and existing SOT-only contract (task_plan.md, findings.md, progress.md).
  • Do not expand read scope beyond the minimal files needed for the requested intent.

Reference example:

Deterministic Workflow (Required)

Run this workflow in order for every entrypoint (manual trigger phrases, slash-command wrappers, and plugin-driven invocation):

  1. Preflight

- Confirm SOT inputs exist: task_plan.md, findings.md, progress.md. - Confirm output root: docs/notes. - Set mode: capture, status, audit, review, or optimize. - For optimize mode, collect optional user-provided report directories as additional input roots.

  1. Bootstrap

- Ensure required minimal docs/notes files and templates exist. - Apply contract in references/publishing-and-dedupe.md.

  1. Extract Candidates

- Apply contracts in references/extraction-and-classification.md.

  1. Classify

- Route each candidate using the classification decision table contract.

  1. Publish

- Append same-day timeline events and update decision/knowledge notes with dedupe.

  1. Verify and Report

- Run verification checklist. - For review and optimize, apply references/quality-reports.md.

Candidate Schema and Extraction Rules (Required)

Candidate fields MUST include:

  • source_ref, change, why, candidate_type, confidence
  • optional: sot_fingerprint, exclusion_reason, unresolved_source_ref

Apply full extraction/classification contract in references/extraction-and-classification.md.

Publish Confirmation Semantics (Required)

  1. Extract candidate.
  2. Validate schema fields and thresholds.
  3. Publish into target note.
  4. Mark committed after publish succeeds.

Apply full publishing contract in references/publishing-and-dedupe.md.

First-Run Bootstrap (Required)

If docs/notes is missing, or if any required minimal file is missing, bootstrap from references/bootstrap/.

Apply the required minimal files list and bootstrap rules in references/publishing-and-dedupe.md.

Publishing Strategy

Apply classification, timeline, and milestone publish contracts in references/extraction-and-classification.md.

Review Report Mode (Required)

Use review mode to evaluate harvest output quality and persist one reusable report for later optimization planning.

Apply full review contract in references/quality-reports.md.

Review Rollup Mode (Required)

Use optimize mode to aggregate multiple review reports into one optimization roadmap.

Apply full rollup contract in references/quality-reports.md.

Execution Contract (Required)

  • Treat trigger methods as entrypoints only (manual phrases, slash-command wrappers, plugin-driven calls).
  • MUST route all entrypoints through the same deterministic workflow.
  • Produce equivalent output for equivalent source input regardless of trigger method.
  • Do not implement separate dedupe behavior per trigger entrypoint.
  • Keep plugin-driven capture behavior contract-compatible with manual entrypoints.
  • Keep review and optimize modes repo-agnostic. Do not hardcode project-specific heuristics as universal rules.

Source Extraction Boundaries (Required)

Extract with allowlist rules from source-of-truth files. Do not summarize everything.

Apply full allowlist/denylist and thresholds in references/extraction-and-classification.md.

Harvest Exclusion Markers

Support explicit exclusion markers inside source-of-truth files:

  • <!-- harvest:exclude:start -->
  • <!-- harvest:exclude:end -->

Ignore content inside this block during harvest publishing.

Anti-Recursion Guard

  • Do not summarize notes under docs/notes back into new notes.
  • Use source-of-truth files as input only (task_plan.md, findings.md, progress.md).
  • Skip entries that only describe harvest's own publishing activity.

Dedupe and Fingerprint Contract (Required)

  • Timeline events MUST include sot_fingerprint.
  • Compute sot_fingerprint from normalized source_ref + change + why.
  • Same timeline day + same sot_fingerprint means no-op (do not append duplicate block).
  • Equivalent source input must produce equivalent no-op behavior across manual and plugin entrypoints.

Fingerprint normalization:

  1. Trim leading/trailing whitespace on source_ref, change, and why.
  2. Collapse internal whitespace to single spaces.
  3. Lowercase each part.
  4. Join as <source_ref>||<change>||<why>.
  5. Compute SHA-256 hex lowercase.

Reference example:

Note Rules

  • Keep notes concise and reusable.
  • Include traceability metadata in formal notes.
  • Summarize; do not paste large verbatim source-of-truth sections.

Verification Checklist

Before finalizing updates:

  1. Every formal note has source_files, source_date, and source_ref.
  2. Every timeline event has source_ref and sot_fingerprint.
  3. docs/notes/index.md links to latest decisions and knowledge.
  4. No reverse edits were made to task_plan.md, findings.md, progress.md by second-brain steps.
  5. No large copied source-of-truth blocks appear in formal notes.
  6. In review mode, report file includes scorecard, deductions, and path-based evidence.
  7. In optimize mode, rollup file includes coverage counts, aggregated scores, roadmap priority, and source report paths.
  8. In optimize mode, rollup file includes input root resolution results (included + skipped + reasons).

Failure Handling

  • If source_ref cannot be resolved, set note status: draft and record unresolved_source_ref.
  • Do not block the source-of-truth workflow because of second-brain publish errors.

Non-Goals

  • Do not modify global IDE/user rule files.
  • Do not add mandatory always-on conversation loops.
  • Do not turn this skill into a general cross-skill memory engine.
  • Do not collect or persist tool chatter as project knowledge.

Anti-Patterns

  • Treating second-brain notes as execution-state files.
  • Creating parallel truth that conflicts with source-of-truth planning files.
  • Defining trigger-specific behavior that diverges from the deterministic workflow.

平台分布

Codex

35.65%
按下载量换算82

Claude

30.35%
按下载量换算70

Cursor

18.61%
按下载量换算43

Gemini CLI

9.77%
按下载量换算22

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills