usability-flow-audit
Skill9 starsChanged 5 months agoMITView on GitHub
Audit ableton-mind user flows and developer flows. Use for install, doctor, CLI UX, docs quickstart, MCP tool ergonomics, recipe workflows, error messages, recovery steps and producer-facing usability.
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill to test whether users can install, diagnose and use ableton-mind without hidden knowledge.
- Distinctive: line 14
Run safe parts of the flow.
- Distinctive: line 15
Check that errors tell users what happened and what to do next.
- Distinctive: line 16
Check MCP tool and recipe ergonomics: names, schemas, defaults, verify/diff output and discoverability.
- Distinctive: line 17
Keep root docs English and localized docs under docs/pt.
- Very specific: line 21
Write _workspace/quality-audit/usability-{N}.md with:
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Usability Flow Audit
Use this skill to test whether users can install, diagnose and use ableton-mind without hidden knowledge.
Workflow
- Pick real personas: musician installing the bundle, developer using npm, MCP client user, contributor running tests.
- Trace each flow through README, docs, CLI and actual commands.
- Run safe parts of the flow. For unavailable Live/hardware steps, mark the exact prerequisite.
- Check that errors tell users what happened and what to do next.
- Check MCP tool and recipe ergonomics: names, schemas, defaults, verify/diff output and discoverability.
- Keep root docs English and localized docs under docs/pt.
Report Format
Write _workspace/quality-audit/usability-{N}.md with:
- Flow.
- Steps tested.
- Result.
- Friction or failure.
- Proposed copy/CLI/schema change.
- Verification step.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ableton-mind-buildSkill
- ableton-remote-scriptSkill
- cross-boundary-qaSkill
- device-schema-extractionSkill
- mcp-distributionSkill
- mcp-server-developmentSkill
- recipe-authoringSkill
- ableton-mind-buildSkill
- ableton-mind-quality-auditSkill
- ableton-remote-scriptSkill
- command-surface-auditSkill
- cross-boundary-qaSkill
- device-schema-extractionSkill
- local-copilotSkill
- mcp-distributionSkill
- mcp-server-developmentSkill
- recipe-authoringSkill
- refactor-maintainabilitySkill
- runtime-release-auditSkill
- security-auditSkill
- test-coverage-expansionSkill
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.