CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

safety-guard

Guard against destructive operations with three modes: Careful intercepts dangerous commands (rm -rf, git push --force, DROP TABLE) for confirmation, Freeze locks writes to one directory, and Guard combines both. Advisory: the agent applies these rules itself; no hook ships with it. Use when working on production systems, running agents autonomously, restricting edits to a directory, or during migrations, deploys, and data changes.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A compact, readable skill that clearly explains its three modes and honestly documents its advisory enforcement limits. Its main weakness is workflow rigor for a destructive-operation skill: Freeze mode lacks any verification step and the post-confirmation/denial flow is undefined, which caps workflow clarity. The Integration section also references ECC-specific tooling the skill never defines.

Suggestions

Add an explicit verification step for Freeze mode, e.g., "Before every Write/Edit, verify the target path is inside the frozen directory; if not, stop and tell the user what outside change is needed."

Define the confirmation flow end-to-end with an example prompt (what the agent shows, what counts as confirmation, and what to do on denial — e.g., propose the safer alternative instead).

Trim or explain the Integration section: "codex -a never" and "ECC 2.0 observability risk scoring" reference tooling the skill never defines, so either expand them into actionable guidance or remove them.

DimensionReasoningScore

Conciseness

The body is mostly lean, but there are minor trim opportunities: Guard mode's "The agent can read anything but only writes to src/api/, and asks before any destructive command" restates the two combined modes, "Useful when you want an agent to focus on one area" pads Freeze mode, and the Integration section's ECC-specific items ("Enable by default for `codex -a never` sessions", "Pair with observability risk scoring in ECC 2.0") reference tooling undefined in the skill. This fits the score-4 anchor (efficient, minor instances of over-explanation) rather than 5, where every token would earn its place.

4 / 5

Actionability

Guidance is mostly concrete for an instruction-only skill: a specific watched-pattern list ("rm -rf", "git push --force", "DROP TABLE", "docker system prune", etc.) and concrete behaviors ("The agent does not Write/Edit outside src/components/, and explains why when a change would need it"). Minor gaps remain — no example of the confirmation prompt the agent should show, and "Unlock: Tell the agent to stop applying the rules" leaves the mechanism vague — so it fits score 4 rather than the fully copy-paste-ready score 5, and is more complete than the score-3 pseudocode level.

4 / 5

Workflow Clarity

Careful mode has an explicit checkpoint ("shows what the command does, asks for confirmation, suggests safer alternative"), but this is a destructive-operation skill and validation is incomplete: Freeze mode has no verification step (e.g., checking the target path is inside the frozen directory before each write), and there is no defined flow for what the agent does after the user confirms or denies. Per the guideline capping destructive-operation skills with validation gaps at 3, this is 3 rather than 4.

3 / 5

Progressive Disclosure

The ~55-line body has well-organized sections (When to Use, How It Works with one subsection per mode, Enforcement) and no bundle files, none of which are needed at this size. The two external links (permission deny rules, PreToolUse hooks) are appropriate one-level-deep pointers. Per the simple-skill exception for short skills with no need for external references, well-organized sections alone warrant 5; score 4 would imply misplaced content, of which there is none.

5 / 5

Total

16

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that names all three modes with concrete command examples and provides an explicit "Use when" clause covering production work, autonomous agents, migrations, and deploys. It stays in third person and honestly discloses its advisory nature. Trigger coverage is good though not exhaustive of natural synonyms.

DimensionReasoningScore

Specificity

The description enumerates all three modes with concrete actions and specific command examples: "Careful intercepts dangerous commands (rm -rf, git push --force, DROP TABLE) for confirmation, Freeze locks writes to one directory, and Guard combines both". This matches the score-5 anchor (multiple specific concrete actions, comprehensive coverage) rather than 4, since every mode is named with concrete command-level detail.

5 / 5

Completeness

It explicitly answers both what (three named modes each with its concrete behavior) and when (an explicit "Use when..." clause with concrete triggers including migrations, deploys, and autonomous agents). This matches the score-5 anchor exactly; score 4 would require the when-clause to be less explicit than it is.

5 / 5

Trigger Term Quality

The "Use when" clause lists natural phrases users would say — "working on production systems, running agents autonomously, restricting edits to a directory, or during migrations, deploys, and data changes". Coverage is good but misses common synonyms such as "confirm before deleting", "protect", or "safe mode", so it fits the score-4 anchor (a few natural terms missing) rather than the comprehensive score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

The destructive-operation guard niche with named Careful/Freeze/Guard modes is clearly distinguishable, but triggers like "restricting edits to a directory" and "working on production systems" overlap with permission-management and general safety skills. This is the score-4 anchor (mostly distinct, minor overlap risk with closely related skills) rather than 5 (minimal conflict risk).

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

affaan-m/ECC

Path

skills/safety-guard/SKILL.md

Reviewed

Table of Contents

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.