agentleFS
Sign inStart free
Zack-GroganZack-Grogan/agentos-foundation/.agents/skills/audit/SKILL.md

audit

Skill0 starsChanged 2 months agoMITView on GitHub

Audit workspace accessibility, truth states, responsiveness and interaction quality.

194 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use level-up and pm-discovery.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SkillPilotCHSkill

    level-up

    Eine Automatisierung pro Woche finden, scopen, shippen. Output landet als proposed-Eintrag in cadence.md mit konkreten Implementations-Schritten.

    Also in 12 projects that use this

  • ww-w-aiSkill

    pm-discovery

    PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 176 edited versions we read keep these.

  • 3

    Distinctive

    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:

    Read app shell rules first: no hero/masthead, conventional footer, default card grid or permanent chat.

    line 6
  2. Distinctive:

    Read the spatial contract.

    line 9
  3. Distinctive:

    Run the rubric against a complete workflow and its failures.

    line 11

“Common” is measured: kept by at least 6 in 10 of the 176 edited versions of this file we could read. “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

Read app shell rules first: no hero/masthead, conventional footer, default card grid or permanent chat; use contextual instruments and stable app windows.

Original AgentOS-specific procedure; not a vendored upstream skill. Read the spatial contract. Use visual grammar for styling and interactions for behavior; load only the relevant reference.

  1. Run the rubric against a complete workflow and its failures.
  2. Record severity, reproducible evidence and a smallest correction per issue.
  3. Separate layout evidence from backend and live-integration verification.

Deliver changed artifacts or a concrete review with evidence. Preserve canonical state and permission boundaries. Do not make the screenshot more attractive by hiding real failures.

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.

Check your setup, free