Notre avis
Crée des notes dans le coffre Obsidian en respectant des conventions strictes de métadonnées, de taxonomie, de placement et de formatage pour maintenir une base de connaissances structurée.
Points forts
- Assure une cohérence uniforme entre toutes les notes du coffre.
- Impose une taxonomie contrôlée, évitant les tags inventés.
- Intègre des vérifications pré-écriture via l'interface en ligne de commande Obsidian pour améliorer les liens et le placement.
- Définit des règles claires pour les tables des matières et les appels Obsidian.
Limites
- Nécessite qu'Obsidian soit en cours d'exécution pour les vérifications CLI complètes.
- La taxonomie rigide peut ne pas convenir à des sujets très spécialisés.
- Suppose que l'utilisateur suive les conventions à la lettre, ce qui peut être contraignant.
Lors de l'ajout d'une nouvelle note à un coffre Obsidian suivant un schéma organisationnel et une taxonomie spécifiques.
Pour une note rapide et informelle sans souci de structure, ou lorsque le sujet ne correspond pas à la taxonomie définie.
Analyse de sécurité
SûrThe skill instructs non-destructive shell commands (obsidian CLI for search, backlinks, file listing) with fallback to Glob/Grep. No sensitive data exfiltration, no disabling of safety features, no execution of remote or obfuscated payloads. The use of Bash is limited to these harmless operations.
Aucun point d'attention détecté
Exemples
Create a new research note on the topic of AI agents for marketing, dated today, with status active. Place it in the Research folder for this month.Add a project note for the new website redesign project in the Projects folder, with tags [business, plan], and include a TOC if it has more than 3 sections.Create a reference note for a PDF about competitive analysis, placed in References/, with tags [research, business], and set status to active.name: vault-note description: Create Obsidian vault notes with correct frontmatter, taxonomy, and formatting conventions allowed-tools: "Bash Read Write Edit Glob Grep"
Vault Note
Create notes for Kyle's Obsidian vault following all established conventions.
Frontmatter
Every note must include:
---
date: YYYY-MM-DD
tags:
- <tag>
status: active | archive
aliases: []
---
dateis the creation or last-major-edit datetagsmust include at least one from the taxonomystatusisactivefor current notes,archivefor completed/retiredaliasescan be empty[]but the field must exist
Tag Taxonomy
Use only these tags: ai, tools, business, marketing, career, finance, strategy, plan, architecture, review, playbook, research, delightful, github, braze, rosetta, clipping, briefing, meta, audit
If a note doesn't fit cleanly, use the closest match. Don't invent new tags.
Placement Rules
| Content type | Location |
|---|---|
| Formal research — /research output or Kyle-authored | Research/<Month YYYY>/ |
| Research-adjacent deliverables staging (not from /research) | Claude/Findings/<Month YYYY>/ |
| Active project work | Projects/<project-name>/ |
| Clippings, PDFs, external material | References/ |
| Topic synthesis pages (wiki) | Wiki/ |
| Completed/retired notes | Archive/ (set status: archive) |
Table of Contents
Notes with 4 or more ## sections must include a numbered TOC after the frontmatter using [[#Section]] wiki-links. Do NOT put numbers in section headers — numbering belongs in the TOC list only.
Pre-Write Vault Check (CLI)
Before writing a note, use the Obsidian CLI to improve placement and linking (requires Obsidian running — skip if unavailable):
- Find linking candidates —
obsidian search query="<topic keywords>" limit=10to discover notes worth wiki-linking - Check for orphans —
obsidian backlinks file="<similar note>"to see what links into related content and mirror those patterns - Verify placement —
obsidian files folder="<target folder>"to confirm the destination folder exists and see sibling notes
Fall back to Glob/Grep if the CLI is unavailable.
- Wiki relevance — If the note is tagged
research, checkWiki/for a topic page that should link to this note. Flag it for the user if a wiki update seems warranted. Do not auto-edit wiki pages from vault-note — that's the research skill's job or a manual session.
Formatting Conventions
- Monolithic notes. Notes are long-form and heavily cross-referenced. Don't atomize.
- Wiki-links are organic. Use
[[note name]]and[[note name#section]]inline where contextually relevant. No forced## Relatedappendix sections. - Obsidian callouts. Use
[!note],[!tip],[!warning],[!danger],[!info],[!success],[!question],[!quote]sparingly — 1–3 per note max. - Footnotes for sources. Prefer footnotes over inline URLs when a sentence references a source.[^1] Inline URLs are fine in lists or when the link IS the content.
- No inline
#tagsin runner/automated output. Inline tags are welcome in conversational notes. - Block quotes from previous outputs. When continuing or contradicting a previous note, pull it in with a wiki-linked block quote:
From [[AI Briefing — 2026-02-27#News]]: Content from that note...
- No loose files in vault root. Everything has a home.
Priorisation de Tâches
Productivite
Priorise vos tâches avec les frameworks Eisenhower, ICE et RICE.
Generateur de Rapport Hebdomadaire
Productivite
Generez des rapports de statut hebdomadaires structures et concis.
Rapport de Daily Standup
Productivite
Génère des rapports de daily standup structurés et concis.