scan
Skill0 starsChanged 12 days agoMITView on GitHub
Classify an image the user sends (handwritten notes / printed document / homework / a screenshot / a meme), confirm the read, then route it to the right place. Use for any photo/image, or the //scan command.
35 other projects use a version of this.
Adopted by
Most recently taken up by
- jskswamy/skillstheir own version, first seen Nov 8, 2026
- KadirHarmanc/nazar-skilltheir own version, first seen Nov 8, 2026
- AsiaOstrich/EngramGraphtheir own version, first seen Nov 8, 2026
- Ubuntu-Buddha/claude-code-stranger-dangertheir own version, first seen Nov 8, 2026
- cfgaudit/cfgaudittheir own version, first seen Nov 6, 2026
- buildomator/buildomatortheir own version, first seen Nov 4, 2026
Used with
Projects with it also use coverage, metrics and 9 more.
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.
PydanticSkillcoverage
Fetch coverage diff from Codecov for the current branch or a specific PR. Shows uncovered lines, patch coverage, and overall coverage change.
Also in 4 projects that use this
GoogleSkillmetrics
Expertise in analyzing time-series repository health metrics, investigating root causes, and proposing proactive workflow improvements.
Also in 3 projects that use this
MicrosoftSkillreport
Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.
Also in 5 projects that use this
anombyte93Skilldiscover
Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.
Also in 3 projects that use this
Google CloudSkillfix
Plan a remediation strategy after a test failure.
Also in 3 projects that use this
MicrosoftSkillinit
Also in 3 projects that use this
Other versions35 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 35
- andrew-shwetzer/career-ops-plugin★ 501same name
- andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-★ 500same name
- cwinvestments/memstack★ 425same name
- buildomator/buildomator★ 102same name
- AsiaOstrich/universal-dev-standards★ 84same name
- mbwsims/claude-universe★ 71same name
- ratomirjovanovic/pandaward★ 50same name
- fivetaku/tikeytaka★ 40same name
- cfgaudit/cfgaudit★ 12same name
- thatmike1/claude-skills★ 10same name
25 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- captureSkill
- capture-to-inboxSkill
- escalate-to-architectSkill
- file-noteSkill
- interview-meSkill
- janitorSkill
- migrateSkill
- process-inboxSkill
- recallSkill
- resumeSkill
- selftestSkill
- taskSkill
- weekly-reviewSkill
- learn-acceleratorSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 32 edited versions we read keep these.
1
Distinctive
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
- Distinctive: line 28
If you can't read it, or two types fit → ask, don't guess.
- Very specific: line 36
Exactly ONE inbox: ALWAYS resolve it with python $MYOS_ENGINES/myos_paths.py get inbox — never hardcode, never invent Vault/Inbox or any …
“Common” is measured: kept by at least 6 in 10 of the 32 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.
Files
scan
The single front door for an image. Classify → confirm → route. One image in, the
right destination out — no wandering, no misfiling. Mirrors the bare-image behaviour in
the agent's persona (when the user just drops a photo with no words), and is the //scan command.
Procedure
- Read the image (vision model) and classify it into ONE of:
- handwritten notes / printed document / homework / curriculum → a clean note in the one Inbox (below).
- a type with its own pipeline (a receipt, a book cover, …) → that pipeline's tool, if one is installed. If none is, treat it as a document.
- a GIF / meme / reaction → it's a vibe, not a task. React in kind; don't file it.
- State your read and the action, and wait for a quick confirm ("Looks like lecture notes on recursion — transcribe to the Inbox? [y]"). Only act after the user confirms. If you can't read it, or two types fit → ask, don't guess.
- Route on confirm:
- notes/doc/homework → OCR/transcribe it, lightly clean errors but keep the user's wording,
then write to the inbox with
write_file:<inbox>/<title>.mdwhere<inbox>=python $MYOS_ENGINES/myos_paths.py get inbox.
- notes/doc/homework → OCR/transcribe it, lightly clean errors but keep the user's wording,
then write to the inbox with
- Verify the artifact exists and report the real path. Never say "filed" without it.
Pitfalls
- Exactly ONE inbox. ALWAYS resolve it with
python $MYOS_ENGINES/myos_paths.py get inbox— never hardcode, never inventVault/Inboxor any otherInbox. Writing a second inbox is the exact bug this exists to prevent (and the janitor flags it as CRITICAL). - No Dataview / Templater in a filed note — knowledge notes must read fine as plain markdown (a small model writing query blocks it doesn't understand = an unreadable note).
- Don't rewrite or "improve" the user's notes — transcribe + clean OCR only, preserve voice.
- Confirm first. A wrong guess that acts is worse than a one-line "is this X?".
Verification
- A new
<inbox>/<title>.mdexists (plain markdown, no Dataview), and the reply quotes its real path. - A routed type: the downstream tool's own ✅ line, relayed verbatim.
Cadence
On demand — any image the user sends, or //scan.
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
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.

