CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aif-security-checklist

Security audit checklist based on OWASP Top 10 and best practices. Covers authentication, injection, XSS, CSRF, secrets management, and more. Use when reviewing security, before deploy, asking "is this secure", "security check", "vulnerability".

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/aif-security-checklist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 exceptionally actionable — copy-paste commands, contrastive vulnerable/safe examples, and a severity table — and its references are real and well signaled. Its weaknesses are verbosity (duplicated skill-context policy, a generic interaction contract, and heavy config/language rules) and the absence of a single explicit end-to-end audit sequence with validation checkpoints.

Suggestions

Deduplicate the skill-context guidance: the 'Shared project skill-context' section and the 'Project Context' section state overlapping precedence rules — merge them into one, and trim the generic 'Runtime-aware questions' contract to the essentials.

Present the full audit as one explicit numbered procedure (read config → read resolved SECURITY.md → run scripts/audit.sh → audit scope categories → render ignored-items section → append aif-gate-result JSON) with validation checkpoints, instead of leaving the reader to assemble it from topic sections.

Offload the injection/XSS/CSRF/API/infra checklist details to references files the way AUTH-PATTERNS.md and RACE-CONDITIONS.md already do, keeping only the checklist summaries inline to shrink the SKILL.md footprint.

DimensionReasoningScore

Conciseness

The ~630-line body includes several padded sections unrelated to security checking: the generic "Runtime-aware questions" interaction contract, skill-context precedence rules stated twice ("Shared project skill-context" and again under "Project Context"), and lengthy language/translation policy. Not 1 because the actual checklists and code examples are dense and useful rather than explaining concepts Claude already knows.

2 / 5

Actionability

Highly concrete throughout: runnable grep audit commands, vulnerable-vs-safe TypeScript/PHP snippets, git-history cleanup commands, a shipped scripts/audit.sh, an exact CSP header value, and a severity/fix-timeline table. The `{{shell_home_skills_dir}}` placeholder is environment-substituted, so commands are effectively copy-paste ready and cover the common cases.

5 / 5

Workflow Clarity

The ignore flow has numbered steps ending in "Confirm the item was added" and an enforcement/verify step exists, but the main audit procedure (read config → read SECURITY.md → run audit → render ignored-items section → append gate JSON) is never presented as one ordered sequence — it is distributed across sections with mostly implicit checkpoints. Not 4 because a reader must assemble the sequence themselves; not 2 because the individual sub-flows are clearly enumerated.

3 / 5

Progressive Disclosure

Three real, clearly signaled one-level-deep references ("→ read `references/AUTH-PATTERNS.md`", RACE-CONDITIONS.md, PROMPT-INJECTION.md) plus scripts/audit.sh, all verified to exist in the bundle. Not 5 because ~600 lines remain inlined in SKILL.md while only three categories were offloaded — the injection/XSS/API/infra checklists and code blocks could follow the same pattern.

4 / 5

Total

14

/

20

Passed

Description

83%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 a strong example: third-person voice, a concrete what anchored to OWASP Top 10 and named coverage areas, and an explicit 'Use when' clause with quoted trigger phrases. Minor gaps — the "and more" hedge, unlisted covered categories, and a few missing synonyms — keep specificity and trigger coverage just below the top anchors.

DimensionReasoningScore

Specificity

Quotes: "Security audit checklist based on OWASP Top 10 and best practices" and "Covers authentication, injection, XSS, CSRF, secrets management, and more" — it names the domain plus several concrete coverage areas. Not 5 because "and more" is a hedge and covered categories (infra, prompt-injection, race-condition) are unlisted; not 3 because it goes well beyond naming 1-2 actions.

4 / 5

Completeness

Clearly answers what ("Security audit checklist based on OWASP Top 10... Covers authentication, injection, XSS, CSRF, secrets management") and when, with an explicit "Use when" clause containing concrete quoted trigger phrases. Both halves are explicit, matching the top anchor; 4 would require the 'when' to be less specific than it is.

5 / 5

Trigger Term Quality

"Use when reviewing security, before deploy, asking \"is this secure\", \"security check\", \"vulnerability\"" are natural phrases a user would say. Not 5 because common synonyms like "audit", "pentest", "hardening", or "OWASP" as trigger words are missing.

4 / 5

Distinctiveness Conflict Risk

"Security audit checklist" carves a clear niche with security-specific triggers, so it is mostly distinct. Not 5 because it could still overlap with closely related skills (general code review, dependency-audit, or pentest skills) in a security-focused bundle.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (634 lines); consider splitting into references/ and linking

Warning

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

lee-to/ai-factory

Path

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