CtrlK
BlogDocsLog inGet started
Tessl Logo

x-api-pentest

Use when the user provides an OpenAPI or Swagger spec and asks to find security issues, pentest the API, audit endpoints for OWASP API Top 10, or check for BOLA, BFLA, mass assignment, injection, or SSRF vulnerabilities in a running HTTP API

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 content is a well-structured orchestration overview that offloads detail to clearly-signaled reference files and a sequential step architecture with strong validation checkpoints. It is efficient and highly actionable for routing, though executable command specifics live in referenced files.

Suggestions

Tighten the 'How this differs from existing skills' section (four verbose comparisons) into one-line distinctions or move the full comparison entirely to references/related-skills.md.

Consider trimming the nine-item 'Red Flags' list to the highest-signal items and folding the rest into gotchas.md.

Inline one or two concrete CLI invocations (e.g., a representative Schemathesis command) so the body is executable without immediately opening references/tool-invocations.md.

DimensionReasoningScore

Conciseness

The body is information-dense and assumes Claude's pentest knowledge without padding, but sections like 'How this differs' (four detailed comparisons) and the nine-item 'Red Flags' list could be trimmed slightly. Not a 5 because not every token earns its place.

4 / 5

Actionability

Provides concrete bootstrap steps with specific config keys, file paths, an exact MCP call, and named CLI tools, but the executable command detail is delegated to references/tool-invocations.md and step files rather than inline. Not a 5 because copy-paste commands live in referenced files.

4 / 5

Workflow Clarity

A clear six-step sequence with explicit ordering dependencies ('step 4 requires step 2 credentials'), a non-negotiable consent gate, halt-at-checkpoint rules, blind re-verification, and a Red Flags checklist providing strong feedback loops for a destructive/batch operation.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview with one-level-deep references, each listed with a one-line purpose and load-condition ('Loaded ONLY when needed by a step', 'loaded by step-04 only if LLM endpoints detected'); all eight referenced files exist under ./references/.

5 / 5

Total

18

/

20

Passed

Description

100%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 comprehensive and concrete, listing specific actions and vulnerability classes with a clear 'Use when...' trigger and a well-defined niche. It is dense but every clause carries trigger or capability signal rather than fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (find security issues, pentest the API, audit endpoints) plus a comprehensive set of specific vulnerability classes (BOLA, BFLA, mass assignment, injection, SSRF).

5 / 5

Completeness

Explicitly answers both what (black-box API security testing / endpoint auditing) and when, with a clear 'Use when the user provides an OpenAPI or Swagger spec and asks to...' trigger clause.

5 / 5

Trigger Term Quality

Covers natural user phrasing and synonyms ('OpenAPI or Swagger spec', 'pentest', 'audit', 'check for ... vulnerabilities') plus the running HTTP API context, giving comprehensive trigger coverage.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (OpenAPI/Swagger-spec-driven live HTTP API pentesting with named OWASP API Top 10 vuln classes) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
quangtran88/x-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.