agentleFS
Sign inStart free
prestariusprestarius/jet-skills-stack/skills/obsidian-note/SKILL.md

obsidian-note

Skill1 starsChanged 2 months agoMITView on GitHub

Generate a complete Obsidian note using Jet's frontmatter schema and section conventions. Use whenever the user wants a note for their vault, says "make an Obsidian note", "add this to my vault", or wants meeting/architecture/project notes captured. Notes from a Markdown source must be exhaustive, never summarized.

3 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

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Use fixed section headings appropriate to the note type.

    line 16
  2. Distinctive:

    Exhaustiveness rule: if the note is derived from a Markdown document or a transcript, capture the full content faithfully — do not shorten …

    line 17
  3. Distinctive:

    Never propose a starter vault.

    line 18

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

Produce a single .md note. Frontmatter (exact keys, fill all):

---
created: YYYY-MM-DD
tags: []
category:
status:
---
  • category and status use the vault's existing vocabulary if CONTEXT.md defines it; otherwise ask once.
  • Use fixed section headings appropriate to the note type; keep heading names consistent across notes.
  • Exhaustiveness rule: if the note is derived from a Markdown document or a transcript, capture the full content faithfully — do not shorten into a summary. Restructure for clarity, but lose nothing.
  • Never propose a starter vault. If a template/plugin is needed, suggest adding it as a single, separate step.

See references/frontmatter-schema.md for the schema rationale and assets/note.template.md for a blank template.

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.

Check your setup, free