007

Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/007/SKILL.md

Quality

Content

43%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 SKILL.md body is a thin, well-intentioned overview that delegates essentially all substance to the detailed guide, but it provides no executable workflow in the body itself and the delegated references contain broken file and script links.

Suggestions

Add a minimal executable quick-start (e.g. the quick_scan.py / full_audit.py invocation with a relative path and a validation/verify step) directly in SKILL.md so the body is actionable without loading the guide.

Fix broken references: remove or create the five missing reference files (hardening-linux.md, hardening-windows.md, payment-security.md, bot-security.md, compliance-matrix.md) and the missing scripts (threat_modeler.py, security_checklist.py, surface_mapper.py, hardening_advisor.py) referenced in detailed-guide.md.

Replace Windows absolute paths (C:\Users\renat\skills\007\scripts\...) with portable relative paths (e.g. python scripts/quick_scan.py --target <path>) and add an explicit validate-then-proceed checkpoint for destructive or batch operations.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's intelligence, and avoids explaining concepts Claude already knows, though phrases like 'Treat its safety, prerequisites, and validation requirements as mandatory' are slightly redundant given 'Read ... before executing'.	4 / 5
Actionability	The body offers only high-level direction ('Read the detailed guide before executing this skill') with no concrete commands or steps in SKILL.md itself, leaving the executable guidance delegated and unspecified.	2 / 5
Workflow Clarity	No multi-step sequence or validation checkpoints appear in the body; the Limitations section's 'Stop and ask for clarification' is a weak checkpoint, but for a destructive/batch-capable audit skill the missing validation caps this low.	2 / 5
Progressive Disclosure	There is a clearly signaled one-level-deep reference to references/detailed-guide.md, but that guide points to five reference files (hardening-linux, hardening-windows, payment-security, bot-security, compliance-matrix) and several scripts (threat_modeler.py, security_checklist.py, surface_mapper.py, hardening_advisor.py) that do not exist, and uses non-portable Windows absolute paths, breaking navigation.	3 / 5
	Total	11 / 20 Passed

Description

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

The description conveys a broad, concrete set of security capabilities and a clear niche, but omits any explicit 'when to use' trigger clause, which caps completeness and leaves activation guidance implicit.

Suggestions

Append an explicit 'Use when ...' clause listing natural trigger phrases (e.g. 'Use when the user asks for a security audit, threat model, STRIDE/PASTA analysis, OWASP review, hardening, or incident response').

Add common synonyms and variations users actually say (e.g. 'pentest', 'vulnerability scan', 'secure this app', 'red team / blue team') to broaden trigger coverage.

Tighten 'for any project' so the scope reads as a deliberate positioning rather than an over-claim.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete, distinct actions — 'Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security' — giving comprehensive coverage of the domain.	5 / 5
Completeness	The 'what' is clearly stated but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms users would say are present ('security audit', 'threat model', 'STRIDE'), but common synonyms and variations are missing and there are no file-extension-style triggers, so it is not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	The security niche with distinct triggers (STRIDE/PASTA, OWASP, Red/Blue Team, incident response) is mostly distinct, with only minor overlap risk against general code-review skills.	4 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/007/SKILL.md
Commit: b1aebac

Reviewed: ~12 hours ago

Table of Contents

Discovery Implementation Validation

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.