Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

analysisanalysis 搜索

Agent Skill

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

总安装

3,819

周安装

156

GitHub Stars

1

下载量

1,236
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

简介

用于查找、检索和筛选相关信息。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

  • 适合根据关键词或任务场景快速定位候选结果。
  • 通过 npx 命令从指定仓库安装,需确认权限与维护状态。
  • 使用前建议核验是否会触发联网、命令执行或文件读写操作。
  • analysis 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

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.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

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