How do I install the Wordpress Workspace Agent UX Consistency Check skill?

Run npx skillmds@latest add automattic/wordpress-workspace-agent-ux-consistency-check in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Wordpress Workspace Agent UX Consistency Check safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Wordpress Workspace Agent UX Consistency Check?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Wordpress Workspace Agent UX Consistency Check free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Wordpress Workspace Agent UX Consistency Check?

Automattic (@automattic) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Wordpress Workspace Agent UX Consistency Check by automattic

Name: Wordpress Workspace Agent UX Consistency Check
Author: Automattic

Wordpress Workspace Agent UX Consistency Check

Review WordPress Workspace Agent, site picker, conversation history, Quick Ask, QuickLauncher, settings, and sidebar UX for consistency with the repo's plain, explicit, site-scoped interaction patterns. Use when changing Agent UI, site switching, starred/all-sites behavior, conversation pagination, or settings copy.

Automattic Updated Sep 17, 2026

File contents

WordPress Workspace Agent UX Consistency Check

Use this skill for recurring Agent and workspace UI patterns.

Workflow

Inspect the relevant UI and state.
- Common files: Sources/WordPressAgentWindowView.swift, Sources/WordPressAgentUtilityOverlayView.swift, Sources/MenuBarView.swift, Sources/SettingsView.swift, and Sources/AppState.swift.
- Search with rg -n "Starred|All Sites|Load previous|QuickLauncher|@|settings|shortcut|conversation|site" Sources.
Preserve site-scoped clarity.
- Make the active selected site visible before sending text, audio, images, screenshots, or Agent messages.
- Prefer explicit site switching over hidden "last site" behavior.
- When a user chooses a site-bound app or action, make that site handoff visible and update the current site deliberately.
- Use Starred and All Sites as plain labels.
Prefer calm, explicit controls.
- Avoid hidden auto-loading when a visible action is clearer.
- Use "Load previous conversations" for paging older history.
- Persist state users mentally own: starred sites, sidebar sections, collapse state, and cached lists.
- Keep buttons and settings copy straightforward rather than clever.
Keep settings explanatory.
- Toggles should say what changes when enabled, especially for artifacts, indexing, debug behavior, permissions, and setup reruns.
Review failure and empty states.
- Empty, loading, signed-out, no-site, no-results, and permission-denied states should be specific and actionable.

Output

Lead with UX inconsistencies and behavioral risks.
Include file and line references.
Separate product-language suggestions from implementation bugs.

---name: wordpress-workspace-agent-ux-consistency-checkdescription: Review WordPress Workspace Agent, site picker, conversation history, Quick Ask, QuickLauncher, settings, and sidebar UX for consistency with the repo's plain, explicit, site-scoped interaction patterns. Use when changing Agent UI, site switching, starred/all-sites behavior, conversation pagination, or settings copy.---# WordPress Workspace Agent UX Consistency CheckUse this skill for recurring Agent and workspace UI patterns.## Workflow1. Inspect the relevant UI and state. - Common files: `Sources/WordPressAgentWindowView.swift`, `Sources/WordPressAgentUtilityOverlayView.swift`, `Sources/MenuBarView.swift`, `Sources/SettingsView.swift`, and `Sources/AppState.swift`. - Search with `rg -n "Starred|All Sites|Load previous|QuickLauncher|@|settings|shortcut|conversation|site" Sources`.2. Preserve site-scoped clarity. - Make the active selected site visible before sending text, audio, images, screenshots, or Agent messages. - Prefer explicit site switching over hidden "last site" behavior. - When a user chooses a site-bound app or action, make that site handoff visible and update the current site deliberately. - Use Starred and All Sites as plain labels.3. Prefer calm, explicit controls. - Avoid hidden auto-loading when a visible action is clearer. - Use "Load previous conversations" for paging older history. - Persist state users mentally own: starred sites, sidebar sections, collapse state, and cached lists. - Keep buttons and settings copy straightforward rather than clever.4. Keep settings explanatory. - Toggles should say what changes when enabled, especially for artifacts, indexing, debug behavior, permissions, and setup reruns.5. Review failure and empty states. - Empty, loading, signed-out, no-site, no-results, and permission-denied states should be specific and actionable.## Output- Lead with UX inconsistencies and behavioral risks.- Include file and line references.- Separate product-language suggestions from implementation bugs.

Frequently asked questions