Skip to content

alexandervashurin/semaphore / .claude/skills/careful

careful

Flagged

Safety guardrails for destructive commands. Warns before rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, and similar destructive operations. User can override each warning. Use when touching prod, debugging live systems, or working in a shared environment. Use when asked to "be careful", "safety mode", "prod mode", or "careful mode".

Security report

Flagged

Static analysis of one exact version. It reduces risk and shows evidence; it does not certify that a skill is safe.

Commit
e21a404bfba3ed14a34a2eae8bef983fa65a4b8e
Content hash
a61443b98a398bcc454ac616ed153cb695871ec46788e42a695bab869168b153
Scanned
2026-11-17
Scanner version
skillxone-scan-1.0.0
Policy version
0.1-draft
Decision
1 open critical or high finding.
Verification expires
Not applicable

Findings (1 high, 1 info)

  • highCMD-RM-RF-BROADbin/check-careful.sh:54

    A recursive, forced delete targets the root directory, a system directory or the home directory. Severity lowered from critical because it appears in a code comment.

    # rm -rf / rm -r / rm --recursive

    Suggested fix: Delete only specific paths inside a working or temporary directory.

    Report as false positive

  • infoINT-BROAD-ALLOWED-TOOLSSKILL.md:10

    SKILL.md pre-approves unrestricted shell access through `allowed-tools`, so the agent may run commands without asking.

    allowed-tools: - Bash - Read

    Suggested fix: Restrict the tool, for example `Bash(git status:*)`, or leave approval to the user.

    Report as false positive

Checks run

  • prompt-injection
  • dangerous-commands
  • credentials
  • network
  • file-access
  • integrity

Checks skipped

  • dependencies: No dependency manifest in the skill directory.
  • gitleaks: gitleaks is not installed on this host.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall