Token导航 LogoToken导航

Agent Skill · 研究检索

claimify(claimify 搜索)

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

claimify 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证为 MIT,暂无第三方扫描结果,按安装量在研究检索类的 73,675 个 Skill 里排第 70,176。

总安装 212周安装 9GitHub Stars 公开资料未说明下载 74核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

AgentSkills.tonpx skills
npx skills add leegonzales/aiskills --skill "claimify"

这个 Skill 是做什么的

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

用于查找并安装 AI 代理技能,扩展宿主功能集。适合开发者探索可用工具与集成方案时使用。安装命令:npx skills add leegonzales/aiskills --skill "claimify"。应验证来源可靠性以防引入恶意代码。claimify 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

原始 README 未提供技能分类与过滤机制。

来源仓库内路径:skills/claimify

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add leegonzales/aiskills --skill "claimify";命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

claimify 怎么安装?

在终端执行 npx skills add leegonzales/aiskills --skill "claimify"。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

claimify 支持哪些 AI 工具?

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

claimify 需要什么权限?

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

claimify 是免费的吗?

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

claimify 用的人多吗?

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

claimify 安全吗?

没有查到第三方扫描结果,安全性无法从公开资料判断,安装前请自行审查源码、依赖和命令行为。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 许可证明确为 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调用外部服务未明确有提醒
claimify

claimify 搜索 · 本页

212—需要联网MIT未收录

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

SKILL.md 原文

name
claimify
description
Extract and structure claims from discourse into analyzable argument maps with logical relationships and assumptions. Use when analyzing arguments, red-teaming reasoning, synthesizing debates, or transforming conversations into structured claim networks. Triggers include "what are the claims," "analyze this argument," "map the logic," or "find contradictions.

Claimify

Extract claims from text and map their logical relationships into structured argument networks.

Overview

Claimify transforms messy discourse (conversations, documents, debates, meeting notes) into analyzable claim structures that reveal:

  • Explicit and implicit claims
  • Logical relationships (supports/opposes/assumes/contradicts)
  • Evidence chains
  • Argument structure
  • Tension points and gaps

Workflow

  1. Ingest: Read source material (conversation, document, transcript)
  2. Extract: Identify atomic claims (one assertion per claim)
  3. Classify: Label claim types (factual/normative/definitional/causal/predictive)
  4. Map: Build relationship graph (which claims support/oppose/assume others)
  5. Analyze: Identify structure, gaps, contradictions, implicit assumptions
  6. Output: Format as requested (table/graph/narrative/JSON)

Claim Extraction Guidelines

Atomic Claims

Each claim should be a single, testable assertion.

Good:

  • "AI adoption increases productivity by 15-30%"
  • "Psychological safety enables team learning"
  • "Current training methods fail to build AI fluency"

Bad (not atomic):

  • "AI is useful and everyone should use it" → Split into 2 claims

Claim Types

TypeDefinitionExample
FactualEmpirical statement about reality"Remote work increased 300% since 2020"
NormativeValue judgment or prescription"Organizations should invest in AI training"
DefinitionalEstablishes meaning"AI fluency = ability to shape context and evaluate output"
CausalX causes Y"Lack of training causes AI underutilization"
PredictiveFuture-oriented"AI adoption will plateau without culture change"
AssumptionUnstated premise[implicit] "Humans resist change"

Relationship Types

  • Supports: Claim A provides evidence/reasoning for claim B
  • Opposes: Claim A undermines or contradicts claim B
  • Assumes: Claim A requires claim B to be true (often implicit)
  • Refines: Claim A specifies/clarifies claim B
  • Contradicts: Claims are mutually exclusive
  • Independent: No logical relationship

Output Formats

Table Format (default)

| ID | Claim | Type | Supports | Opposes | Assumes | Evidence |
|----|-------|------|----------|---------|---------|----------|
| C1 | [claim text] | Factual | - | - | C5 | [source/reasoning] |
| C2 | [claim text] | Normative | C1 | C4 | - | [source/reasoning] |

Graph Format

Use Mermaid for visualization:

graph TD
    C1[Claim 1: AI increases productivity]
    C2[Claim 2: Training is insufficient]
    C3[Claim 3: Organizations should invest]
    
    C1 -->|supports| C3
    C2 -->|supports| C3
    C2 -.->|assumes| C4[Implicit: Change requires structure]

Narrative Format

Write as structured prose with clear transitions showing logical flow:

## Core Argument

The author argues that [main claim]. This rests on three supporting claims:

1. [Factual claim] - This is supported by [evidence]
2. [Causal claim] - However, this assumes [implicit assumption]
3. [Normative claim] - This follows if we accept [prior claims]

## Tensions

The argument contains internal tensions:
- Claims C2 and C5 appear contradictory because...
- The causal chain from C3→C7 has a missing premise...

JSON Format

For programmatic processing:

{
  "claims": [
    {
      "id": "C1",
      "text": "AI adoption increases productivity",
      "type": "factual",
      "explicit": true,
      "supports": ["C3"],
      "opposed_by": [],
      "assumes": ["C4"],
      "evidence": "Multiple case studies cited"
    }
  ],
  "relationships": [
    {"from": "C1", "to": "C3", "type": "supports", "strength": "strong"}
  ],
  "meta_analysis": {
    "completeness": "Missing link between C2 and C5",
    "contradictions": ["C4 vs C7"],
    "key_assumptions": ["C4", "C9"]
  }
}

Analysis Depth Levels

Level 1: Surface

  • Extract only explicit claims
  • Basic support/oppose relationships
  • No implicit assumption mining

Level 2: Standard (default)

  • Extract explicit claims
  • Identify clear logical relationships
  • Surface obvious implicit assumptions
  • Flag apparent contradictions

Level 3: Deep

  • Extract all claims (explicit + implicit)
  • Map full logical structure
  • Identify hidden assumptions
  • Analyze argument completeness
  • Red-team reasoning
  • Suggest strengthening moves

Best Practices

  1. Be charitable: Steelman arguments before critique
  2. Distinguish: Separate what's claimed from what's implied
  3. Be atomic: One claim per line, no compound assertions
  4. Track evidence: Note source/support for each claim
  5. Flag uncertainty: Mark inferential leaps
  6. Mind the gaps: Identify missing premises explicitly
  7. Stay neutral: Describe structure before evaluating strength

Common Patterns

Argument Chains

Premise 1 (factual) → Premise 2 (causal) → Conclusion (normative)

Implicit Assumptions

Often found by asking: "What must be true for this conclusion to follow?"

Contradictions

Watch for:

  • Same speaker, different times
  • Different speakers, same topic
  • Explicit vs implicit claims

Weak Links

  • Unsupported factual claims
  • Causal claims without mechanism
  • Normative leaps (is → ought)
  • Definitional ambiguity

Examples

See references/examples.md for detailed worked examples.

平台分布

Claude Code

30.67%
按下载量换算23

windsurf

23.68%
按下载量换算18

OpenCode

15.77%
按下载量换算12

Codex

13.25%
按下载量换算10

Antigravity

8.49%
按下载量换算6

Gemini CLI

3.19%
按下载量换算2

安全审计

暂无安全审计结果可展示。

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills