Install any skill in seconds. Free to start, no credit card required.
Get Started Free →doccker/cc-core-defensive
通用防御性编码规范,适用于跨语言代码修改中的最小改动、真实边界处理、定向验证,以及约束假想风险驱动的过度兜底或抽象;不负责语言细节、正式 review 或结构化 debug。
Passed 18 of 22 test cases with the skill, and 17 of 22 without it.
1 fixed17 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
I need to update the rate limiter in api_gateway.go from fixed window to sliding window. Should I draft the sliding window implementation immediately from scratch, or what step must come first?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends inspecting the existing rate limiter implementation before drafting new code. | Passed | Passed |
| Recommends identifying the exact invocation impact boundary prior to code modification. | Missed | Passed |
The instructions your model reads when the skill loads.
在修改现有代码、配置或脚本时,优先使用本技能控制改动范围、决策方式和验证深度。
不要用于:
references/change-boundary.mdreferences/verification.mdreferences/decision-principles.mdtest cases passed, vs 17 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.