CtrlK
BlogDocsLog inGet started
Tessl Logo

cors

CORS misconfiguration exploitation — reflected origin, null origin, trusted-subdomain abuse, regex-validation bypass, and credentialed cross-origin data theft.

68

Quality

83%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, highly actionable playbook with executable probes, a concrete exploit PoC, and an explicit validation Decision Gate. It respects Claude's competence with no concept padding and is well organized as a single self-contained file.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — compact curl probes, a terse misconfig matrix, and a minimal HTML PoC; the brief opening framing on ACAO+ACAC severity earns its place as tactical context rather than concept padding. Not level 2 because nothing reads as filler.

3 / 3

Actionability

Provides fully executable curl/bash probe commands, a copy-paste HTML exfil PoC, and named tools with concrete invocations (e.g. 'python corsy.py -u https://<TARGET>'). Not level 2 — no pseudocode or missing key details.

3 / 3

Workflow Clarity

Clear numbered sequence (Detection → Matrix → PoC → Chains → Tools → OPSEC) culminating in an explicit Decision Gate checklist that validates pre-escalation and downgrades otherwise — a concrete feedback loop. Not level 2 because validation checkpoints are explicit, not implicit.

3 / 3

Progressive Disclosure

Self-contained single-file skill with well-organized sections and no nested/deep references; per the simple-skill guideline, well-organized sections with no need for external files score 3. The inline 'finding-protocol' pointer is a one-level cross-skill reference, not a deep nest.

3 / 3

Total

12

/

12

Passed

Description

67%

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 specific and well-scoped to a distinct niche, clearly stating what the skill does. Its main weakness is the missing explicit "Use when…" trigger guidance and some jargon-heavy phrasing, which cap completeness and trigger-term quality at 2.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when testing CORS/Access-Control-Allow-Origin headers, reflected-origin or null-origin reflection, or credentialed cross-origin data theft.'

Soften jargon in the description by including common user-facing terms like 'ACAO', 'preflight', and 'Access-Control-Allow-Origin' alongside the technical classes.

Move or mirror the metadata when_to_use trigger list into the description itself so the when-guidance is visible without metadata inspection.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — "reflected origin, null origin, trusted-subdomain abuse, regex-validation bypass, and credentialed cross-origin data theft" — matching the score-3 anchor; it is not the vague single-action level 2.

3 / 3

Completeness

The "what" is explicit and thorough, but there is no "Use when…" clause or equivalent trigger guidance; per the judging guidelines a missing explicit trigger caps completeness at 2. Not level 1 because the what is strong.

2 / 3

Trigger Term Quality

Includes core natural terms ("CORS", "cross-origin", "origin") but leans on jargon ("regex-validation bypass", "trusted-subdomain abuse") and omits common variations a user might say ("ACAO", "preflight"). Not level 3 because coverage is uneven, not level 1 because key terms are present.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche (CORS misconfig exploitation) with distinct, non-overlapping triggers unlikely to fire for the wrong skill; matches the score-3 anchor.

3 / 3

Total

10

/

12

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
PurpleAILAB/Decepticon
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.