agentleFS
mhxiemhxie/Atelier/.claude/skills/reading/SKILL.md

reading

Skill5 starsChanged 35 days agoMITView on GitHub

Use when the user's primary intent is to have an article, paper, transcript, or note read and discussed: a supplied URL or wikilink is the main payload, or the user explicitly asks to read or discuss attached content. Incidental links in capture, inbox triage, save-for-later, or cited questions do not trigger this skill. Forwards into the canonical Atelier `/hi` router.

2 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not bypass /hi or call Reader directly.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Reading (Atelier entry hint)

Forward the user's input verbatim into /hi <user-text>. The router in skills/hi/SKILL.md selects the row and follows its procedure; reading dispatch is defined there, not here.

Trigger only when the URL, wikilink, or "read this" phrase is the request itself. URLs appear inside many other intents; these stay with the router:

  • Capture with a link (5/4 看了 https://... 觉得有意思): the URL is content.
  • Curate or inbox triage (triage my inbox, curate readwise), even with URLs.
  • Save for later (save this <url>): Scribe records the URL verbatim.
  • A question that cites a link: the question is the request.
  • A meal record with a restaurant link: dine.
  • Wikilinks inside structured notes (see also [[Foo]]).

Do not bypass /hi or call Reader directly; a reading-shaped phrase that is really about "this week" or feeling "burnt out" belongs to weekly or energy-audit, and only the router sees the whole catalog.

The entry-hint contract lives in protocols/runtime-adapters.md → Runtime Surfaces. When the reading concept changes in harness/intents.toml, update this description to match; lint checks structure, not trigger phrasing.

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.