CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

44

Quality

45%

Does it follow best practices?

Impact

—

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./instructions/r2/core/skills/dangerous-actions/SKILL.md
SKILL.md
Quality
Evals
Security

<dangerous_actions>

<process>
  1. Assess BLAST RADIUS before execution.
  2. "THINK THE OPPOSITE" — what if this goes wrong?
  3. Consider safer alternatives.
  4. MUST REQUIRE EXPLICIT user approval.

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):

  1. Application code itself.
  2. Just-created data you CAN fully recover.
  3. Temporary data without side-effects.
</process> <pitfalls>
  • Assuming local action has no remote consequence.
  • Generating destructive commands in scripts without flagging.
</pitfalls>

</dangerous_actions>

Repository
griddynamics/rosetta
Commit

0f3002b

Last updated
Created

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.

Claim skill