ring 测试技能 Subag

AI 智能社区

作者仓库星标 189
作者仓库 ring

解读按原文结构重写，命令、链接、术语均保留；右侧可核对作者原始 SKILL.md

方法与流程

RED Phase: Watch It Fail：Run 3+ combined-pressure scenarios WITHOUT the skill. Document agent choices and rationalizations word-for-word. Why verbatim? Exact wording reveals the loopholes to close.
GREEN Phase: Write Minimal Skill：Address the specific failures documented in RED. Don't add hypothetical content — write just enough to address actual observed failures. Re-run same scenarios WITH skill; agent should now comply.
REFACTOR Phase: Close Loopholes：Agent still violated rule despite having the skill? Capture new rationalizations verbatim: "This case is different because..." "I'm following the spirit not the letter"

适用与边界

When to use：Before deploying a new skill After editing an existing skill Skill enforces discipline that could be rationalized away
当前原文没有单列不适用场景或限制。

原文中的明确线索

要点：「Complementary」、「Testing skills is TDD applied to process documentation.」、「Prerequisite」、「Skip」、「word-for-word」、「Why verbatim?」、「Pressure types」、「Best tests combine 3+ pressures.」
文件与命令：ring:test-driven-development、examples/CLAUDEMDTESTING.md、10k/min、3hr/200

流狐整理：以上内容来自当前 SKILL.md 的章节与原词；未补写作者没有声明的工具、兼容性或能力。

Testing Skills With Subagents

When to use

Before deploying a new skill
After editing an existing skill
Skill enforces discipline that could be rationalized away

Skip when

Pure reference skill → no behavior to test
No rules that agents have incentive to bypass

Complementary: ring:writing-skills, ring:test-driven-development

Testing skills is TDD applied to process documentation.

Run scenarios without the skill (RED — watch agent fail), write skill addressing those failures (GREEN), then close loopholes (REFACTOR).

Prerequisite: Understand ring:test-driven-development first. Complete worked example: examples/CLAUDE_MD_TESTING.md.

When to Test

Test skills that: enforce discipline (TDD, testing requirements), have compliance costs (time, effort, rework), could be rationalized away ("just this once"), or contradict immediate goals (speed over quality).

Skip: Pure reference skills (API docs), skills without rules to violate.

TDD Mapping

TDD Phase	Skill Testing	What You Do
RED	Baseline test	Run scenario WITHOUT skill, watch agent fail
Verify RED	Capture rationalizations	Document exact failures verbatim
GREEN	Write skill	Address specific baseline failures
Verify GREEN	Pressure test	Run WITH skill, verify compliance under pressure
REFACTOR	Plug holes	Find new rationalizations, add counters

RED Phase: Watch It Fail

Run 3+ combined-pressure scenarios WITHOUT the skill. Document agent choices and rationalizations word-for-word.

Why verbatim? Exact wording reveals the loopholes to close.

Writing Pressure Scenarios

Quality	Example
Bad	"What does the skill say?" — agent recites
Good	"Production down, $10k/min, 5min window" — single pressure
Great	"3hr/200 lines done, 6pm, dinner plans, forgot TDD. A) Delete B) Commit C) Tests now" — multi-pressure + forced choice

Pressure types: Time (deadline), sunk cost (hours invested), authority (senior says skip), economic (job at stake), exhaustion (end of day), pragmatic ("being realistic").

Best tests combine 3+ pressures.

GREEN Phase: Write Minimal Skill

Address the specific failures documented in RED. Don't add hypothetical content — write just enough to address actual observed failures. Re-run same scenarios WITH skill; agent should now comply.

REFACTOR Phase: Close Loopholes

Agent still violated rule despite having the skill? Capture new rationalizations verbatim:

"This case is different because..."
"I'm following the spirit not the letter"
"Being pragmatic means adapting"

For each rationalization, add: explicit negation rule, rationalization table entry, red flag entry.

Meta-test: "You read the skill and chose wrong anyway. How could the skill have been written to make the right answer the only acceptable one?"

Continue REFACTOR until no new rationalizations appear.

Signs of Bulletproof Skill

Agent chooses correct option under maximum pressure
Agent cites skill sections as justification
Agent acknowledges temptation but follows rule anyway
Meta-test reveals "skill was clear, I should follow it"

Real-World Impact

From applying TDD to TDD skill itself:

6 RED-GREEN-REFACTOR iterations to bulletproof
10+ unique rationalizations discovered
Each REFACTOR closed specific loopholes
Final: 100% compliance under maximum pressure

流狐档案作者与许可取自来源；运行、权限和网络为流狐检测或估算

流狐分类: AI 智能
作者声明 Agent: 未找到明确声明；不据此推断已兼容或已测试
静态检查: 88 / 100 · 启发式扫描，不代表运行安全
作者 / 版本 / 许可: @LerianStudio · 未声明 license
流狐 Token 估算: 低消耗
流狐接入估算: 即装即用
是否需要外部 API Key: 未发现要求
检测到的系统要求: 未声明
底层运行要求: 未声明
检测到的文件与系统行为: 只读
允许写入 / 修改
检测到的网络行为: 仅限本地
安装命令数: 无（仅作为资料）

档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。

需要注意： 未限定 allowed-tools，默认拥有全部工具权限。

输出预览 ring-testing-skills-with-subagents.preview

作者没有在当前 SKILL.md 中定义固定输出样例。

SKILL.md SKILL.md

# Testing Skills With Subagents

## When to use
- Before deploying a new skill
- After editing an existing skill
- Skill enforces discipline that could be rationalized away

## Skip when
- Pure reference skill → no behavior to test
- No rules that agents have incentive to bypass

## Related
**Complementary:** ring:writing-skills, ring:test-driven-development

**Testing skills is TDD applied to process documentation.**

Run scenarios without the skill (RED — watch agent fail), write skill addressing those failures (GREEN), then close loopholes (REFACTOR).

**Prerequisite:** Understand `ring:test-driven-development` first. Complete worked example: `examples/CLAUDE_MD_TESTING.md`.

## When to Test

Test skills that: enforce discipline (TDD, testing requirements), have compliance costs (time, effort, rework), could be rationalized away ("just this once"), or contradict immediate goals (speed over quality).

**Skip:** Pure reference skills (API docs), skills without rules to violate.

## TDD Mapping

| TDD Phase | Skill Testing | What You Do |
|-----------|---------------|-------------|
| RED | Baseline test | Run scenario WITHOUT skill, watch agent fail |
| Verify RED | Capture rationalizations | Document exact failures verbatim |
| GREEN | Write skill | Address specific baseline failures |
| Verify GREEN | Pressure test | Run WITH skill, verify compliance under pressure |
| REFACTOR | Plug holes | Find new rationalizations, add counters |

## RED Phase: Watch It Fail

Run 3+ combined-pressure scenarios WITHOUT the skill. Document agent choices and rationalizations **word-for-word**.

**Why verbatim?** Exact wording reveals the loopholes to close.

### Writing Pressure Scenarios

| Quality | Example |
|---------|---------|

…

证据边界与执行链路

作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。

章节    -> When to use → Skip when → Related → When to Test → TDD Mapping → RED Phase: Watch It Fail
要点    -> Complementary · Testing skills is TDD applied to process documentation. · Prerequisite · Skip · word-for-word · Why verbatim? · Pressure types · Best tests combine 3+ pressures.
文件/命令 -> ring:test-driven-development · examples/CLAUDEMDTESTING.md · 10k/min · 3hr/200
内容 SHA-256 -> 805ce08f01cf