Token导航 LogoToken导航

Agent Skill · 研究检索

rp-why(回答为什么)

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

rp-why 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为执行命令;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 42,313。

总安装 1,088周安装 44GitHub Stars 11下载 341核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/block/agent-skills --skill rp-why

这个 Skill 是做什么的

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

rp-why 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词快速定位候选结果时使用。适用于研究检索类任务,可结合来源仓库和原始 README 核验具体用法。通过 npx skills add 命令从 GitHub 安装,需确认权限范围和维护状态。

使用前建议检查是否会触发联网、命令执行或文件读写等敏感操作。rp-why 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/rp-why

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

rp-why 怎么安装?

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

rp-why 支持哪些 AI 工具?

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

rp-why 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 npx skills add https://github.com/block/agent-skills --skill rp-why 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

rp-why 是免费的吗?

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

rp-why 用的人多吗?

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

rp-why 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 需要执行命令,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 不能接受 Skill 在你机器上执行命令的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 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调用外部服务未明确有提醒
rp-why

回答为什么 · 本页

1,08811执行命令未明确有提醒

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

SKILL.md 原文

rp-why: Gas Town × DOK Framework

Overview

The rp-why skill is a self-reflection framework that helps AI practitioners measure and improve their AI collaboration practice. It combines two powerful dimensions:

  • Horizontal Axis: Gas Town Stages — Measures AI tool adoption maturity from basic chatbots to multi-agent orchestration
  • Vertical Axis: DOK Levels — Measures the cognitive complexity of prompts from simple recall to extended thinking

The intersection of these dimensions reveals growth opportunities and helps users maximize the value they extract from their AI tools.


How to Use This Skill

Installation

Install the skill using the skills CLI:

npx skills add https://github.com/block/agent-skills --skill rp-why

Make sure you have the built-in skills extension enabled in your agent (Goose, Claude Desktop, etc.).

Using Slash Commands

Once the skill is loaded, you can use slash commands directly in your conversation:

You: /rp-why current

Goose will analyze your current session and provide:

  • Your Gas Town stage assessment
  • DOK distribution breakdown
  • Quadrant position
  • Growth nudges

Available Commands

CommandWhat It Does
/rp-why currentAnalyze the current session
/rp-why initGenerate a baseline from your history
/rp-why compareCompare current session to baseline

Alternative: Natural Language

You don't have to use slash commands. You can also just ask naturally:

You: Analyze my AI collaboration patterns using the Gas Town DOK framework
You: What's my DOK distribution for this session?
You: How does this session compare to my baseline?

The skill will recognize these requests and provide the same analysis.

When to Use

  • End of session: Run /rp-why current to reflect on your work
  • Weekly: Run /rp-why compare to track progress
  • First time: Run /rp-why init to establish your baseline

Problem Statement

Many AI practitioners face a hidden inefficiency: a mismatch between tool sophistication and task cognitive complexity.

Anti-PatternImpact
Using powerful autonomous agents for simple "what is X?" queriesUnrealized potential
Asking deep strategic questions through basic chatbot interfacesBottlenecked thinking
No visibility into personal AI usage patternsStagnant growth
No framework for intentional growth in AI collaboration skillsMissed opportunities

Without measurement, there's no improvement. Users need a mirror to see their AI collaboration patterns clearly.


The Framework

Yegge's 8 Gas Town Stages (AI Tool Adoption)

From Steve Yegge's "Welcome to Gas Town" (January 2026):

StageNameDescription
8Full Gas TownComplete AI-native development ecosystem
7Agentic WorkflowsAutomated pipelines with agent coordination
6Multi-AgentOrchestrating multiple specialized agents
5CLI Single Agent, YOLOTerminal-based autonomous agent (e.g., Goose)
4Chat IDEIntegrated chat in development environment
3CopilotUsing AI code completion, inline suggestions
2CuriousExperimenting with basic chatbots occasionally
1ObserverWatching and evaluating AI tools, not yet actively using

Webb's DOK Levels (Cognitive Complexity)

From Norman Webb's Depth of Knowledge framework (1997):

LevelNameDescriptionPrompt Indicators
4Extended ThinkingComplex investigation, multiple sessions"Research and synthesize...", "Create a framework...", "Investigate over time..."
3Strategic ThinkingReasoning, planning, analysis, synthesis"Design...", "Analyze...", "What if...", "Develop a strategy..."
2ApplicationApply concepts, make decisions, compare"How would you...", "Compare...", "Explain why..."
1RecallFacts, definitions, simple procedures"What is...", "List...", "Define..."

Integration Matrix (Stage × DOK)

The intersection creates six distinct zones:

              DOK 1        DOK 2         DOK 3          DOK 4
            (Recall)   (Application) (Strategic)   (Extended)
           ┌──────────┬──────────────┬────────────┬────────────┐
Stage 6-8  │   Over-  │    Over-     │ Underutil- │  Frontier  │
(Multi/    │  powered │   powered    │   izing    │            │
 Agentic)  │          │              │            │            │
           ├──────────┼──────────────┼────────────┼────────────┤
Stage 5    │   Over-  │  Underutil-  │  Expected  │  Growing   │
(CLI YOLO) │  powered │    izing     │            │            │
           ├──────────┼──────────────┼────────────┼────────────┤
Stage 3-4  │   Over-  │   Expected   │  Growing   │  Frontier  │
(Copilot/  │  powered │              │            │            │
 Chat IDE) │          │              │            │            │
           ├──────────┼──────────────┼────────────┼────────────┤
Stage 1-2  │ Expected │   Growing    │  Thinking  │  Thinking  │
(Observer/ │          │              │   Ahead    │   Ahead    │
 Curious)  │          │              │            │            │
           └──────────┴──────────────┴────────────┴────────────┘

