CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

security-best-practices

Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.

1.18x
Quality

76%

Does it follow best practices?

Impact

97%

1.18x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/cloud-profile/skills/security-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 a well-structured instruction-only skill: clear multi-mode workflow, concrete report/fix procedures, and sound progressive disclosure into a real references bundle. Weaknesses are moderate verbosity and redundancy (overlapping workflow sections, repeated report-delivery instructions, a stray 'codex' reference and a 'describe anyways' typo), plus the absence of a concrete severity taxonomy or report example.

Suggestions

Merge the 'Workflow' section and 'Workflow Decision Tree' into one pass, and deduplicate the report-delivery instructions ('After you write the report file, summarize... Also tell the user where...').

Add a concrete severity taxonomy (e.g. Critical/High/Medium/Low with one-line definitions) and a short example report skeleton so findings and sections are formatted consistently.

Enumerate or link the available reference files (or at least the supported language list with its per-language general files), fix the 'describe anyways' typo, and remove the stale 'codex' reference in the TLS section.

DimensionReasoningScore

Conciseness

The body is mostly efficient and does not explain concepts Claude already knows, but it has noticeable padding: the 'Workflow' section and 'Workflow Decision Tree' partially repeat each other, report instructions restate delivery steps twice ('After you write the report file, summarize the findings to the user. Also tell the user where the final report was written to'), and phrases like 'This skill provides a description of how to identify...' and 'From there it can operate in a few ways' could be trimmed. This matches anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') better than anchor 4's 'minor instances'.

3 / 5

Actionability

As an instruction-only skill it gives concrete, executable guidance: the reference filename format '<language>-<framework>-<stack>-security.md' (which matches the actual bundle files), a specific report filename 'security_best_practices_report.md', explicit report structure requirements (executive summary, severity sections, numeric finding IDs, line numbers), and per-finding fix instructions. This fits anchor 4 ('mostly executable guidance; concrete... with minor gaps'); it is not a 5 because no example report skeleton or concrete severity taxonomy (e.g. Critical/High/Medium/Low) is provided.

4 / 5

Workflow Clarity

The sequence is clear (identify languages/frameworks -> load matching references -> operate in one of three modes -> report -> fixes) with a decision tree for ambiguous cases, and user-confirmation checkpoints are present (let the user read the report before fixes, notify before fixing passive findings, follow the user's testing/commit flows). Minor validation gaps keep it at anchor 4 rather than 5: testing flows are conditional ('if any') and there are no explicit verify/re-check loops after applying fixes.

4 / 5

Progressive Disclosure

The SKILL.md body is an overview that appropriately pushes the bulk of detail into ten real, one-level-deep reference files, with clear instructions to check the references directory and a naming convention that matches the actual bundle filenames. It falls short of anchor 5 because the references are never enumerated or linked (discovery relies solely on the format string), heading levels are inconsistent (h1 for '# Overrides'/'# Report Format'/'# Fixes' vs h2 elsewhere), and the two inline 'General Security Advice' items are not clearly signaled as cross-cutting rather than language-specific.

4 / 5

Total

15

/

20

Passed

Description

73%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 well-constructed description with explicit trigger conditions, third-person voice, language scoping, and negative triggers that sharply reduce conflict risk with general code-review skills. Its main weakness is that the 'what' undersells the skill's actual modes (secure code generation, passive detection, report generation), and a few natural synonyms like 'vulnerability' are missing.

Suggestions

Enumerate the concrete capabilities in the 'what' clause, e.g. '...write secure-by-default code, passively flag vulnerabilities while coding, and produce prioritized security reports with suggested fixes.'

Add common natural trigger synonyms such as 'vulnerability review', 'security audit', or 'hardening' alongside 'security best practices guidance' and 'security review/report'.

Consider naming the report deliverable explicitly (e.g. 'produces a severity-ranked findings report') so users searching for report generation find this skill.

DimensionReasoningScore

Specificity

The description names the domain ('language and framework specific security best-practice reviews') and two actions ('reviews and suggest improvements'), matching the anchor for 1-2 concrete actions. It does not list the several specific capabilities the skill actually has (secure-by-default code generation, passive detection, report production), so it falls short of anchor 4's 'several specific actions; minor gaps'.

3 / 5

Completeness

Both 'what' ('Perform... security best-practice reviews and suggest improvements') and 'when' ('Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help') are explicit. It sits between anchor 4 and 5: the 'when' is concrete, but the 'what' is a single composite action and less comprehensive than anchor 5's multi-action example, so 4 fits better than 5 and is clearly above anchor 3 (where 'when' would be missing or weak).

4 / 5

Trigger Term Quality

Phrases like 'security best practices guidance', 'a security review/report', 'secure-by-default coding help', and 'python, javascript/typescript, go' are natural terms users would say. Common synonyms such as 'vulnerability', 'audit', or 'pentest' are absent, matching anchor 4 ('good keyword coverage; a few natural terms missing') rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (best-practice security review for three named language stacks) and actively disambiguates with negative triggers: 'Do not trigger for general code review, debugging, or non-security tasks'. This matches anchor 5 ('clear niche with distinct triggers; minimal conflict risk'); anchor 4's 'minor overlap risk' would apply if it lacked the explicit exclusions.

5 / 5

Total

16

/

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

.claude/cloud-profile/skills/security-best-practices/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.