Token导航 LogoToken导航

Agent Skill · 研究检索

toc-builder(目录生成器)

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

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

总安装 519周安装 21GitHub Stars 公开资料未说明下载 163核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/gasserane/personal-skills --skill toc-builder

这个 Skill 是做什么的

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

toc-builder 用于查找、检索和筛选相关信息。适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词、任务场景或来源线索快速定位候选结果。通过 npx skills add 命令从指定 GitHub 仓库安装使用。

安装前需确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。建议结合原始 README 核验具体用法和功能边界。

来源仓库内路径:skills/toc-builder

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

toc-builder 怎么安装?

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

toc-builder 支持哪些 AI 工具?

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

toc-builder 需要什么权限?

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

toc-builder 是免费的吗?

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

toc-builder 用的人多吗?

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

toc-builder 安全吗?

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

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

值得选的地方

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

目录生成器 · 本页

519—只读未明确通过

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

SKILL.md 原文

Theory of Change Builder

A ToC is not a logic model with arrows. It is an argument about how change happens, with the assumptions made visible and testable. This skill enforces that standard.

When to use

Trigger for theory-of-change work: new programme design, ToC revision, pathway analysis, programme logic review, funder-required ToC submissions, or ToC critique.

Do not trigger for routine results frameworks, logframes, or indicator lists — those are downstream of the ToC.

Required inputs

Ask in one batch. Do not start drafting without the first four.

  1. Long-term outcome or vision: the change Ane wants the programme to contribute to, stated in language the target population would recognise (required)
  2. Target population and context: who, where, what constraints shape their lives (required)
  3. Programme scope: what interventions the programme can actually deliver (required)
  4. Timeframe: short (12 mo), medium (3 yr), long (5-10 yr) markers (required)
  5. Existing analysis: prior ToC, needs assessment, or evaluation findings (optional)
  6. Feminist political economy analysis: who holds power in this system, how gender and other axes shape access (optional but required for SRHR; will prompt if missing)

Method

Work backward from the long-term outcome. Never forward from activities.

Step 1 — articulate the vision

Write the long-term outcome as one sentence. Must be specific enough to be falsifiable. "Improved SRHR outcomes" fails. "Adolescent girls in [region] access quality contraception within 30 minutes' travel, without third-party consent" passes.

Step 2 — identify preconditions

What must be true for the long-term outcome to hold? List preconditions at medium-term and short-term horizons. Each precondition is itself a change state, not an activity.

Step 3 — surface the causal links

For every link between preconditions, name:

  • Causal claim: why does A lead to B in this context?
  • Assumption: what must be true, outside the programme's control, for A to actually lead to B?
  • Evidence status: *tested* (cite the source), *plausible* (cite the framework), or *untested* (flag for evidence gap)

Step 4 — apply the feminist political economy lens

Do not skip this, even if the programme is not labelled SRHR. For each node:

  • Whose interests does this change serve? Whose interests does it threaten?
  • What power relations must shift for this change to stick?
  • Which voices defined this outcome? Who was consulted? Who co-designed?

If these questions cannot be answered, mark the precondition with ⚠️ Feminist political economy analysis missing.

Step 5 — identify threats to the ToC

From Mayne (2019): what alternative explanations would account for the expected change if the programme were not running? What other contributions are likely? Name them.

Step 6 — define the contribution question

State the evaluative question the ToC must eventually answer. Follow Mayne (2019) phrasing: "To what extent and in what ways did the programme contribute to [outcome], given other contributions and context?"

Step 7 — plan the evidence

For each assumption, name:

  • What would confirm it?
  • What would disconfirm it?
  • What data source could provide that evidence?
  • When will the ToC be revisited in light of the evidence?

Output structure

Produce a ToC document with these sections under these H2s:

  1. Vision — one sentence, as described in Step 1
  2. Context and population — two paragraphs max
  3. Pathway diagram — text representation: each precondition as a node, each link described in one sentence. If the user needs a visual, produce Mermaid source.
  4. Preconditions by horizon — three columns (short / medium / long), each precondition one line
  5. Causal claims and assumptions — table: *From → To*, *Causal claim*, *Assumption*, *Evidence status*
  6. Feminist political economy analysis — per-node power and participation notes
  7. Threats to the ToC — rival explanations and other contributions
  8. Contribution question — one sentence
  9. Evidence plan — table: *Assumption*, *Confirming evidence*, *Disconfirming evidence*, *Data source*, *Revisit date*
  10. Data gaps — ⚠️ Data gap: entries for anything missing

Citation requirements

Every framework claim cites author and year. Mandatory versions:

  • Vogel (2012) "Review of the Use of 'Theory of Change' in International Development" (DFID)
  • van Eerdewijk et al. (2017) "White Paper: A Conceptual Model of Women and Girls' Empowerment" (KIT)
  • Mayne (2019) "Revisiting the Contribution Question" *Evaluation* 25(3)
  • Cornwall & Rivas (2015) for feminist framing when relevant

Writing rules

Follow CLAUDE.md house style. No hedging in causal claims — if the claim is uncertain, state that the evidence is untested. No logical leaps — if Step 3 cannot name the causal mechanism, mark the link as ⚠️ Untested mechanism.

Limitations

This skill does not generate indicators. Route to indicator-designer after the ToC is stable. It does not replace stakeholder consultation — it structures the analysis Ane brings from that consultation.

平台分布

Codex

35.96%
按下载量换算59

Claude

30.68%
按下载量换算50

Cursor

18.25%
按下载量换算30

Gemini CLI

9.38%
按下载量换算15

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills