obsidian
Skill9 starsChanged 5 months agoMITView on GitHub
Ingest an Obsidian/markdown note into a structured notes file in notes/
101 other projects use a version of this.
Adopted by
Most recently taken up by
- lx-wnk/skillstheir own version, first seen Nov 16, 2026
- thegovind/skillstheir own version, first seen Nov 16, 2026
- zkManuel0123/CodexClawtheir own version, first seen Nov 16, 2026
- chuckplayer/claude-agent-packtheir own version, first seen Nov 16, 2026
- rodos4312/Meu-Agenttheir own version, first seen Nov 15, 2026
- metaspartan/cybaratheir own version, first seen Nov 15, 2026
Used with
Projects with it also use taskflow-inbox-triage, discord-e2e and 10 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.
AtomicBot-aiSkilltaskflow-inbox-triage
Also in 6 projects that use this
molt-botSkilldiscord-e2e
Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and Gateway evidence from manual user interactions.
Also in 10 projects that use this
molt-botSkillopenclaw-repair-sweep
Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.
Also in 10 projects that use this
clawdbotSkillopenclaw-performance
Performance work in OpenClaw: a slow or heavy flow (latency, CPU, memory, SQL, RPC, renders), writing or reviewing a perf PR, or adding a cache. Count the work, delete waste first, cache last.
Also in 7 projects that use this
clawdbotSkillplugin-sdk-impact
Count Plugin SDK consumers across live ClawHub releases and bundled OpenClaw plugins before deprecation, removal, or behavior changes; supports public release-date filters.
Also in 7 projects that use this
emanueleieloSkillsonos
Control Sonos speakers: discover, play/pause, volume, grouping, favorites, and queue management via sonos CLI.
Also in 5 projects that use this
- +2 more from molt-bot
Other versions101 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 101
- openclaw/openclaw★ 395ksame name
- moltbot/clawdbot★ 394ksame name
- steipete/warelay★ 394ksame name
- steipete/clawdis★ 394ksame name
- moltbot/moltbot★ 394ksame name
- clawdbot/clawdbot★ 394ksame name
- molt-bot/clawdbot★ 391ksame name
- NousResearch/hermes-agent★ 264ksame name
- spinabot/brigade★ 11ksame name
- steipete/agent-scripts★ 7.5ksame name
91 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.
- .claude/AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- alphaxivSkill
- askSkill
- autoexploreSkill
- collateSkill
- curriculumSkill
- editSkill
- goalSkill
- notionSkill
- retrieveSkill
- tutorSkill
- webSkill
- zoteroSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 4 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 96 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
If $ARGUMENTS is empty, ask the user for a file path, then continue.
- Very specific: line 14
All output is under notes/ (personal notes, as opposed to objective sources under sources/).
- Very specific: line 21
Extract: Read the note at $ARGUMENTS with the Read tool.
- Distinctive: line 50
Before writing, verify the envelope:
- Distinctive: line 59
If any check fails, fix the envelope before writing.
- Distinctive: line 66
Propose: After writing, suggest the user:
- Very specific: line 67
Run /retrieve <topic> to find related sources and existing pages.
- Very specific: line 68
Run /collate <topic> to synthesise a paper or concept page from this note together with other sources on the same topic.
“Common” is measured: kept by at least 6 in 10 of the 96 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
Ingest an Obsidian note at $ARGUMENTS and produce a structured
notes/obsidian_<slug>.md file following the project template.
If $ARGUMENTS is empty, ask the user for a file path, then continue.
Layout
All output is under notes/ (personal notes, as opposed to
objective sources under sources/). Template lives at
.claude/Templates/note.md. Existing files in notes/ are
style references — read one before writing your first output.
Steps
- Extract. Read the note at $ARGUMENTS with the
Readtool. Identify:- The H1 (
# ...) line as thetitle. If absent, fall back to the filename stem with underscores/dashes converted to spaces, in Title Case. [[wikilinks]]and#tags— leave them in place inside the body. The navigator uses[[wikilinks]]as graph edges, so they must be preserved verbatim.- Concepts list: collect the target of each
[[wikilink]](the part before|if aliased, trimmed) plus each#tagname (strip the leading#). Dedup at exact-string level, preserve first-occurrence order. This becomes theconcepts_mentionedfield.
- The H1 (
Format. Fill in the obsidian schema below. This skill extends the shared
.claude/Templates/note.mdwithsource_links(a list) andconcepts_mentioned; the schema here is authoritative for obsidian notes.type: obsidian_notetitle: from Step 1source_links: a YAML block list containing $ARGUMENTS verbatim as its single entry:source_links: - $ARGUMENTSconcepts_mentioned: an inline YAML list of the concepts collected in Step 1 (e.g.[chain-of-thought, tool-use, transformers]). Use[]if the note has no[[wikilinks]]or#tags.## Content: the full note text. Preserve the author's wording, headings, lists, code blocks, emphasis,[[wikilinks]], and#tagsas faithfully as possible. Do not summarise unless the note is very long.
Before writing, verify the envelope:
- Starts with
---on line 1; has a closing---delimiter. - Contains exactly these four frontmatter keys:
type,title,source_links,concepts_mentioned. typeis the literal stringobsidian_note.source_linksis a YAML list whose only entry equals $ARGUMENTS verbatim.concepts_mentionedis a YAML list (possibly empty).- Body contains a non-empty
## Contentsection.
If any check fails, fix the envelope before writing.
- Write. Slugify the title to snake_case (lowercase, spaces/dashes →
underscores, drop non-alphanumeric characters). Write to
notes/obsidian_<slug>.mdwith theWritetool. If the file already exists, ask the user before overwriting. - Propose. After writing, suggest the user:
- Run
/retrieve <topic>to find related sources and existing pages. - Run
/collate <topic>to synthesise a paper or concept page from this note together with other sources on the same topic.
- Run
Wrap up
Report: output file path, the title and wikilinks/tags preserved, and anything skipped (one-line reason each).
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.

