CtrlK
BlogDocsLog inGet started
Tessl Logo

common-owasp

OWASP Top 10 audit checklists for Web Applications (2021), APIs (2023), and Mobile (2024). Use when performing any security review, PR review, or codebase audit touching web, mobile, or API code.

64

Quality

78%

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 ./.github/skills/common/common-owasp/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 well-structured, actionable OWASP checklist with concrete detection signals and properly signaled references to real bundle files. Weakest on workflow clarity, where the batch-audit process lacks explicit validation/feedback loops, and the closing anchor sections add minor noise.

Suggestions

Add an explicit validation/feedback loop for the batch audit, e.g. after marking items, re-confirm each 🔴/⚠️ against the referenced detection-signal file before reporting, and define what 'fixed' looks like.

Clarify or remove the terse 'Canonical response anchors' and 'Remediation anchors' sections, which duplicate terms already covered by the tables without added guidance.

Provide one or two runnable commands (e.g. a grep/ripgrep snippet for common signals like 'findById(' or 'Access-Control-Allow-Origin: *') to move detection from described to executable.

DimensionReasoningScore

Conciseness

The body is dense and free of concept padding, but the closing 'Canonical response anchors' and 'Remediation anchors' one-liners are cryptic and partly redundant with the tables and could be tightened.

4 / 5

Actionability

Provides highly concrete detection signals (e.g. 'findById(params.id) without owner filter', 'JWT without expiry', 'CORS *') that are directly grep-able, though there are no runnable commands or scripts.

4 / 5

Workflow Clarity

A rough sequence exists (always-apply rules, then activate checklist, mark items, apply score cap) with a triage marking scheme, but explicit validation feedback loops for this batch audit operation are missing, capping the score.

3 / 5

Progressive Disclosure

Well-organized sections with clearly signaled one-level-deep references to real files (references/owasp-web.md, owasp-api.md, owasp-mobile.md) for full signals, though the inline tables are fairly dense and the final anchor sections are loosely organized.

4 / 5

Total

15

/

20

Passed

Description

87%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 clearly states what the skill provides and when to use it, with concrete trigger terms and a distinct, low-conflict niche. Minor specificity gains are possible by enumerating more of the underlying checklist actions.

DimensionReasoningScore

Specificity

Names three concrete frameworks (Web 2021, APIs 2023, Mobile 2024) and several specific actions (security review, PR review, codebase audit), with only minor gaps in coverage of the underlying checklist actions.

4 / 5

Completeness

Explicitly answers both what ('OWASP Top 10 audit checklists for Web Applications, APIs, and Mobile') and when ('Use when performing any security review, PR review, or codebase audit...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('security review', 'PR review', 'codebase audit', 'web, mobile, or API code', 'OWASP') with good coverage, though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (OWASP Top 10 audit checklists across three named framework editions) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
HoangNguyen0403/agent-skills-standard
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.