CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bfla

Broken Function Level Authorization (BFLA) — exploit action-level access control failures where lower-privileged principals invoke admin/staff functions across REST, GraphQL, gRPC, WebSocket, and background job paths.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 offensive-testing skill: every step is executable, the admin-baseline-then-replay methodology is explicitly validated with a checklist and verification script, and there is no wasted prose. The only structural improvement would be offloading the framework table and transport-specific sections into reference files to slim the main SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense and lean — almost entirely executable commands, terse lists ("Look for: method returning 200/204 where others return 403"), and tables, with no padding or explanation of concepts Claude already knows. Minor trimmable framing (intro paragraph, Detection Notes, ATT&CK mapping) keeps it just below anchor 5.

4 / 5

Actionability

Fully executable, copy-paste-ready curl, Python, and grpcurl snippets with placeholders cover the common cases: admin baseline and replay diff, method alternation loop, encoding/trailing-slash alternation, GraphQL mutations with alias batching, background job approval, and header trust bypass. The framework weaknesses table gives concrete, named patterns per framework.

5 / 5

Workflow Clarity

A clear numbered sequence (recon and actor x action matrix, admin baseline first to rule out a universally broken action, lower-privilege replay with a stated win condition, then method/transport/GraphQL/job/header variations) is capped by an explicit Verification section with a 3-part confirmation checklist and an executable verification script. Validation checkpoints for the destructive/batch operations are present, so the workflow-clarity cap does not apply.

5 / 5

Progressive Disclosure

No bundle files exist, so the skill is a single self-contained file; it is well-sectioned with clear headers and easy navigation. At ~240 lines, content such as the framework weaknesses table, gRPC testing, and detection notes could be split into reference files, which keeps it below anchor 5's ideal split; structure is far above anchor 3's disorganized inline bulk.

4 / 5

Total

18

/

20

Passed

Description

70%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, well-scoped, third-person description that clearly communicates the skill's niche and transport coverage. Its main weakness is the missing "Use when..." trigger clause, which caps completeness and limits natural-language discoverability beyond technical jargon.

Suggestions

Append an explicit trigger clause to the description, e.g., "Use when testing for BFLA, broken function level authorization, admin endpoint bypass, or privilege escalation via admin APIs."

Include one or two natural-language synonyms (e.g., "privilege escalation", "admin API bypass") directly in the description rather than only in metadata.when_to_use, so users who don't know the acronym BFLA can still trigger the skill.

State the concrete actions users get out of the skill (e.g., enumerate the actor x action matrix, replay requests across roles, verify durable state changes) to round out the capability list.

DimensionReasoningScore

Specificity

The description names a concrete action ("exploit action-level access control failures where lower-privileged principals invoke admin/staff functions") and enumerates five specific transport surfaces (REST, GraphQL, gRPC, WebSocket, background job paths). It falls just short of anchor 5 because it describes a single capability pattern rather than multiple distinct actions, and is well above anchor 3's minimal 1-2 generic actions.

4 / 5

Completeness

The "what" is clearly and specifically stated, but the description contains no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. It is not a 4 because the "when" is absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural terms a pentester would say are present: "BFLA", "Broken Function Level Authorization", "admin/staff functions", and the transport names. A few natural synonyms (e.g., "privilege escalation", "admin endpoint bypass") are missing from the description itself — they appear only in metadata.when_to_use — which keeps it below anchor 5 but above anchor 3's incomplete keyword coverage.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — action-level authorization testing, explicitly framed as distinct from object-level (IDOR) issues — with distinct trigger terms, so the risk of firing for the wrong skill is minimal.

5 / 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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/exploit/web/bfla/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.