Token导航 LogoToken导航TokenDH.com
研究检索执行命令github未标认证来源可访问许可证需确认审计提醒

rp-why回答为什么

Agent Skill

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

总安装

1,088

周安装

44

GitHub Stars

11

下载量

341
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

简介

rp-why 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词快速定位候选结果时使用。

  • 适用于研究检索类任务,可结合来源仓库和原始 README 核验具体用法。
  • 通过 npx skills add 命令从 GitHub 安装,需确认权限范围和维护状态。
  • 使用前建议检查是否会触发联网、命令执行或文件读写等敏感操作。
  • rp-why 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

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

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

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 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills