CtrlK
BlogDocsLog inGet started
Tessl Logo

access-control

Missing modifiers, wrong msg.sender checks, default-public functions, missing onlyOwner / onlyRole / onlyDAO authorization.

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/contracts/access-control/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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 audit playbook with executable commands, concrete PoC templates, and a clear step sequence, assuming the reader's competence throughout. Its only notable gap is the lack of an explicit completeness/validation checkpoint in the audit workflow.

Suggestions

Add an explicit verification checkpoint, e.g. a final step like 'Confirm every public/external state-changer from step 1 has been reviewed against the modifier checklist before closing the audit.'

Optionally surface the cross-referenced adjacent skills (sig-replay/SKILL.md) in a small 'Related playbooks' section rather than inline parentheticals.

DimensionReasoningScore

Conciseness

Lean and efficient throughout, assuming Solidity/audit competence; it does not explain what modifiers or access control are, and every section (grep recipes, modifier-bug table, PoC templates) earns its place.

3 / 3

Actionability

Provides fully executable grep and slither commands plus copy-paste-ready Foundry PoC tests (e.g. test_unauth_call, test_role_takeover) and concrete remediation code — concrete, specific, and runnable.

3 / 3

Workflow Clarity

The 7-step audit sequence is clearly ordered, but there is no explicit validation/completeness checkpoint telling Claude how to confirm it has found every state-changer or when the audit is complete; checkpoints are implicit.

2 / 3

Progressive Disclosure

A single well-organized file with clearly labeled sections and no deeply nested references; for a self-contained skill under the rubric's simple-skill note, this organization merits a top score.

3 / 3

Total

11

/

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 smart-contract access control, naming concrete bug categories rather than vague capabilities. Its main weakness is the absence of an explicit 'Use when...' trigger clause and incomplete coverage of natural-language terms users might say.

Suggestions

Add an explicit trigger clause, e.g. 'Use when auditing smart contracts for access control, missing modifiers, privilege escalation, or unprotected admin functions.'

Include more natural user-facing terms such as 'permission', 'authorization', and 'admin access' alongside the technical identifiers.

DimensionReasoningScore

Specificity

Lists multiple concrete failure categories: 'Missing modifiers, wrong msg.sender checks, default-public functions, missing onlyOwner / onlyRole / onlyDAO authorization' — specific actions/bugs rather than vague language.

3 / 3

Completeness

Clearly states what the skill covers (the bug classes), but the description lacks an explicit 'Use when...' trigger clause; per the rubric a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

Includes real terms like 'onlyOwner', 'msg.sender', and 'modifier', but misses common natural variations a user would say such as 'access control', 'permission', or 'authorization check'; coverage is partial.

2 / 3

Distinctiveness Conflict Risk

Scoped narrowly to smart-contract access control (onlyOwner/onlyRole/onlyDAO, msg.sender), a clear niche with distinct triggers unlikely to collide with other skills.

3 / 3

Total

10

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

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.