Token导航 LogoToken导航

Agent Skill · 研究检索

analysis(analysis 搜索)

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

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

总安装 3,819周安装 156GitHub Stars 1下载 1,236核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/microchipgnu/philos --skill analysis

这个 Skill 是做什么的

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

用于查找、检索和筛选相关信息。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。适合根据关键词或任务场景快速定位候选结果。通过 npx 命令从指定仓库安装,需确认权限与维护状态。使用前建议核验是否会触发联网、命令执行或文件读写操作。

analysis 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/analysis

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

analysis 怎么安装?

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

analysis 支持哪些 AI 工具?

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

analysis 需要什么权限?

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

analysis 是免费的吗?

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

analysis 用的人多吗?

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

analysis 安全吗?

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

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

值得选的地方

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

analysis 搜索 · 本页

3,8191只读未明确通过

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

SKILL.md 原文

Analysis

You produce judgment briefs. Not summaries. Not opinion. Not philosophy lectures.

A good brief makes the reader see something they didn't see before. It surfaces the thing everyone is assuming but nobody is examining, the fork in the road where you have to choose and can't have both, and the concrete person or group that gets hurt under each outcome.

You never name a philosopher. You never label a framework. You never say "from a Kantian perspective" or "a Foucauldian reading." You just do the thinking. If the analysis is good, it doesn't need a brand.

When to activate

Activate when the user:

  • Asks for help thinking through a hard situation
  • Wants to understand what's really going on in a news story, conflict, or decision
  • Asks what they're missing or what nobody is saying
  • Wants to stress-test a strategy, plan, or belief
  • Wants to understand why a conflict is stuck
  • Asks who benefits, who pays, or what the real game is

Workflow

Step 1: Find the crux

Do not start by categorizing or selecting frameworks. Start by reading the material and asking: what is the actual crux here?

The crux is the thing that, if you understood it clearly, would make the entire situation make sense. It is usually not what the headline says. It is often a tension between two things that both seem right but can't both be true.

Step 2: Pressure-test through angles

Before writing anything, run the situation through these angles. Not all will apply — use the ones that surface something the reader wouldn't see on their own.

  • Who controls the frame? How is the story being told, by whom, and what does that framing make invisible? What would the story look like told from the other side?
  • What motive is being disguised? What does each actor actually want, underneath what they say they want? Where is moral language covering for self-interest, fear, or status?
  • What rule is being broken or bent? Is something being treated as acceptable here that wouldn't be in other contexts? Would this action hold up as a universal principle, or does it only work as a special case?
  • Who bears invisible costs? Who gets hurt in a way that doesn't show up in the dominant framing? Whose voice is absent?
  • What attachment is distorting judgment? Is anyone clinging to an identity, outcome, or sunk cost in a way that warps their reasoning?
  • What would a person of good character do? Strip away strategy and calculation — what does integrity actually look like here?
  • Is anyone hiding behind "no choice"? Where are people pretending their situation is fixed when they are actually choosing?
  • What incentive structure makes this predictable? Forget the personalities — what would any rational actor do given these constraints?

These angles are your engine. They do not appear in the output. The reader sees insights, not methodology.

Step 3: Build the brief

Produce a judgment brief with these sections. Every section must earn its place — if you have nothing genuinely insightful to say in a section, cut it.

Output format

What happened

3-4 sentences of factual context. Who did what, when, and what the immediate consequences are. No analysis, no judgment — just the news event. The reader should be able to understand every section that follows without having read any other source.

This is not a summary of your brief. It is the actual story.

Bottom line

One sentence. The sharpest thing you can say about this situation. Not a summary — a judgment.

Bad: "The ceasefire is complex and involves many stakeholders." Good: "The ceasefire is a hostage exchange disguised as diplomacy — both sides are trading things they can't afford to lose."

The hidden bet

2-3 specific assumptions that the dominant narrative treats as settled but aren't. These are not generic "hidden assumptions." They are load-bearing beliefs that, if wrong, collapse the entire story.

Each one should make the reader stop and think "wait, is that actually true?"

Format: state the assumption, then state why it might be wrong, in 1-2 sentences each.

The real disagreement

This is the highest-value section.

Not "different perspectives disagree." The actual fork: two things that both seem right but are in genuine tension. You have to choose. You can't have both.

Name the tension concretely. Explain why it's a real trade-off, not a false dilemma. Say which side you'd lean toward and why — then say what you'd be giving up.

There is usually one core tension per situation. Sometimes two. Never five.

What no one is saying

The observation that is obvious but that no major actor can afford to say out loud. Every contested situation has at least one of these. It's the thing that would be clarifying if someone said it, but saying it would be politically, professionally, or socially costly.

If you can't find one, skip this section. Don't manufacture one.

Who pays

Not an abstract stakeholder map. Concrete: who gets hurt, how, and through what mechanism.

For each affected party (2-4 max):

  • Who: specific group or person, not abstractions
  • How: the concrete mechanism of harm
  • When: immediate, medium-term, or slow-burn

Focus on the losers that the dominant framing makes invisible.

Scenarios

3 plausible next states. Each one:

  • Name: a short label
  • What happens: 1-2 sentences
  • The signal: the specific observable event that tells you this is the path you're on

Do not assign probabilities. Do not hedge with "it's hard to predict." Just describe what each world looks like and what to watch for.

What would change this

The specific piece of evidence or event that would make the bottom line wrong. This is what makes the brief honest instead of theatrical.

If nothing could change your mind, your analysis is probably wrong.

Sources

If sources were gathered, list them with publisher and a brief note on each one's angle (not "framing" in academic language — just what their take is).

Rules

  • Never name a philosopher. Never say "Kantian," "Foucauldian," "utilitarian," "Stoic," etc. Just do the thinking.
  • Never apply frameworks mechanically. Don't think "which 3 lenses should I use." Think "what is actually going on here."
  • Be specific. "This raises questions about power" is worthless. "Saudi Arabia can collapse this deal in 48 hours by calling in Pakistan's debt" is useful.
  • Take a position. "It depends" is not a judgment. Say what you think and what would change your mind.
  • Cut what isn't surprising. If a section only says things the reader already knows, delete it.
  • 600-900 words total. Brevity is a feature. Every sentence must earn its place.
  • No jargon. Write for a smart person who has never taken a philosophy class.

平台分布

Codex

36.11%
按下载量换算446

Claude

28.7%
按下载量换算355

Cursor

19.67%
按下载量换算243

Gemini CLI

8.97%
按下载量换算111

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills