functional-audit
Skill0 starsChanged 13 days agoMITView on GitHub
Run an authorized functional and visual audit of the user's own application: user journeys with test accounts, UI vs server-side authorization, error states, timeouts, accessibility and visual regressions, using a configured browser integration or producing a manual test plan. Use when the user invokes functional-audit or asks for functional/visual QA.
In this repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- full-auditSkill
- security-auditor-proSkill
- security-auditSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Start with step 1 (authorization and scope).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
functional-audit
Mode: FUNCTIONAL.
Load and follow the core procedure in ../security-auditor-pro/SKILL.md (relative to this skill's directory),
including its policy (../security-auditor-pro/references/POLICY.md), steps and hard rules.
Focus: critical user journeys with test accounts and synthetic data; check that every UI restriction is also enforced server-side (hidden buttons are not security controls); error, empty and timeout states; accessibility basics; visual regressions. If no browser integration (e.g. Playwright MCP) is available, deliver a step-by-step manual test plan and mark visual coverage as NOT TESTED.
Start with step 1 (authorization and scope). If scope is unknown, ask for it before doing anything else.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

