CtrlK
BlogDocsLog inGet started
Tessl Logo

api-audit

Audit REST, GraphQL, and RPC APIs against the OWASP API Security Top 10 (2023). Use when the user mentions 'API security,' 'API audit,' 'BOLA,' 'broken object level authorization,' 'BFLA,' 'function-level authorization,' 'mass assignment,' 'API rate limiting,' 'GraphQL security,' 'REST security,' 'API authentication,' 'API authorization,' 'excessive data exposure,' or needs to review API endpoints for security weaknesses.

71

Quality

88%

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

90%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.

An information-dense, highly actionable audit skill that assumes Claude's competence and backs every category with concrete grep patterns and runtime verification guidance. Structure and workflow are strong, with only minor room to tighten the verification loop and consider splitting per-category detail.

DimensionReasoningScore

Conciseness

The body is dense and lean: every line is a concrete audit signal (grep patterns, vulnerable code patterns, bypass techniques) with no padding or explanation of concepts Claude already knows (JWT, CORS, GraphQL).

5 / 5

Actionability

It provides copy-paste-ready grep strings ("params.id", "jwt.verify", "res.json(<entity>)"), concrete code patterns, and specific runtime verification steps (authenticate as user A, request B's resource, observe 404), covering common cases.

5 / 5

Workflow Clarity

There is a clear scope → per-category audit → verify-at-runtime → report sequence with explicit verification checkpoints and per-category checklists, but the runtime-verify steps are illustrative rather than a fully systematic per-finding loop.

4 / 5

Progressive Disclosure

The skill is a single, well-sectioned self-contained file with clear headers and no nested references, and no bundle files exist to navigate; however the long inline per-category detail could arguably be split into reference files, a minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

86%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 with excellent trigger-term coverage and explicit what/when guidance. Its only weakness is that it names a single action (audit) rather than enumerating several concrete actions, and it shares a niche with the sibling owasp-audit skill.

DimensionReasoningScore

Specificity

The description states one concrete action — "Audit REST, GraphQL, and RPC APIs against the OWASP API Security Top 10 (2023)" — applied across a comprehensive domain, but does not enumerate multiple distinct actions as the score-4 anchor requires.

3 / 5

Completeness

It explicitly answers "what" (audit APIs against the OWASP API Top 10) and "when" via a "Use when the user mentions ..." clause with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

It lists a comprehensive set of natural trigger terms users would actually say, including synonyms ("BOLA" / "broken object level authorization", "BFLA" / "function-level authorization") and both generic and specific phrasings.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear API-surface niche with specific triggers, but overlaps with the closely related `owasp-audit` sibling skill (cross-referenced in the body), giving minor conflict risk rather than minimal.

4 / 5

Total

17

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

Total

15

/

16

Passed

Repository
briiirussell/cybersecurity-skills
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.