stride-analysis-patterns

Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.

Quality

59%

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/stride-analysis-patterns/SKILL.md

Quality

Content

40%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 token-efficient and well-sectioned but extremely generic: no concrete threat-modeling steps, no validation checkpoints, and a broken reference to a missing resource file.

Suggestions

Add concrete, executable threat-modeling steps (e.g., enumerate data flows, map each STRIDE category to components, produce a ranked threat table) instead of the generic 'apply best practices' bullets.

Create the referenced `resources/implementation-playbook.md` or remove the broken reference so progressive disclosure actually resolves.

Include an explicit validation checkpoint (e.g., confirm every STRIDE category was applied per trust boundary) to lift workflow clarity above the current generic guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean and does not explain what STRIDE is, assuming Claude's competence; the only bloat is the generic Instructions boilerplate ("Apply relevant best practices and validate outcomes"), which keeps it just below a 5.	4 / 5
Actionability	Instructions are high-level abstractions ("Clarify goals... Apply relevant best practices... Provide actionable steps") with no concrete steps, code, or commands, and the only actionable detail is offloaded to a referenced file.	2 / 5
Workflow Clarity	The three Instruction bullets are parallel generic guidance rather than a sequenced process, with no concrete validation checkpoints for the threat-modeling workflow.	2 / 5
Progressive Disclosure	Sections exist and one reference is signaled, but the referenced `resources/implementation-playbook.md` does not exist in the bundle, so the disclosed path is broken and navigation fails.	2 / 5
	Total	10 / 20 Passed

Description

78%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 cleanly answers both what and when with a clear niche and natural trigger terms, though the capability list is thin (a single action) rather than comprehensive.

Dimension	Reasoning	Score
Specificity	"Apply STRIDE methodology to systematically identify threats" names the domain and one concrete action (identify threats), but offers no broader coverage of what the skill does, matching the 1-2 concrete actions anchor rather than the several-actions anchor at 4.	3 / 5
Completeness	It explicitly states the what ("Apply STRIDE methodology to systematically identify threats") and the when ("Use when analyzing system security, conducting threat modeling sessions, or creating security documentation") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms like "threat modeling sessions", "system security", and "security documentation" plus the "STRIDE" keyword give good coverage a user would plausibly say, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	STRIDE is a clearly distinctive niche with its own trigger term, though the broad phrase "analyzing system security" leaves minor overlap risk with adjacent security skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/stride-analysis-patterns/SKILL.md
Commit: 3eff4af

Reviewed: 2 days 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.