agentleFS
JackywineJackywine/jackywine-digital-garden-skills/skills/getting-started-2/SKILL.md

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

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
  1. Distinctive:

    Ask before major deletes or batch moves.

    line 31
  2. Distinctive:

    Do not publish, deploy, invent lived experience, or store secrets in flomo/Obsidian.

    line 32

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

  1. What should I call myself, and how should I address you?
  2. Is flomo connected (official remote MCP preferred)? Confirm I may write notes tagged #Grokbot/Import when you ask.
  3. Where is your Obsidian vault on this computer (full folder path)? Confirm the Grok Bot desktop app can reach that machine.
  4. Folder map — suggest defaults if they have none: vault root = notes you wrote; Clippings/ = other people's writing; AI outputs/ = anything I author.
  5. Any protected notes or systems I must never rewrite?
  6. Property style: minimal (only add fields when needed) or template-heavy?
  7. 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.

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.