agentleFS
c-ibarrac-ibarra/ObsidianKnowledgeCurator/.agents/skills/notion-curator/SKILL.md

notion-curator

Skill0 starsChanged 45 days agoMITView on GitHub

Use this skill when the user wants to curate, import, or migrate folders or files imported from Notion into the structured zones (raw and wiki) of the Obsidian vault. Triggers include "import Notion folder", "curate Notion imported files", "process new Notion material", "migrate Notion folder", "curate Notion import".

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

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

    Vault Directory Permissions: Ensure the agent has read/write permission to the Obsidian folder.

    line 12
  2. Very specific:

    Avoid shell commands: Never use shell commands (find, mkdir, mv, cat) since they always trigger manual user approval prompts.

    line 13
  3. Distinctive:

    Read the contents of the target Notion directory to locate imported markdown files:

    line 16
  4. Very specific:

    Read original note: Use native view_file to read the content keylessly.

    line 24
  5. Distinctive:

    Reformat to zero-YAML standard: Use the cognitive LLM context to convert it:

    line 25
  6. Very specific:

    Create or update files under <RootFolder>/wiki/<ConceptName>.md (PascalCase, e.g.

    line 44
  7. Distinctive:

    NEVER use YAML frontmatter.

    line 56
  8. Very specific:

    NEVER use emojis outside of ## 📌 Key Takeaways.

    line 57
  9. Distinctive:

    Use native filesystem tools exclusively to prevent authorization prompts.

    line 59

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

Notion Curator Skill

Goal

Natively read, reformat, and migrate imported Notion markdown files into the structured vault zones (raw/ and wiki/) completely keylessly using native cognitive context and without triggering authorization prompts by utilizing native file tools.

Prerequisites

  • Vault Directory Permissions: Ensure the agent has read/write permission to the Obsidian folder.
  • Avoid shell commands: Never use shell commands (find, mkdir, mv, cat) since they always trigger manual user approval prompts. Use native view_file and write_to_file tools.

Step 1 — Scan source folder

Read the contents of the target Notion directory to locate imported markdown files:

# Check files inside target Notion directory
# (Use native file listing/view tools if available, or a single non-interactive file-read check)

Step 2 — Process and Curate notes (Zero-YAML Standard)

For each file in the Notion folder:

  1. Read original note: Use native view_file to read the content keylessly.
  2. Reformat to zero-YAML standard: Use the cognitive LLM context to convert it:
    • H1 Title at the top.
    • Metadata blockquote (Zero-YAML):
      > **Source:** Notion Course
      > **Author:** Carlos Ibarra · **Date:** May 2026
      > **Type:** course note
      > **Tags:** #no-read-yet
    • Key Takeaways section (## 📌 Key Takeaways) with bullet points and emojis.
    • Technical body with structured headers (## 1. Topic, ## 2. ...), preserving code blocks.
    • Flashcards section (## Flashcards): 1. **Q:** [Question]? → **A:** [Answer].
    • Glossary section (## Glossary): - **[Term]**: [Definition].
    • Related section (## Related) with suggested wikilinks.
  3. Write curated note: Save it under <RootFolder>/raw/<Course Name>/<Section>/<Note Name>.md using native write_to_file.

Step 3 — Compile concepts natively (Wiki)

For each processed note:

  1. Extract 3–5 core concepts using your cognitive LLM context.
  2. Create or update files under <RootFolder>/wiki/<ConceptName>.md (PascalCase, e.g. TargetEncoding) using write_to_file.
  3. Include deep synthesis and a Sources backlink section pointing to the raw note.

Step 4 — Update Master Plan

  1. Parse the metadata of all curated raw notes.
  2. Edit <VaultRoot>/<RootFolder>/Master Plan — <Course>.md directly using replace_file_content to rebuild its index table.

Step 5 — Move Original Files

Move the original Notion file to a processed/ directory:

  • Since moving files normally requires a shell command, batch the move operations or perform a native write of the file in the new location and delete the original using native tools, or request a single batch command approval at the end.

Constraints

  • NEVER use YAML frontmatter.
  • NEVER use emojis outside of ## 📌 Key Takeaways.
  • Maintain original language for course content.
  • Use native filesystem tools exclusively to prevent authorization prompts.

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.