CtrlK
BlogDocsLog inGet started
Tessl Logo

meta-security-review-bundle

Compose three independent security gates over a candidate operation — policy/governance review, secret/credential scan, and audit-log emit — then arbitrate the verdicts with a strict priority rule (governance DENY > scanner WARN > ALLOW). Use when reviewing a proposed code change, script, or environment manipulation for safety.

63

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./src/opensquilla/skills/exp/meta-security-review-bundle/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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.

The content is concise and well-organized as a self-contained meta-skill overview, but the actionable detail sits in the frontmatter prompts while the body stays descriptive, and the workflow lacks an explicit verification checkpoint. Adding a validate-gate-outputs step and tightening the rationale prose would lift actionability and workflow clarity.

Suggestions

Add an explicit verification checkpoint in the workflow that validates each gate produced a well-formed DENY/ALLOW or WARN/CLEAR line before arbitrating.

Move a concrete, copy-ready example of the arbitrate verdict output into the body so the guidance is directly executable rather than descriptive.

Trim the pptx slide-7 rationale paragraphs; keep only the actionable arbitration rule and fallback behavior.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, avoiding concept re-explanation; a few sentences restating the slide-7 rationale could be trimmed.

4 / 5

Actionability

Executable guidance lives mostly in the frontmatter step prompts; the body itself is meta-commentary explaining the pattern rather than giving concrete, copy-ready commands, leaving some execution detail implicit.

3 / 5

Workflow Clarity

The five-step sequence and depends_on ordering are clear with a fallback section, but the arbitration workflow lacks an explicit validation checkpoint verifying gate outputs before proceeding, which caps destructive/batch workflows at 3.

3 / 5

Progressive Disclosure

A short, self-contained overview organized into clear sections (Arbitration rule, Fallback, Use sparingly) with no external bundle files needed; navigation is trivial for a sub-50-line skill.

5 / 5

Total

15

/

20

Passed

Description

87%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 precise, well-structured description that states concrete capabilities and a clear use-when clause with natural trigger terms. It is highly specific and distinct, with only minor room to broaden everyday phrasing.

DimensionReasoningScore

Specificity

Names three concrete gates (policy/governance review, secret/credential scan, audit-log emit) plus an explicit arbitration rule (governance DENY > scanner WARN > ALLOW); minor gap in coverage detail keeps it just below 5.

4 / 5

Completeness

Explicitly answers both what ('Compose three independent security gates… then arbitrate') and when ('Use when reviewing a proposed code change, script, or environment manipulation for safety') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Natural phrases like 'reviewing a proposed code change', 'script', 'review for safety', and 'security review' are present, but some wording leans domain-jargon ('candidate operation', 'environment manipulation') leaving a few common variants implicit.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (combinator security-gate arbitration) with distinct triggers and minimal overlap risk with general coding/review skills.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
TokenRhythm/opensquilla
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.