grackle: Skill for Claude Code

.claude/skills/ux-audit/SKILL.md

ux-audit is a skill for Claude Code from nick-pape/grackle. It costs 0 tokens per session (758 once invoked), scanned A, original, MIT.

A user-experience review process for the Grackle web interface, supported by screenshots. It examines the code and runs the application in a test mode to inspect its pages, states, and interactions.

In plain words
What is it for?
Use it to review navigation, layouts, forms, dialogs, task states, project views, settings, and other major screens in the Grackle web UI.
Why use it?
It creates an evidence-based list of interface problems and improvement ideas instead of relying only on reading source code or guessing how the application looks.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents.

This is nick-pape/grackle's own configuration. It tells Claude Code how to work on grackle itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything grackle configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/nick-pape/grackle/main/.claude/skills/ux-audit/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/nick-pape/grackle

Made for: Claude Code.

Wrote 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.

agentmods badge for ux-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/nick-pape/grackle/ux-audit/github.svg)](https://agentmods.dev/skills/nick-pape/grackle/ux-audit)
Your own site
<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.

agentmods 80×15 button for ux-audit

Your own site · 80×15
<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>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 758 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00758
Opus 5 $0.00000 $0.00379
Sonnet 5 $0.00000 $0.00152
Haiku 4.5 $0.00000 $0.00076

Measured 9d ago against content hash 54e48178080f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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 9d 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.

.claude/skills/ux-audit/SKILL.md · 64 lines

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

  1. 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
  2. Launch the app in mock mode — start the Vite dev server and open http://localhost:<port>/?mock using the Playwright MCP tools.

  3. 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.

  4. 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?

Read the full file on GitHub · 64 lines

Changes

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.

  1. 9d ago First seen · 64 lines · 0 tokens per session scan A 54e48178080f

Subscribe to this mod's changes

ux-audit is a skill published in the GitHub repository nick-pape/grackle (21 stars, last pushed 2mo 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.