Borrowing it
Nothing to install: this file belongs to nick-pape/grackle. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nick-pape/grackle/main/.claude/skills/ux-audit/SKILL.mdgit clone --depth 1 https://github.com/nick-pape/grackleWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/nick-pape/grackle/ux-audit)<a href="https://agentmods.dev/skills/nick-pape/grackle/ux-audit"><img src="https://agentmods.dev/badge/skills/nick-pape/grackle/ux-audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/nick-pape/grackle/ux-audit"><img src="https://agentmods.dev/badge/skills/nick-pape/grackle/ux-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00758 |
| Opus 5.5 | $0.00000 | $0.00303 |
| Sonnet 5.5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
ux-audit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Audit Skill
Performs a comprehensive User Experience audit of the Grackle web UI, producing a prioritized report of improvement proposals backed by screenshots.
Invocation
/ux-audit
What It Does
-
Explore the codebase — launch subagents in parallel to understand:
- Web UI component structure, routing, navigation, layout (
packages/web/src/) - Proto definitions and data model (
packages/common/proto/,packages/server/) - All entity types, their fields, relationships, and status lifecycles
- Forms, creation experiences, modals, and interaction patterns
- Web UI component structure, routing, navigation, layout (
-
Launch the app in mock mode — start the Vite dev server and open
http://localhost:<port>/?mockusing the Playwright MCP tools. -
Visually inspect every major state — navigate through the UI using Playwright MCP (
browser_navigate,browser_click,browser_snapshot,browser_take_screenshot) capturing screenshots of:- Landing / empty state
- Each sidebar tab (Projects, Environments)
- Project expanded with task tree
- Every task status (pending, blocked, in_progress, review, done, failed)
- Every task tab (Overview, Stream, Diff, Findings)
- Project DAG view
- Settings page
- Every creation form (project, task, subtask, environment, token)
- Any edge cases or surprising behaviors discovered
Save screenshots to
screenshots/with descriptive names. -
Analyze as a UX Designer — put on a Product UX Designer hat and evaluate:
- Information architecture: Does the navigation make sense? Is the hierarchy clear?
- Consistency: Are creation patterns, action placements, and interaction models consistent?
- Discoverability: Can users find features? Are empty states helpful?
- Efficiency: Are common workflows streamlined? Any unnecessary clicks?
- Visual design: Is space used well? Are important elements prominent?
- Completeness: Are there data model fields not exposed in the UI? Missing CRUD operations?
- Standards compliance: Does it follow common UI conventions?
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 64 lines · 0 tokens per session scan A 54e48178080f
ux-audit is a skill published in the GitHub repository nick-pape/grackle (22 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 758 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
configure-coddy
Change Coddy's own configuration when the user asks for it: edit settings, providers, models, logging, permissions, or find, install, update, and remove MCP servers and skills. Stages UCI-style commands for config.yaml and commits only after the user confirms saving; MCP servers are entries of the mcp.json files. Load…
crossreview
Run when the user invokes /crossreview (or /crossreview:setup to choose the reviewers) or asks for a cross-review, a quorum review or a second opinion from other agents or models: fan a code review (uncommitted work, a branch, a commit range, files, a plan or a document) out to several console code agents (Claude…
rpa-init
Run when the user invokes /rpa-init or asks to onboard or warm up context on a repository. The agent studies code, reads documentation and test code, sets up the dev environment as the project expects, runs tests, and writes a short project report. No extra user brief is required.
rpa-gen-rules
Use when the user invokes /rpa-gen-rules or asks to create, refresh, audit, or synchronize project instructions such as root AGENTS.md, Cursor .cursor/rules, or Claude Code .claude/rules, especially when existing rule trees have drifted.
rpa-feat
Run when the user invokes /rpa-feat together with a clear feature description (for example issue text). BDD workflow: plan, failing tests, implementation, green tests, full suite, docs and examples, linter at the end. Will not work correctly without the user supplying what to build.
rpa-bugfix
Run when the user invokes /rpa-bugfix together with a clear bug description (expected vs actual, reproduction). Reproduction test first, then fix, full test suite, short report. Will not work correctly without the bug details.