Zone Definitions:

ZoneDescriptionAction
FrontierPushing boundaries of both tool and cognitionCelebrate & Document
Thinking AheadHigh cognitive work with basic toolsUpgrade tools
GrowingStretching into higher complexity, positive trajectoryEncourage
ExpectedAppropriate match of tool sophistication to task complexityMaintain
UnderutilizingSophisticated tools for simpler tasksIncrease DOK
OverpoweredTools exceed task needs—opportunity to level up your questionsRealign

Commands

/rp-why current

Analyze the current session's Gas Town stage and DOK distribution.

Output includes:

  • Stage assessment with confidence level
  • DOK distribution breakdown with percentages
  • Quadrant position visualization
  • Contextual growth nudges
  • Reflection prompt

/rp-why init

Generate a baseline from your conversation history (analyzes available sessions).

Output includes:

  • Historical analysis period and session count
  • Baseline DOK distribution
  • Typical Gas Town stage
  • Growth targets
  • Baseline saved to ~/.config/goose/rp-why-baseline.json

/rp-why compare

Compare current session against your established baseline.

Output includes:

  • Side-by-side DOK comparison (baseline vs current)
  • Quadrant movement visualization
  • Progress toward growth targets
  • Trajectory analysis

Sample Output

╔══════════════════════════════════════════════════════════════════╗
║                    rp-why: CURRENT SESSION                       ║
╚══════════════════════════════════════════════════════════════════╝

GAS TOWN STAGE: 5 (CLI Single Agent, YOLO)

DOK DISTRIBUTION
────────────────────────────────────────────────────────────────────
DOK 1 (Recall):      ████░░░░░░░░░░░░░░░░  17%
DOK 2 (Application): ████████████░░░░░░░░  52%
DOK 3 (Strategic):   ██████░░░░░░░░░░░░░░  26%
DOK 4 (Extended):    █░░░░░░░░░░░░░░░░░░░   5%

QUADRANT: Underutilizing
────────────────────────────────────────────────────────────────────
You're using powerful autonomous tools—there's an opportunity to
match your questions to that power.

GROWTH NUDGES
────────────────────────────────────────────────────────────────────
1. Shift 2-3 DOK 2 prompts to DOK 3 by adding "analyze trade-offs"
2. Before simple queries, ask: "Can I make this more strategic?"
3. Try one DOK 4 extended investigation this week

🪞 REFLECTION
────────────────────────────────────────────────────────────────────
What complex challenge could benefit from your agent's full
capabilities today?

Target User Profiles

ProfileTypical StageDOK DistributionCharacteristics
Traditional1-2DOK1: 60%, DOK2: 30%, DOK3: 10%Minimal AI use
Adopter3-4DOK1: 40%, DOK2: 40%, DOK3: 15%, DOK4: 5%Growing comfort
Practitioner5DOK1: 25%, DOK2: 45%, DOK3: 25%, DOK4: 5%Autonomous agents
Advanced5-6DOK1: 15%, DOK2: 35%, DOK3: 35%, DOK4: 15%Strategic use
Frontier7-8DOK1: 10%, DOK2: 25%, DOK3: 40%, DOK4: 25%Agentic workflows

Growth Nudge Reference

Frontier (High Stage, High DOK)

  • "You're pushing boundaries—document what you learn"
  • "Share patterns with others; teach what works"
  • "Explore the edges: what's not yet possible?"

Thinking Ahead (Low Stage, High DOK)

  • "Your thinking exceeds your tools—time to upgrade!"
  • "Explore CLI agents or IDE integration"
  • "Your DOK is strong; let better tools amplify it"

Underutilizing (High Stage, Lower DOK)

  • "Powerful tools deserve powerful questions"
  • "Before each prompt, ask: Can this be more strategic?"
  • "Batch simple queries; save the agent for complex work"

Learning Zone (Low Stage, Low DOK)

  • "This is a natural starting point—focus on learning the tools"
  • "Try one new AI capability each session"
  • "Don't worry about DOK yet—get comfortable first"

Overpowered (High Stage, Low DOK)

  • "Your tools exceed your task needs—opportunity to level up your questions"
  • "Consider: Is this query worth an autonomous agent?"
  • "Batch simple lookups; reserve agent for strategic work"

Upgrading Your Prompts

DOK LevelPrompt PatternExample
1 → 2Add "how" or "why""What is a mutex?" → "How would I use a mutex here?"
2 → 3Add "trade-offs" or "design""How do I implement caching?" → "Design a caching strategy considering our constraints"
3 → 4Extend across sessions"Analyze this architecture" → "Research caching patterns over multiple sessions and synthesize recommendations"

Attribution

  • Gas Town Stages: Steve Yegge, "Welcome to Gas Town" (January 2026) https://steve-yegge.medium.com/welcome-to-gas-town-4f25ee16dd04
  • Depth of Knowledge (DOK): Norman Webb (1997) Webb, N. L. (1997). Criteria for alignment of expectations and assessments in mathematics and science education. Council of Chief State School Officers.

Version History

VersionDateChanges
3.02026-02Quadrant visualization, growth nudges, reflection prompts, updated terminology
2.x2026-01Integration matrix, target profiles, baseline comparison
1.x2025-12Initial Gas Town stages, basic DOK tracking

平台分布

Codex

37.91%
按下载量换算129

Claude

30.23%
按下载量换算103

Cursor

19.06%
按下载量换算65

Gemini CLI

10.3%
按下载量换算35

安全审计

Gen Agent Trust Hub

可疑

Socket

通过

Snyk

通过

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/block/agent-skills --skill rp-why 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

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

继续浏览同类 Skills