CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

conducting-api-security-testing

Conducts security testing of REST, GraphQL, and gRPC APIs to identify vulnerabilities in authentication, authorization, rate limiting, input validation, and business logic. The tester uses the OWASP API Security Top 10 as the testing framework, combining Burp Suite interception with Postman collections and custom scripts to test endpoint security at every privilege level. Activates for requests involving API security testing, REST API pentest, GraphQL security assessment, or API vulnerability testing.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/conducting-api-security-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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, largely actionable manual testing playbook whose core weakness is its relationship to its own bundle: the shipped automation script and its API reference are never referenced from SKILL.md, so a reader would never know they exist. Secondary issues are explanatory padding of known concepts and absent validation checkpoints (scope confirmation, finding reproduction, post-test cleanup) around batch and data-modifying test operations.

Suggestions

Add a section wiring in the bundle, e.g., '## Automated scanning: For bulk checks run `python scripts/agent.py --base-url https://api.target.com --token <jwt> --low-priv-token <jwt> --graphql --output report.json`; see [references/api-reference.md](references/api-reference.md) for all functions and OWASP coverage.'

Insert validation checkpoints into the workflow: confirm written authorization and test accounts before Step 1, reproduce each finding with a second request before reporting, and restore/verify any data modified during mass-assignment or DELETE-method tests.

Trim the Key Concepts table and Tools & Systems entries of definitions Claude already knows (JWT, rate limiting, Burp Suite, Postman), keeping only skill-specific methodology terms like BOLA/BFLA test technique.

DimensionReasoningScore

Conciseness

The workflow steps are dense and directive ('Change `alg` to `none` and remove the signature', 'hashcat -m 16500 jwt.txt wordlist.txt'), but the Key Concepts table and Tools & Systems section explain concepts Claude already knows (JWT as 'a self-contained token format used for API authentication', Rate Limiting, Burp Suite, Postman), adding ~20 lines of padding that could be trimmed.

3 / 5

Actionability

Mostly executable guidance: copy-paste-ready GraphQL introspection query, mass-assignment JSON payload, NoSQL operator injection payload, and a hashcat command, plus concrete endpoint examples ('GET /api/users/123/orders -> GET /api/users/456/orders'). Minor gaps keep it below fully executable — e.g., 'Test all parameters... with SQL injection payloads' and 'Submit XML content with external entity declarations' give no example payloads, and SSRF testing lists no concrete metadata addresses.

4 / 5

Workflow Clarity

The five-step sequence (Discovery, Authentication, Authorization, Input Validation, Data Exposure) is clearly ordered, but there are no validation checkpoints around the batch and destructive-natured operations the workflow itself prescribes — 'Send 100+ rapid requests to authentication endpoints', 'DELETE /api/users/456', and mass-assignment writes that modify data. Per the rubric, missing validation/verification for batch/destructive operations caps this at 3.

3 / 5

Progressive Disclosure

The bundle ships scripts/agent.py (a 228-line automated testing agent) and references/api-reference.md (its CLI and function documentation), yet the SKILL.md body contains zero references to either — no path, no link, no mention. The bundle is effectively buried and undiscoverable from the main file, which is the navigation failure this dimension measures; the body's own section structure is otherwise good.

2 / 5

Total

12

/

20

Passed

Description

88%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 explicitly covers what (five vulnerability classes across three API types with a named framework and tooling) and when (four concrete activation triggers) in third-person voice. The only meaningful improvement is broader trigger synonym coverage.

DimensionReasoningScore

Specificity

Multiple specific concrete capabilities with comprehensive coverage: 'Conducts security testing of REST, GraphQL, and gRPC APIs to identify vulnerabilities in authentication, authorization, rate limiting, input validation, and business logic' — five named vulnerability classes across three API protocols, plus a named methodology ('OWASP API Security Top 10 as the testing framework, combining Burp Suite interception with Postman collections'). Uses third-person voice throughout ('Conducts', 'The tester uses').

5 / 5

Completeness

Clearly and explicitly answers both what and when: the first two sentences state what the skill does with concrete capabilities, and 'Activates for requests involving API security testing, REST API pentest, GraphQL security assessment, or API vulnerability testing' provides an explicit trigger clause with concrete phrases — matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Good keyword coverage with four natural trigger phrases a user would actually say: 'API security testing, REST API pentest, GraphQL security assessment, or API vulnerability testing'. Not 5 because common synonyms and variations are missing — 'API pentest' as a standalone phrase, 'penetration testing', 'API audit', or specific vulnerability names (BOLA, IDOR) users might mention.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers: API-specific protocols (REST, GraphQL, gRPC) and an API-specific framework (OWASP API Security Top 10) distinguish it from general web-application or network penetration testing skills. Not 5 because in a cybersecurity skill set, phrases like 'API security testing' and 'API vulnerability testing' carry minor overlap risk with closely related security-assessment skills.

4 / 5

Total

18

/

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

mukul975/Anthropic-Cybersecurity-Skills

Path

skills/conducting-api-security-testing/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.