Menu
File new knowledge into the Obsidian vault at the correct location with proper frontmatter and wiki-links.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Weekly backlog audit — field completeness, staleness tiers, and duplicate detection. Run during grooming to clean up the backlog.
Creates a JIRA Bug with steps to reproduce, expected/actual behavior, and fix criteria. Activates when users ask to create a bug report, file a bug, or report an issue.
Creates a JIRA Epic with scope, success criteria, and child story breakdown. Activates when users ask to create an epic.
Creates a JIRA Story with user story format, acceptance criteria, and technical notes. Activates when users ask to create a story or user story.
Creates a JIRA Task for tech debt, infrastructure, documentation, or spike work. Activates when users ask to create a task, spike, tech debt ticket, or infrastructure work.
Daily briefing — sprint progress, new tickets, and recent comments in one report. Run this to get oriented at the start of the day.
| name | vault-save |
| description | File new knowledge into the Obsidian vault at the correct location with proper frontmatter and wiki-links. |
| allowed-tools | ["mcp__obsidian__write_note","mcp__obsidian__search_notes","mcp__obsidian__read_note","mcp__obsidian__patch_note","mcp__obsidian__update_frontmatter"] |
| argument-hint | <topic or content> |
Create a new note in the Obsidian vault at the correct location, with proper frontmatter, wiki-links to related notes, and content written in the user's voice.
Determine what to save from the argument or conversation context. Ask the user to clarify if unclear.
Choose the correct vault location based on content type:
| Content Type | Location | Template Reference |
|---|---|---|
| Work technical learning | Work/Knowledge/ | Knowledge-Template |
| Personal technical learning | Personal/Knowledge/ | Knowledge-Template |
| Work project documentation | Work/Projects/[Project]/ | Work-Project-Template |
| Personal project documentation | Personal/Projects/ | Project-Template |
| Meeting notes | Work/Meetings/ | Meeting-Template |
| Technical design/decision | Work/Projects/[Project]/ | Technical-Doc-Template |
| Homelab/infrastructure | Personal/Projects/ | Project-Template |
If the location is ambiguous, ask the user.
Search for related notes using mcp__obsidian__search_notes with relevant terms. Identify 2-5 related notes to link to.
Create the note using mcp__obsidian__write_note:
date, type, tagsReport what was created:
[[Work Projects Hub]], [[Home Lab Hub]], etc.)Optionally update today's daily note #### Related Notes section to reference the new note. Only do this if the user is actively working in a daily note context (e.g., they ran /daily earlier in the session). Use mcp__obsidian__patch_note to add the wiki-link.
---
date: YYYY-MM-DD
type: knowledge | project | meeting | technical-doc
tags:
- relevant-tag
---
Kubernetes Pod Security Standards.md, not k8s-pod-security.md[[Work Projects Hub]], [[Quarterly Hub]], [[Home Lab Hub]]