CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

audit-prep-assistant

Prepares codebases for security review using Trail of Bits' checklist. Helps set review goals, runs static analysis tools, increases test coverage, removes dead code, ensures accessibility, and generates documentation (flowcharts, user stories, inline comments). Use when preparing your own codebase to be audited by someone else, getting a repository review-ready before an external security review, deciding what to fix before auditors start, or asking what assessors need from a project. For understanding unfamiliar code you are about to audit, use audit-context-building instead.

Quality

76%

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 ./plugins/building-secure-contracts/skills/audit-prep-assistant/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

48%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 has a genuinely strong skeleton — a clear 4-step process, a valuable anti-rationalization table, and a timeline/checklist — but it is padded with a 135-line mock example and a 'What You'll Get' section that duplicates the process, while most concrete steps remain abstract bullets. Splitting reference material into separate files and trimming duplication would substantially improve it.

Suggestions

Cut or compress the ~135-line 'Example Output' mock package to a short 10-15 line excerpt (or move it to references/example-package.md) and delete the 'What You'll Get' section, which restates Steps 1-4 almost item-for-item.

Replace abstract bullets with concrete commands where possible — e.g., actual CodeQL/Semgrep invocation lines instead of the '# CodeQL and Semgrep checks' placeholder, and specific coverage/dead-code detection commands per platform (forge coverage, cargo-udeps, etc.) instead of 'Suggest new tests' / 'Find unused functions'.

Move the detailed documentation-generation guidance (flowcharts, user stories, actors/privileges, glossary) into a references/ file and reference it one level deep, keeping SKILL.md as a lean overview with the steps, tool commands, and checklist.

DimensionReasoningScore

Conciseness

Noticeably verbose with padded, duplicative sections: the ~135-line 'Example Output' mock package, the 'What You'll Get' section that restates Steps 1-4 nearly item-for-item, and 'How I Work' which repeats the four steps again. Roughly half the body restates content already present elsewhere; this matches the anchor 'noticeably verbose; several unnecessary explanations or padded sections' rather than the mostly-efficient anchor 3.

2 / 5

Actionability

Concrete guidance exists where it matters most (executable commands: 'slither . --exclude-dependencies', 'dylint --all', 'golangci-lint run', plus the rationalizations table's concrete required actions), but most of the body is abstract bullet lists ('Suggest new tests', 'Map primary workflows', 'Define user roles') with no commands or examples, and the multi-tool guidance is literally a placeholder comment ('# CodeQL and Semgrep checks'). This matches the anchor for some concrete but incomplete guidance with pseudocode-level gaps.

3 / 5

Workflow Clarity

Steps 1-4 are clearly sequenced with a timeline (2 weeks / 1 week / few days before) and a final prep checklist; explicit checkpoints appear ('Test on fresh environment', 'Verify build succeeds', 'Run full test suite') and the rationalizations table enforces not skipping steps. Minor validation gaps remain — e.g., no 'verify tests still pass after dead-code removal' step — keeping it at 'clear sequence with most checkpoints present' rather than the explicit feedback-loop anchor 5.

4 / 5

Progressive Disclosure

The body is well-sectioned with headers, but everything lives inline in a single ~400-line SKILL.md: no reference files exist (only an assets/trail-of-bits-mark.svg, which the body never references), and large blocks like the full example audit-prep package clearly belong in a separate reference file. This matches 'some structure but could be better organized; content that should be separate is inline'.

3 / 5

Total

12

/

20

Passed

Description

92%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 strong description: comprehensive third-person action list, an explicit multi-scenario 'Use when' clause, and explicit disambiguation from a related skill. The only minor gap is a few missing natural trigger synonyms such as 'audit prep'.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions in third person — 'Helps set review goals, runs static analysis tools, increases test coverage, removes dead code, ensures accessibility, and generates documentation (flowcharts, user stories, inline comments)' — covering the skill comprehensively. This matches the anchor for multiple specific concrete actions with comprehensive coverage; a 4 would require minor coverage gaps, which are not present.

5 / 5

Completeness

It explicitly answers both 'what' (the enumerated preparation actions) and 'when' via a dedicated 'Use when...' clause with four concrete trigger scenarios. This directly matches the anchor 'clearly and explicitly answers both what AND when with concrete trigger phrases'; score 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Natural trigger phrases are well covered: 'preparing your own codebase to be audited by someone else', 'getting a repository review-ready', 'before an external security review', 'deciding what to fix before auditors start', 'asking what assessors need from a project'. A few natural variations users might say (e.g., 'audit prep', 'pre-audit cleanup', 'security review checklist') are absent, so it sits between the 'good coverage' (4) and 'comprehensive synonyms' (5) anchors, closer to 4.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct (auditee-side preparation using Trail of Bits' checklist) and it actively disambiguates from the sibling skill: 'For understanding unfamiliar code you are about to audit, use audit-context-building instead.' Clear niche with distinct triggers and minimal conflict risk, matching the top anchor.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

trailofbits/skills

Path

plugins/building-secure-contracts/skills/audit-prep-assistant/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.