CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bypassing-authentication-with-forced-browsing

Discovering and accessing unprotected pages, APIs, and administrative interfaces by enumerating URLs and bypassing authentication controls during authorized security assessments.

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/bypassing-authentication-with-forced-browsing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 highly actionable, well-sequenced skill body built almost entirely from executable ffuf/gobuster/curl commands that cover the technique comprehensively. The two real weaknesses are the missing validation of batch-enumeration results (no false-positive/soft-404 baseline or confirmation step, which caps workflow clarity) and complete failure to reference the existing scripts/agent.py and references/api-reference.md bundle files, leaving them orphaned.

Suggestions

Add a false-positive baseline step to the enumeration workflow (e.g., probe a random nonexistent path to calibrate soft-404 response size/status and use ffuf -fs auto or -fl to filter), plus an explicit 'manually confirm each finding before reporting' checkpoint.

Wire up the bundle: add a step or note pointing to `python scripts/agent.py --target <url> --admin-paths --session-cookie <token>` as the automated path, and link to references/api-reference.md for the full argument tables and function documentation.

Trim the Key Concepts table (Claude already knows these terms) and drop or fold the Feroxbuster/DirBuster rows from Tools & Systems, since neither tool is used anywhere in the workflow.

DimensionReasoningScore

Conciseness

The workflow itself is lean — each step is a one-line lead-in followed by executable commands — but the "Key Concepts" table (Forced Browsing, Directory Enumeration, Path Normalization, etc.) and "Tools & Systems" table restate knowledge Claude already has, and the Tools table lists Feroxbuster and DirBuster that never appear in the workflow. These are minor, trimmable instances of over-explanation rather than the 'some unnecessary explanation' of score 3, since the bulk of the body is compact, purposeful command blocks.

4 / 5

Actionability

Nearly every step is copy-paste-ready: ffuf commands with real wordlist paths, match codes, output files, thread/rate flags; gobuster invocations; shell loops for actuator endpoints, HTTP methods, and sensitive files; concrete curl comparisons for authenticated vs unauthenticated access. Coverage spans directories, files, extensions, admin paths, API endpoints, actuator, method override, path normalization, double encoding, and backups, matching the 'fully executable, covers the common cases' anchor.

5 / 5

Workflow Clarity

The six steps are clearly sequenced (enumerate → find admin/debug → test auth enforcement → method bypass → path bypass → backup discovery) and Step 3 includes an explicit verification heuristic ("If both return similar content, authentication is not enforced"). However, the batch enumeration operations have no result-validation guidance: there is no soft-404 / custom-error-page baseline check (a classic false-positive source for ffuf-based discovery) and no manual-confirmation checkpoint before reporting findings. Per the guideline capping batch-operation workflows without validation at 3, this sits at score 3 rather than 4, though it is above score 2 because the sequence and one checkpoint are genuinely present.

3 / 5

Progressive Disclosure

The body is well-sectioned (When to Use, Prerequisites, numbered Workflow, Scenarios, Output Format) and stays a reasonable length, but it never references the bundle files that actually exist: references/api-reference.md and scripts/agent.py are completely orphaned — no link, no mention, no navigation — despite automating and documenting exactly what the body teaches. Content that could live in the reference file (command catalogs, argument tables) is inlined. This matches 'some structure but could be better organized' with references effectively unsignaled; not score 2 because the in-body structure itself is solid and the body is not an unstructured wall of text.

3 / 5

Total

15

/

20

Passed

Description

71%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 specific, concrete description written in appropriate third-person voice that clearly communicates what the skill does and to which resource types. Its main weakness is the absence of an explicit 'Use when...' trigger clause — the temporal context is limited to 'during authorized security assessments' — and the omission of the term 'forced browsing' itself as a natural trigger keyword.

Suggestions

Append an explicit trigger clause, e.g. "Use when testing an authorized target for hidden or unlinked admin panels, unprotected API endpoints, exposed backup/config files, or endpoints missing authentication checks."

Work natural synonyms into the description — "forced browsing", "admin panel", "directory enumeration" — so it matches the phrasings users actually type.

Keep the current concrete action list intact; it is the description's strongest element and should not be trimmed when adding the trigger clause.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with named target types: "Discovering and accessing unprotected pages, APIs, and administrative interfaces by enumerating URLs and bypassing authentication controls". It names both the techniques (URL enumeration, authentication bypass) and the resource types (pages, APIs, admin interfaces), matching the comprehensive-coverage anchor rather than the score-4 anchor's 'minor gaps'.

5 / 5

Completeness

The "what" is clearly and concretely stated, but the only "when" is the scope qualifier "during authorized security assessments" — a deployment context, not explicit trigger guidance. Per the guideline that a missing 'Use when...' clause or equivalent caps completeness at 3, this matches the 'clear what, when weakly implied' anchor; it is above score 2 (the what is specific, not vague) but below score 4 (no explicit when-to-invoke statement).

3 / 5

Trigger Term Quality

Good natural keywords are present ("unprotected pages", "APIs", "administrative interfaces", "enumerating URLs", "bypassing authentication", "authorized security assessments"), but a few natural terms users would say are missing — notably the technique's own name "forced browsing" (it appears only in the skill name), plus synonyms like "admin panel", "hidden endpoints", or "directory brute-forcing". Fits the 'good coverage, a few natural terms missing' anchor; not score 5 because synonym coverage is incomplete, not score 3 because the included terms are natural and well-chosen rather than merely 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The auth-bypass/forced-browsing niche is well-delineated with specific triggers (unprotected pages, admin interfaces, URL enumeration, authentication controls), so it is mostly distinct from unrelated skills. Minor overlap risk remains with closely related web-app pentest skills (general directory enumeration, broken-access-control testing), which matches score 4 rather than 5's 'minimal conflict risk'.

4 / 5

Total

16

/

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/bypassing-authentication-with-forced-browsing/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.