CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

security

Find and validate concrete PsychSift security risks across secrets, input handling, authentication, authorization, storage, dependencies, and trust boundaries. Use for security review, threat analysis, or confirmed finding remediation.

Quality

89%

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

86%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 tightly written, well-sequenced security review process that assumes Claude's competence and adds only project-specific guidance. The main gap is the absence of any concrete tooling, search commands, or a worked example for the search-and-prove steps, and no explicit recovery path for unproven findings.

DimensionReasoningScore

Conciseness

The body is six lean numbered lines with zero padding and no explanation of concepts Claude already knows; every phrase ("Rank by impact and likelihood; avoid speculative style findings") adds non-obvious guidance. This matches the lean-and-efficient anchor where every token earns its place, not the level below, which would require trimming minor over-explanation.

5 / 5

Actionability

The guidance is concrete for an instruction-only skill: it enumerates specific vulnerability classes to search ("auth, injection, SSRF, file handling, secrets, storage, RLS, and dependencies"), specific evidence standards ("changed code, a safe local test, or deterministic static evidence"), and a defined reporting taxonomy. It stays at mostly-executable rather than fully actionable because no commands, search patterns, or worked examples are given for steps like "Search for realistic exploit paths".

4 / 5

Workflow Clarity

A clear six-step sequence is present with an explicit validation checkpoint ("Prove each finding with changed code, a safe local test, or deterministic static evidence") and safety gates (fixes only when requested, live validation approval-gated). It falls short of the top anchor because there is no feedback loop for error recovery, e.g., what to do when a suspected finding cannot be proven, though step 4's "avoid speculative style findings" implicitly handles it.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no external references to organize, and no bundle files exist; the single well-ordered process list under one heading is the appropriate structure. Per the rubric's simple-skill guidance, this earns the top score without external file references.

5 / 5

Total

18

/

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 states concrete capabilities across an explicit set of security domains and includes an explicit trigger clause. Its only weaknesses are a trigger phrase ("security review") that is broader than the PsychSift-specific scope, and missing common synonyms such as "vulnerability" or "security audit".

DimensionReasoningScore

Specificity

"Find and validate concrete PsychSift security risks across secrets, input handling, authentication, authorization, storage, dependencies, and trust boundaries" names multiple concrete actions (find, validate) with comprehensive coverage across seven enumerated risk domains. This matches the anchor for multiple specific concrete actions with comprehensive coverage, not the level below, which allows minor gaps in coverage.

5 / 5

Completeness

The description explicitly answers both questions: the "what" is "Find and validate concrete... security risks across..." and the "when" is the explicit trigger clause "Use for security review, threat analysis, or confirmed finding remediation". This clearly matches the anchor requiring both what and when with concrete trigger phrases; the level below (4) would require a less explicit or specific "when", which does not apply here.

5 / 5

Trigger Term Quality

"security review, threat analysis, or confirmed finding remediation" are natural phrases users would say, giving good keyword coverage. Common synonyms like "vulnerability", "security audit", or "penetration testing" are missing, which keeps it at good-but-not-comprehensive coverage rather than the top anchor's full synonym and extension coverage.

4 / 5

Distinctiveness Conflict Risk

The "PsychSift" scoping carves out a clear niche, but the trigger clause "Use for security review" is generic and could overlap with closely related general security-review skills when the user is not working on PsychSift. This is minor overlap risk with closely related skills (anchor 4) rather than the minimal conflict risk of anchor 5, whose triggers themselves carry the distinguishing scope.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

BigSimmo/PsychSift

Path

.agents/skills/security/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.