agentleFS
Gaurav890Gaurav890/everything-agentic-engineering/.claude/skills/agentic-ux/SKILL.md

agentic-ux

Skill1 starsChanged 2 months agoMITView on GitHub

Design understandable, controllable, and trustworthy human-agent experiences. Use for copilots, tool-calling agents, generated artifacts, background work, approvals, multi-agent systems, persistent memory, streaming, or long-running workflows.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not default to a chat box.

    line 8

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agentic UX

Do not default to a chat box. Define:

  • what the agent knows, plans, is doing, and has changed;
  • idle, planning, queued, running, streaming, tool, approval, interrupted, partial, failed, retrying, complete, and handoff states;
  • user control: edit plan, approve, deny, pause, interrupt, undo, retry, correct;
  • trust: provenance, citations, confidence boundaries, permissions, previews, irreversible-action warnings, and memory visibility;
  • artifacts, background work, notifications, collaboration, and recovery.

Minimize anthropomorphism that obscures system state. Show enough process for users to predict consequences without dumping raw reasoning or logs. Test partial success and loss-of-connection paths, not only the ideal completion.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.