Token导航 LogoToken导航

Agent Skill · 研究检索

analyzing-source(分析来源)

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

analyzing-source 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证为 MIT,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 68,166。

总安装 235周安装 10GitHub Stars 24下载 82核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/sawyer-middeleer/dot-claude --skill analyzing-source

这个 Skill 是做什么的

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

深度解析单一信息来源并生成综合摘要。支持 URL 抓取与主题驱动的智能检索。优先选择权威且内容详实的原生文档。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。适用于研究合成与知识库构建任务。

analyzing-source 属于研究检索类 Skill,可作为该场景下的辅助能力补充。自动尝试替代方案以确保来源可访问性。

来源仓库内路径:skills/analyzing-source

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

analyzing-source 怎么安装?

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

analyzing-source 支持哪些 AI 工具?

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

analyzing-source 需要什么权限?

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

analyzing-source 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

analyzing-source 用的人多吗?

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

analyzing-source 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 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调用外部服务未明确有提醒
analyzing-source

分析来源 · 本页

23524需要联网MIT有提醒

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

SKILL.md 原文

Analyzing Source

This skill guides you through analyzing a single source in depth and creating a comprehensive summary suitable for research synthesis.

Process

Follow these steps to analyze a source and create a comprehensive summary:

Step 1: Source Discovery and Retrieval

If given a URL:

  • Fetch it directly using WebFetch
  • Verify the content is accessible and relevant

If given a topic or search query:

  • Use WebSearch to find the best source on the topic
  • Prioritize authoritative, detailed sources
  • Fetch the most relevant result using WebFetch

If source is inaccessible or low-quality:

  • Try alternative sources
  • Be persistent in finding substantive information
  • Note any access issues in your summary

Step 2: Deep Analysis

Conduct thorough analysis focusing on:

  • Core concepts, definitions, and frameworks presented in the source
  • Main arguments, claims, and findings - what is the source asserting?
  • Evidence, data, and examples - what supports the claims?
  • Methodologies or approaches - how was this work conducted?
  • Limitations, caveats, and counterarguments - what are the boundaries?
  • Connections to broader themes - how does this relate to the research focus?
  • Quality and credibility - how reliable is this source?
  • Unique insights or perspectives - what new understanding does this offer?

Step 3: Create Comprehensive Summary

Use the template from ./templates/article-summary.md to create your summary.

VERY IMPORTANT: Your summary must be concise yet thorough, which means being extreme information-dense and leveraging key data as much as possible.

Template structure includes:

  • Executive summary
  • Key concepts & definitions
  • Main arguments/findings with evidence
  • Methodology/approach
  • Specific examples & case studies
  • Notable quotes
  • Critical evaluation
  • Relevance to research focus
  • Practical implications

Key principles:

  • Include specific quotes and examples, not just paraphrasing
  • Provide analytical insights about significance and relevance
  • Make clear connections to the research focus provided
  • Be detailed enough that someone can understand the source without reading the original

Step 4: Save Summary File

Create filename:

  • Use a descriptive slug based on the source
  • Example: kubernetes-scaling-patterns.md, netflix-chaos-engineering.md

Save location:

  • Save to: {working_directory}/summaries/{filename}.md
  • Use the complete template structure
  • Ensure all sections are filled out

Step 5: Report Results

Provide a brief report including:

  1. Confirmation of what source you analyzed
  2. The file path where you saved the summary
  3. A 2-3 sentence overview of the most important insights discovered

Important Guidelines

  • Be thorough, not brief: This is deep research, not light scanning. Capture nuance and detail.
  • Include specific evidence: Direct quotes, data points, examples - not just general statements.
  • Think critically: Note limitations, assess quality, identify assumptions.
  • Stay focused: While being comprehensive, ensure everything relates to the research focus.
  • Be self-contained: Your summary should make sense without reading the original source.
  • Save your work: Always save the summary file - the main coordinator depends on it.

Example Execution

Input received:
- Source topic: "Kubernetes horizontal pod autoscaling best practices"
- Research focus: "Scalability patterns in cloud-native systems"
- Working directory: /Users/research/cloud-native-scaling

Step 1: Using WebSearch to find authoritative source on Kubernetes HPA...
Found: kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/
Fetching with WebFetch...

Step 2: Analyzing content...
- Identified core HPA concepts: target metrics, scale-up/down policies, cooldown periods
- Found detailed configuration examples with CPU and custom metrics
- Noted limitations around cluster resources and metric collection latency

Step 3: Creating comprehensive summary using template...
- Executive summary: 3 paragraphs covering main patterns and tradeoffs
- Key concepts: HPA, target utilization, metric servers, custom metrics API
- Main findings: 5 configuration patterns with evidence from examples
- 8 notable quotes extracted from official docs and linked blog posts
- Evidence quality: High (official documentation + real-world examples)

Step 4: Saving summary...
Created: /Users/research/cloud-native-scaling/summaries/kubernetes-hpa-best-practices.md

Step 5: Report
Source analyzed: Kubernetes official documentation on Horizontal Pod Autoscaling
Saved to: /Users/research/cloud-native-scaling/summaries/kubernetes-hpa-best-practices.md

Key insights: This source provides detailed HPA configuration patterns with real-world examples from production systems at scale. Most valuable finding is the discussion of custom metrics integration and the tradeoffs between reactive vs predictive scaling approaches. Also documents common pitfalls like resource request misconfiguration causing scaling issues.

平台分布

Claude Code

30.44%
按下载量换算25

windsurf

21.37%
按下载量换算18

trae

16.89%
按下载量换算14

OpenCode

11%
按下载量换算9

Cursor

8.17%
按下载量换算7

Codex

3.16%
按下载量换算3

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills