copilot-interaction-reviewer
Skill0 starsChanged 9 months agoNo licenceView on GitHub
Reviews any product artifact — a PRD, user flow, UX copy, design description, wireframe annotation, interaction spec, error state, or feature idea — through a senior UX designer's lens, specifically calibrated for Copilot and AI-powered experiences in Microsoft 365. Trigger this skill whenever someone shares work involving an AI or Copilot interaction and wants critique, a design review, a pre-ship check, a craft review, an accessibility audit, or just wants to know if their design is good. Also trigger for questions like "does this feel right?", "what am I missing?", "is this on-brand?", "how would a designer review this?", or "how do I make this better?" If the artifact touches Copilot entry points, response surfaces, agent flows, prompt UI, AI-generated content, AI error states, loading/streaming states, or any AI-driven feature in Word, Excel, PowerPoint, Outlook, Teams, or any M365 surface — use this skill immediately.
In this repository3 other files it gives its agents.
- fluent-designSkill
- frontend-designSkill
- ux-auditSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. About 0 are common, 24 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈24
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
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.

