CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

web-auth-mapping

Authentication surface — login endpoints, JWT/OAuth/SAML/SSO/API-key mechanism identification.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/recon/web-recon/auth-mapping/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 body is a tight, executable recon procedure: a runnable endpoint-discovery loop, a dense mechanism-to-signal identification table, and a concrete handoff output spec, organized into clean sections with no padding or over-explanation. Its only notable gaps are the absence of runnable commands for a couple of signal checks and no explicit retry/validation loop, which keep actionability and workflow clarity at 4.

DimensionReasoningScore

Conciseness

The body is lean with no explanation of concepts Claude already knows — the intro only states purpose ("Exploit downstream needs to know exactly how to hold a session") and the signal table is dense and non-redundant, matching the 5 anchor where every token earns its place.

5 / 5

Actionability

The curl status-code loop over common auth paths is real, executable bash, and the mechanism table gives concrete detection signals (`Set-Cookie`, `Authorization: Bearer eyJ...`, `SAMLRequest`), matching the 4 anchor; it falls short of 5 because probing Bearer/API-key acceptance is described as signals rather than given as runnable commands, and section 3 is guidance rather than code.

4 / 5

Workflow Clarity

A clear three-step sequence (discover endpoints → identify mechanisms → record handoff output) with the inline `[ "$code" != "404" ]` filter and the "success/fail signals" spec acting as checkpoints, fitting the 4 anchor; it lacks the explicit validate-fix-retry feedback loop of the 5 anchor, but this is read-only recon so no destructive/batch cap applies.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and the body is under 50 lines organized into three well-labeled sections with no content that needs to be split out — per the rubric's simple-skill guideline this scores 5.

5 / 5

Total

18

/

20

Passed

Description

61%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 concrete and domain-specific with good trigger keywords, but it omits an explicit "Use when..." trigger clause and frames its content as objects rather than multiple distinct actions, capping completeness and specificity. It is clearly distinguishable from unrelated skills with only minor conflict risk against close auth-related siblings.

Suggestions

Add an explicit "Use when..." trigger clause to the description (e.g., "Use when mapping the auth surface of a target, finding login endpoints, or identifying session/token mechanisms") to raise completeness above 3.

Lead with third-person action verbs covering the full workflow (e.g., "Maps authentication surfaces: discovers login endpoints and identifies JWT/OAuth/SAML/SSO/API-key mechanisms") so specificity reflects several concrete actions rather than one.

Include common trigger synonyms such as "auth", "sign-in", "credentials", and "session" to broaden natural keyword coverage toward the 5 anchor.

DimensionReasoningScore

Specificity

Names the domain and concrete mechanism objects ("login endpoints, JWT/OAuth/SAML/SSO/API-key mechanism identification"), but the only action verb is "identification" — it lists objects, not the several distinct actions (discover, map, record) the 4 anchor requires, while being far more concrete than the 2 anchor's generic "Processes PDF files".

3 / 5

Completeness

The "what" is clear (identify authentication mechanisms and login endpoints), but the description contains no "Use when..." clause or equivalent explicit trigger guidance, which the rubric caps at 3; the "when" is absent rather than merely weakly implied, so 4 does not fit.

3 / 5

Trigger Term Quality

Includes natural terms users would say — "Authentication", "login", "JWT", "OAuth", "SAML", "SSO", "API key" — but misses common variations like "auth", "sign-in", "credentials", and "session", so it falls short of the 5 anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"Authentication surface" with named protocols (JWT/OAuth/SAML/SSO/API-key) carves a mostly distinct recon niche, but authentication is a broad domain where sibling recon or exploit skills likely exist, giving minor overlap risk rather than the minimal risk of the 5 anchor.

4 / 5

Total

14

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/recon/web-recon/auth-mapping/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.