Agent Skills (mblode)
A skill set against AI slop: UI and typography audits, change review, releases, docs and SEO.
- 199 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Release and CI skills run commands, change branches and publish npm packages.
- SEO and UI audits use the network and a browser.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/agent-skills-mblodeDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Release and CI skills run commands, change branches and publish npm packages.
- SEO and UI audits use the network and a browser.
This is third-party code. Review the repository files before installing.
What it does
Matthew Blode's repository collects skills for checking and bringing agent output to a standard fit for release. The design group has `product-design`, `ui-design` with a React and Next.js audit and a ship verdict, `ui-verification` with nine browser probes and `ui-animation` for springs and curves taken from a screen recording. For text there are `ghostwriter`, which writes as you with no visible AI tells, and `eli5`. Quality is checked by `typography-audit` with 78 rules, `dx-audit`, `ax-audit` and `seo`. Shipping uses `tidy` for diff or pull request review with `file:line` findings, `pr-creator`, `pr-babysitter`, `autoship` for npm releases and `ci-speedup`. There are also tools for skills themselves: `agent-skills-creator` and `chat-history`.
Who it is for. Developers and design engineers who hand interfaces and releases to an agent and want checks before shipping.
Good fit when
- A finished Next.js page is checked with a UI audit that ends in a ship verdict.
- Before merge a diff is reviewed with `file:line` findings in confirmed and plausible tiers.
- An npm release goes through changesets, CI watching and publish verification.
- Messages, posts and docs are written as you with no trace of AI.
Not a fit when
- You need one narrow skill with a short instruction.
- The work is outside TypeScript, React and Next.js.
- You want automatic merging with no human confirmation.
Example request
Audit the interface of this Next.js page with the ui-design skill and give a ship verdict with concrete findings.Limitations
The set contains a few dozen skills and some run only by name, for example `app-verification`, `test-audit` and `ci-speedup`. The `tidy` skill only reports by default and fixes only in apply mode. Many skills are tuned to the author's stack: Next.js, Tailwind, Vercel, Linear and changesets. SEO and audit skills use the network and a browser, so access is needed. Install only the skills you need to keep the agent's list short.
How to disable. Delete the relevant folders from `~/.claude/skills/` and `~/.codex/skills/` or reverse the install through `npx skills`. Skills installed without global mode live in the project directory.
FAQ
How do I install the set?
With `npx skills add mblode/agent-skills -g --agent codex claude-code -y`. For one skill use `--skill` with its name.
What does `tidy` do?
It reviews a diff or pull request and returns `file:line` findings in confirmed and plausible tiers: bugs, structure, AI slop, security and tests. By default it only reports, and apply mode makes fixes.
How does `ghostwriter` differ from a plain editor?
It writes as you or your company and strips AI tells. A profile can be skipped, built from your samples or learned from your edits.
Which audits are included?
`typography-audit` with 78 rules, `dx-audit` for libraries and CLIs with 38 rules, `ax-audit` with 24 rules on agentic experience, `seo` and `test-audit`.
What is `autoship` for?
It drives an npm release on changesets: a fix loop, CI watching, merging Version Packages and OIDC publish verification.
Discussion
No questions or reviews yet.
Related
SkillsBuilder Skills
Skills for agents
A set of small skills from Builder.io for agent work habits: visual plans and diff recaps, docs-first checks, cross-agent review and clean status updates
Tech Leads Club Agent Skills
Agent Skills
A vetted skill registry with a CLI that installs into twenty-plus agents and an MCP server for on-demand skill lookup
Dozens of mizchi's agent skills: frontend audits, AWS, Cloudflare, SQL, Playwright and OpenTelemetry, installed one by one
19 skills for UI, code and copy: the agent decides from project evidence and verifies results rather than making a template.
A library of 30-plus instruction skills for coding agents: planning, building, testing, hallucination guards and shipping
A skills library for Claude Code, Cursor and Codex: team code review, TDD, stacked PRs and repository readiness scoring
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Agent Skills (mblode) (this card) | no | 199 | |
| Impeccable | no | 108,873 | a UI design and review skill; this set adds typography and SEO audits together with change review and releases |
| UI Skills | no | 10,998 | UI skills; the mblode set adds diff review, npm shipping and CI work |
README in short
Skills are grouped into architecture, design, writing, quality, shipping and authoring. The author also points to a separate course on spotting and fixing AI slop, while the set itself is built for agents.
README badge
Original SKILL.md
--- name: tidy description: Reviews a local diff, branch diff, or PR with file:line findings in confirmed and plausible tiers, gates any test the diff adds or changes, and in apply mode lands the fixes and diff-scoped simplifications. Use when asked to "review my changes", "code review", "tidy this", "simplify my diff", "deslop this", "structural review", "security audit", or "audit these tests in my PR". For the PR itself use pr-creator; for CI and review threads use pr-babysitter; for UI defects use ui-design; for repo architecture use codebase-architecture; for pruning the whole suite to a target use test-audit. --- # Tidy Review the diff, then fix it when asked. One pass produces the report; the same pass, in apply mode, lands the fixes along with the simplifications a clean diff still hides. - **IS:** review of a local diff, branch diff, PR, or named security scope, returning severity-tiered findings with `file:line` evidence; in apply mode, the smallest complete fixes for those findings plus diff-scoped simplification. - **IS NOT:** creating PRs (`pr-creator`), CI failures and review threads (`pr-babysitter`), user-facing UX, accessibility, or rendered quality (`ui-design` Audit mode), library or CLI ergonomics (`dx-audit`), architecture briefs and repo-wide guardrails (`codebase-architecture`), reviewing plans (`planning`), suite-wide test pruning to a measured target (`test-audit`). ## Report or apply **Report** is the default: "review my changes", "code review", a mode phrase below, or a PR number. Done is the report in the format under Output, carrying the range reviewed, each baseline command's last line, and the references read. The working tree stays as it was. Do not edit a file in report mode, even for a one-character fix; the moment the tree changes the user loses the read-only report they asked for. **Apply** when the user says "tidy", "simplify", "fix", "apply the findings", or asks for the changes to be made. Done is the confirmed findings and supported simplifications in the working tree, the affected checks passing or their failures shown to be baseline, and a summary of what changed, what was left and why, and the check results. Apply mode edits any file the diff touches or a fix requires, and runs the repository's documented lint, type, and test commands without asking: they run locally against the working tree, and landing the changes is what was asked for. It does not commit, push, open PRs, add or upgrade dependencies, run migrations, or write outside the working tree. A report from earlier in the session is input, not authority: apply what current evidence supports and say why anything was not applied. ## Harness precedence Claude Code bundles `/code-review` (correctness plus cleanups, with `--fix`) and `/security-review`. A typed slash command runs the bundled skill; this one runs when named or when a mode phrase matches, and adds the Structural and Deslop modes, a whole-repo Security audit, the plausible tier the bundled commands filter out, `REVIEW.md` support, and the same report on any harness with git and the file tools. Findings from a bundled review already run this session enter the verdict step as candidates rather than being re-derived. ## Mode dispatch Pick one lens from the user's wording. `references/severity-rubric.md` loads in every mode; the table adds the mode's own rubric. | Mode | Triggers | Adds | Scope | |------|----------|------|-------| | **Standard** (default) | `/tidy`, "review my changes", "code review", "tidy this" | nothing | Local or branch diff | | **Structural** | "structural review", "thermo-nuclear review", "deep code quality audit", "harsh maintainability review", "code judo" | `references/structural-quality-rubric.md` | Local or branch diff | | **Deslop** | "deslop this", "clean up AI code", "remove slop", "review for AI patterns" | `references/ai-slop-patterns.md` | Local or branch diff | | **Security audit** | "security audit", "find vulnerabilities", "deepsec", "threat model", "audit for security" | `references/security-checklist.md` | Named subsystem or whole repo, regardless of diff | Conditional loads, in any mode: - `references/context-errors.md` when the diff was agent-written, or adds, changes, or removes a module, system boundary, guard, or fallback. - `references/security-checklist.md` for auth, input handling, external APIs, uploads, dependency or lockfile changes, or environment config. - `references/performance-checklist.md` for fetching, rendering, images, dependencies, or bundle-affecting imports. - `references/test-gate.md` when the diff adds or changes a test. A diff with no test changes loads nothing extra here. - `agents/openai.yaml` only for the optional second-opinion pass in step 3. Otherwise it is launcher metadata for external runners and never loads. ## Workflow 1. **Discover target.** Staged and unstaged changes first (`git diff --stat`, `git diff --staged --stat`); if clean, the branch diff against `git merge-base HEAD origin/<default>`. For a PR, `gh pr diff <n>` with the branch checked out. Record the range or ref pair; it goes in the report. 2. **Gather context.** Open the mode references and the conditional loads with the file tools. A filename in this skill is a pointer, not loaded content; if a required read fails, report the coverage gap rather than claiming the rubric was applied. Capture intent from the user's words, the commit messages, and the PR description. Load scoped `AGENTS.md` / `CLAUDE.md` and a root `REVIEW.md` where one exists: both override this skill's defaults when they conflict, so a pattern they mandate is not a finding. Reuse checks already run on this revision; when a candidate needs execution, run the documented command and preserve its exit status.