CtrlK
BlogDocsLog inGet started
Tessl Logo

mass-assignment

Mass assignment + ORM leak — inject extra fields into create/update requests, escalate to admin, leak protected fields via response.

64

Quality

76%

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/exploit/web/mass-assignment/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 skill is highly actionable with executable code and explicit verification checkpoints, and is well-structured and mostly token-efficient. Main improvements are making the field-iteration feedback loop explicit and optionally splitting the wordlist/framework patterns into a reference file.

Suggestions

Add an explicit feedback loop in the Detect section: 'If no field persists, iterate the section 2 wordlist via Burp Intruder and re-fetch after each batch.'

Consider moving the section 2 field wordlist and section 3 framework patterns into a references/ file (e.g. FIELDS.md) to tighten the overview and improve progressive disclosure.

Trim the 'Known exemplars' section or move it to a reference, since historical context does not aid execution.

DimensionReasoningScore

Conciseness

The body is dense and mostly code/wordlists with little concept over-explanation, but sections like 'Known exemplars' and the severity commentary are tokens that don't directly aid execution.

4 / 5

Actionability

Provides copy-paste-ready PATCH payloads, a concrete privileged-field wordlist, framework-specific snippets (Rails/Django/Express/Spring/Go), and a fully executable Python PoC covering the common cases.

5 / 5

Workflow Clarity

A clear 8-section detect→PoC→defend sequence with explicit validation ('Re-fetch own profile…→ mass assignment', assert is_admin, 'delete another user → confirm admin') avoids the destructive-skill cap; only the error-recovery feedback loop is implicit rather than spelled out.

4 / 5

Progressive Disclosure

Well-organized numbered sections with no nested references, but it is a single ~145-line file where the field wordlist and framework patterns could be split into a one-level-deep reference; the Cross-references point to external upstream paths rather than bundled refs.

4 / 5

Total

17

/

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.

The description is specific and occupies a distinct niche, but lacks an explicit 'Use when...' trigger clause, which caps completeness and leaves trigger-term coverage short of synonyms. Adding a 'Use when...' clause with a few more natural trigger phrases would raise it.

Suggestions

Append an explicit trigger clause, e.g. 'Use when testing APIs for mass assignment, missing strong params / over-permissive serializers, or ORM response leaks.'

Add a few natural synonyms users say ('strong params', 'permit', 'role escalation', 'over-permissive') to broaden trigger-term coverage.

Keep the concrete action list as-is — it already names multiple specific actions covering both the request-side and response-side vectors.

DimensionReasoningScore

Specificity

Quotes 'inject extra fields into create/update requests, escalate to admin, leak protected fields via response' — three concrete actions covering both attack vectors, but not a clean 5 since it omits a detect/verify framing.

4 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' trigger clause, so per the judging guidelines completeness is capped at 3 even though the 'when' is weakly implied.

3 / 5

Trigger Term Quality

Includes the natural core terms 'mass assignment', 'ORM leak', 'admin', and 'protected fields', but is missing common synonyms such as 'strong params', 'role escalation', or 'over-permissive'.

4 / 5

Distinctiveness Conflict Risk

'Mass assignment + ORM leak' names a clear, specific security niche with distinct triggers and minimal overlap risk with other skills.

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.

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.