Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问clear审计提醒

analyzing-source分析来源

Agent Skill

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

总安装

235

周安装

10

GitHub Stars

24

下载量

82
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

简介

深度解析单一信息来源并生成综合摘要。

  • 支持 URL 抓取与主题驱动的智能检索。
  • 优先选择权威且内容详实的原生文档。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。
  • 适用于研究合成与知识库构建任务。analyzing-source 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 自动尝试替代方案以确保来源可访问性。

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.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

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 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。

来源信息

继续浏览同类 Skills