CtrlK
BlogDocsLog inGet started
Tessl Logo

senior-security

Use when the user asks for STRIDE threat modeling, DREAD risk scoring, data-flow-diagram threat analysis, or a quick secret scan — or when a security request needs routing to the right specialist skill (pen-testing, incident response, cloud posture, red team, AI security, threat hunting, secure code review). This skill owns threat modeling; everything else routes to a sibling.

76

Quality

96%

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

The canonical home for this skill is senior-security in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 body is tight, highly actionable, and has an excellent validation-gated workflow, but its progressive-disclosure promise is undercut by missing bundle files (three references and two scripts are referenced but absent from the skill directory).

Suggestions

Ship the referenced bundle files: add references/threat-modeling-guide.md, references/security-architecture-patterns.md, references/cryptography-implementation.md so the References table links resolve.

Provide scripts/threat_modeler.py and scripts/secret_scanner.py (or note them as external/TODO), since the workflow steps invoke them by path and would fail as written.

If the scripts/references are intentionally out-of-scope, replace the bare path references with a short note describing what each provides so the skill is self-sufficient when the files are absent.

DimensionReasoningScore

Conciseness

Lean, dense body that assumes Claude knows STRIDE/DREAD/DFD; uses tight tables and copy-ready bash snippets with no concept re-explanation, matching the lean-and-efficient anchor.

5 / 5

Actionability

Provides fully executable commands with real flags and outputs ("python3 scripts/threat_modeler.py --component ... --json --output threats.json", "python3 scripts/secret_scanner.py /path/to/project --format json --severity high") plus concrete consumption rules, matching the copy-paste-ready anchor.

5 / 5

Workflow Clarity

A 5-step sequence (Scope → Generate → Consume → Sweep → Verification gate) with an explicit validation gate and re-run feedback loop ("Re-run both tools after mitigations land — that re-run is the done signal"), matching the explicit-validation-with-feedback-loops anchor.

5 / 5

Progressive Disclosure

Structure is well-signaled and one-level-deep (a "References (load on demand)" table), but none of the referenced bundle files exist (references/, scripts/ are missing), so navigation to threat-modeling-guide.md, the crypto/architecture references, and the two scripts is non-functional.

3 / 5

Total

18

/

20

Passed

Description

100%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 is exemplary: concrete named methodologies, explicit "Use when..." trigger guidance, broad natural keyword coverage, and a sharp ownership boundary that distinguishes it from sibling skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions across the security surface ("STRIDE threat modeling", "DREAD risk scoring", "data-flow-diagram threat analysis", "quick secret scan", "routing to the right specialist skill"), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both what ("This skill owns threat modeling; everything else routes to a sibling") and when ("Use when the user asks for STRIDE threat modeling, DREAD risk scoring... or a quick secret scan"), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural terms users say ("threat modeling", "risk scoring", "secret scan", "pen-testing", "incident response", "cloud posture", "red team", "AI security", "threat hunting", "secure code review") with synonyms, matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

Carves a clear niche ("This skill owns threat modeling; everything else routes to a sibling") with distinct triggers vs. the routed lanes, minimizing conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 missing

Warning

referenced_paths_exist

Referenced path issues: 8 missing

Warning

Total

14

/

16

Passed

Repository
alirezarezvani/claude-skills
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.