CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-ref-owasp-checklist

OWASP Top 10 security checklist, authentication patterns, input validation, and HTTP security headers reference. Agent-extending skill that amplifies backend-implementation and security-audit workflows with production-grade security patterns. NOT for: frontend UI, DevOps deployment, performance optimization, testing strategy.

Quality

77%

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 ./.claude/skills/moai-ref-owasp-checklist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 dense, well-organized single-file reference whose value is in genuinely specific recommended values (JWT windows, header strings, severity actions) and a real evidence-producing verification checklist. Its main gaps are the absent explicit review sequence, the unprovided grep patterns it asks the agent to show, and one dangling file reference.

Suggestions

Provide the concrete grep/ripgrep patterns behind 'show grep results for common secret patterns' so the verification step is self-contained rather than requiring the agent to invent patterns.

Add a short 3-4 step 'How to run a security review' sequence (scan Red Flags, apply OWASP table, assign P0-P3 severity, run Verification checklist) to make the currently implicit workflow explicit.

Remove or resolve the reference to 'archived-agent-rejection.md §C', which is not part of the skill bundle and reads as a dangling pointer to readers without that parent context.

DimensionReasoningScore

Conciseness

The body is dense reference tables with almost no prose padding, and most rows carry specific values Claude cannot be trusted to recall from memory ('bcrypt (cost factor 12+) or Argon2id', 'Access Token Expiry | 15-30 minutes', 'max-age=31536000; includeSubDomains'). Held below 5 because several rows restate well-known basics ('SQL Injection | Parameterized queries', 'XSS Prevention | HTML escaping') and the 'Common Rationalizations' section is persuasive padding that assumes the agent needs convincing rather than reference data.

4 / 5

Actionability

Concrete throughout: exact settings ('RS256 (asymmetric)', 'httpOnly + secure + sameSite cookie'), named tools per task ('Zod, Joi, pydantic, Go validator', 'DOMPurify (client)', 'Prisma, GORM, SQLAlchemy'), and severity-gated actions ('P0 | CRITICAL | Block release'). Not 5 because the verification checklist demands 'show grep results for common secret patterns' without providing the patterns themselves, and tool mentions lack even minimal usage snippets — minor but real gaps in an otherwise executable reference.

4 / 5

Workflow Clarity

The 'Verification' section supplies explicit checkpoints with evidence requirements ('show which items were evaluated', 'show grep results for common secret patterns') and 'Security Review Severity Levels' maps each finding to a concrete action. However, no explicit ordering of a review exists — how the Red Flags, OWASP table, severity levels, and Verification sections chain together is left implicit, so it fits the 'clear structure, most checkpoints present, minor gaps' anchor rather than the full sequence-plus-feedback-loop anchor.

4 / 5

Progressive Disclosure

A single-file skill with no references/, scripts/, or assets/ directories; sections are clearly headed and the ~130-line body of compact tables is appropriately kept in one file rather than split. Not 5: it exceeds the compact under-50-line case where sections alone suffice, and the body cites 'archived-agent-rejection.md §C' — a document not present in the bundle — a dangling pointer that slightly undermines navigation.

4 / 5

Total

16

/

20

Passed

Description

70%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 specific, well-bounded description of a security-reference niche with good natural keywords and unusually explicit exclusions. Its weaknesses are a buzzword middle sentence and the absence of an affirmative 'Use when...' trigger clause in the description itself — the trigger guidance sits in a sibling when_to_use field, which caps completeness.

Suggestions

Fold an affirmative trigger clause into the description itself, e.g. 'Use when implementing or reviewing backend APIs, or when the user mentions OWASP, injection, XSS, CSRF, or security headers' — currently the when-guidance lives only in the when_to_use field and appears in the description merely as 'amplifies ... workflows'.

Replace the buzzword sentence 'Agent-extending skill that amplifies backend-implementation and security-audit workflows with production-grade security patterns' with concrete trigger terms users actually say (injection, XSS, CSRF, security review, hardening).

Keep the 'NOT for:' exclusion list as-is — it is the description's strongest distinctiveness signal and should anchor any rewrite.

DimensionReasoningScore

Specificity

The first sentence lists four concrete capability areas — 'OWASP Top 10 security checklist, authentication patterns, input validation, and HTTP security headers reference' — matching the 'several specific actions, minor gaps' anchor. Kept below 5 because the second sentence ('Agent-extending skill that amplifies backend-implementation and security-audit workflows with production-grade security patterns') is buzzword-laden rather than a concrete capability.

4 / 5

Completeness

The 'what' is explicit and clear (a reference for the four named security areas), but the description contains no 'Use when...' clause or direct equivalent — the closest is the indirect 'amplifies backend-implementation and security-audit workflows' plus the negative 'NOT for:' list. Per the judging guideline that a missing explicit trigger clause caps completeness at 3, this fits the 'clear what, when only weakly implied' anchor; the actual affirmative trigger guidance lives in a separate when_to_use frontmatter field rather than the description.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'OWASP Top 10', 'security checklist', 'authentication patterns', 'input validation', 'HTTP security headers', 'security-audit', 'backend-implementation' — terms a user working on API security would plausibly say. Falls short of the 5 anchor because common variations like 'injection', 'XSS', 'CSRF', 'vulnerabilities', or 'security review' appear only in the sibling when_to_use field, not in the description itself.

4 / 5

Distinctiveness Conflict Risk

Clear niche — a security-checklist/auth/headers reference — with distinct triggers, and the explicit exclusion list 'NOT for: frontend UI, DevOps deployment, performance optimization, testing strategy' sharply delimits the boundaries. This matches the 'clear niche with distinct triggers; minimal conflict risk' anchor; the exclusions proactively prevent the most likely wrong-skill triggers.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

modu-ai/moai-adk

Path

.claude/skills/moai-ref-owasp-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.