Protect key research results with permanent documentation, drift tests, or artifact-appropriate checks. Use when selecting protection, creating or reviewing tests, or guarding important outputs through integration.
Scanned 9/9/2026
Install to Claude Code
Skills Directorynpx -y skills add FuZhiyu/superRA --skill result-protection --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Result Protection?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/fuzhiyu-result-protection)More formats (shields.io, HTML) on the badges page.
---
name: result-protection
description: Protect key research results with permanent documentation, drift tests, or artifact-appropriate checks. Use when selecting protection, creating or reviewing tests, or guarding important outputs through integration.
---
# Result Protection
Protect key results from unintended changes. Permanent results documentation suffices when the researcher chooses it; drift tests and other checks add automated protection where useful.
## References
Load only the reference for the protection mechanism in use:
| Reference | Load when |
|---|---|
| `references/drift-test-quality.md` | Writing, refreshing, or reviewing drift/regression tests for selected results. |
Load any domain-specific drift-test reference per the active domain skill's stage-load table at the `protection` stage.
## Scope Gate
- `[BLOCKING]` Protect researcher-confirmed key results, not every intermediate number.
- `[BLOCKING]` Record a protection mechanism and durable home for every researcher-confirmed kept result.
- `[BLOCKING]` A protection update that changes expected results requires the same escalation as a meaningful result change.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".
