agentleFS
anyreachaianyreachai/claude-skills/skills/visual-brief/SKILL.md

visual-brief

Skill1 starsChanged 7 months agoNo licenceView on GitHub

Turn dense, hard-to-read material (long emails, specs, program reviews, PDFs, transcripts, data dumps, RFPs, assessments) into a scannable scroll-deck brief — a single HTML artifact of alternating dark/light bands, each with one claim headline and one chart or diagram drawn to scale, plus at most two motion pieces that explain the core mechanism. Use whenever Richard drops content and asks for \"the high level\", \"make this visual\", \"easy to digest\", \"something I can screenshare\", \"a one-pager\", \"a brief\", \"a visual summary\", \"turn this into a deck-like page\", or says material is \"dense\", \"hard to read\", \"too long\", or \"wall of text\" — even when he does not say \"visual\". Also use for refreshes of an existing brief (\"add a section on X\", \"make it share-safe\", \"redo it in the deck style\"). Always start from this skill instead of designing a page from scratch: it carries the visual grammar, the Anyreach deck design system, the motion patterns, and the internal/external split that past briefs got right.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

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