agentleFS
ShawhinTShawhinT/non-coding-skills/skimmable-summary/SKILL.md

skimmable-summary

Skill40 starsChanged 13 days agoNo licenceView on GitHub

Shaw's house format for any multi-item summary, digest, briefing, status report, roundup, or a staged plan/roadmap he'll skim. Use whenever Claude presents several items across categories — scheduled-task reports, \"give me a rundown,\" \"catch me up on X,\" \"summarize my inbox/Slack/calendar/leads/pipeline,\" research roundups, sync results. Render as: a dated H1, a one-line count dashboard, emoji-headed sections with one-sentence linked items, every section always shown with an empty-state line, and a \"🔴 Needs Your Attention\" action closer. This is the DEFAULT presentation for digests to Shaw — apply it even when he doesn't name a format, and especially when he asks to make something \"easier to skim,\" \"more scannable,\" or \"match my format.\" When a task supplies its own section map, keep this frame with those sections. Do NOT use for single facts, one-item lookups, conversational replies, code, or long-form prose (reports, essays, letters, docs).

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

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