dangerous-actions
Rosetta CRITICAL MUST skill. MUST activate when action or its consequence is potentially dangerous, potentially irreversible, potentially destructive, or HIGH RISK. MUST activate when consequence MAYBE dangerous even if action itself seems safe. This is enterprise environment — the cost of dangerous activities is EXTREMELY HIGH, recovery may be impossible, and blast radius may affect production, shared environments, or other teams. If there is even a remote chance - load the skill.
60
70%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No known issues
Fix and improve this skill with Tessl
tessl review fix ./instructions/r2/core/skills/dangerous-actions/SKILL.md<dangerous_actions>
- Assess BLAST RADIUS before execution.
- "THINK THE OPPOSITE" — what if this goes wrong?
- Consider safer alternatives.
- MUST REQUIRE EXPLICIT user approval for hard-deny tier (see below).
Examples (not limited):
- Deleting data from actual servers
- Using actual servers in unit testing
- git reset, deleting branches, force-push
- Generating destructive scripts or commands
- Modifying shared infrastructure, CI/CD, permissions
- Dropping or truncating database tables
Exceptions (only after blast radius):
- Application code itself.
- Just-created data you CAN fully recover.
- Temporary data without side-effects.
- Assuming local action has no remote consequence.
- Generating destructive commands in scripts without flagging.
</dangerous_actions>
- Repository
- griddynamics/rosetta
- Commit
2883247
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.