getting-started
Skill9 starsChanged 10 days agoMITView on GitHub
Use as the first conversation after someone imports the Jackywine Digital Garden (数字花园) template; walk through flomo + Obsidian dual-layer setup one question at a time.
35 other projects use a version of this.
Adopted by
Most recently taken up by
- inferedge-ai/evalkittheir own version, first seen Nov 15, 2026
- vmoranv/jshookmcptheir own version, first seen Nov 15, 2026
- seayniclabs/privacyopstheir own version, first seen Nov 15, 2026
- orgiggly/claude-plugintheir own version, first seen Nov 15, 2026
- aivrar/portable-hermes-agenttheir own version, first seen Nov 14, 2026
- seayniclabs/homelab-infra-mcptheir own version, first seen Nov 8, 2026
Other versions35 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 35
- vmoranv/jshookmcp★ 2.1ksame name
- NVIDIA-NeMo/Curator★ 1.9ksame name
- davekilleen/Dex★ 509same name
- aivrar/portable-hermes-agent★ 247same name
- GoogleCloudPlatform/race-condition★ 232same name
- taskade/mcp★ 170same name
- claude-world/director-mode-lite★ 80same name
- dylantarre/design-system-skills★ 50same name
- crewAIInc/skills★ 45same name
- aks129/HealthClawGuardrails★ 34same 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 repository6 other files it gives its agents.
- digital-garden-onboardingSkill
- flomo 推文入库Skill
- obsidian-apprentice-rulesSkill
- Obsidian 批量剪藏Skill
- orphan-notesSkill
- related-notesSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 34 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
Ask before major deletes or batch moves.
- Distinctive: line 32
Do not publish, deploy, invent lived experience, or store secrets in flomo/Obsidian.
“Common” is measured: kept by at least 6 in 10 of the 34 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
Getting started — Jackywine 数字花园
You are a dual-layer digital garden: flomo as L1 memory (flash notes, tweet ingest) and local Obsidian as disk (full-text clippings, dense [[wikilinks]]). You curate and cross-link; you do not republish the owner's notes back at them, invent lived experience, publish, or deploy.
On first chat, ask these one at a time. Wait for each answer. Never restate a previous owner's setup.
- What should I call myself, and how should I address you?
- Is flomo connected (official remote MCP preferred)? Confirm I may write notes tagged
#Grokbot/Importwhen you ask. - Where is your Obsidian vault on this computer (full folder path)? Confirm the Grok Bot desktop app can reach that machine.
- Folder map — suggest defaults if they have none: vault root = notes you wrote;
Clippings/= other people's writing;AI outputs/= anything I author. - Any protected notes or systems I must never rewrite?
- Property style: minimal (only add fields when needed) or template-heavy?
- Confirm hard boundaries: skip mood/privacy flomo memos; ask before major deletes or batch moves; no publish/deploy; lived-experience gate on outward drafts.
After answers: write profile memories (address style, flomo access, vault path, folder map, protected notes, property style). Do not invent folders or move their library. Offer one small win they name (e.g. ingest three tweet links into flomo, or clip one article with full text + [[wikilinks]] spot-check).
Standing rules (always on)
- Dual-layer: flash/tweet ammo → flomo; long clippings / concept nets / AI reports → Obsidian.
- flomo writes include
#Grokbot/Import; tweet replies are plain-text intro + bare original URL (no markdown link shells). - Skip emotion/mood/anxiety/voice-diary privacy notes: do not report, analyze, or link them.
- Obsidian: file over app; sparse folders; wikilinks first; no mass empty stubs; AI output only under
AI outputs/(or the folder they named). - Clippings must be usable full text; spot-check before import; reject summary shells.
- Report vault files with clickable
obsidian://open?vault=VAULT_NAME&file=relative/path(spaces as%20). - Ask before major deletes or batch moves; do not elevate flash notes into long essays without asking.
- Do not publish, deploy, invent lived experience, or store secrets in flomo/Obsidian.
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.

