From utility
Install (if missing) and configure the obsidian-community/obsidian-kanban plugin in the user's Obsidian vault so its settings line up with the projects domain board format. Use when the user says "configure kanban", "set up obsidian-kanban", "install the kanban plugin", or wants project boards to render and behave correctly.
How this skill is triggered — by the user, by Claude, or both
Slash command
/utility:configure-obsidian-kanbanThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Get the [obsidian-community/obsidian-kanban](https://github.com/mgmeyers/obsidian-kanban) plugin
Get the obsidian-community/obsidian-kanban plugin
installed and tuned so the boards the projects domain writes (<slug>.kanban.md) render and behave
the way those skills assume. This is a one-shot setup task -- run it once per vault.
The contract this skill aligns to is BOARD-FORMAT.md:
@{YYYY-MM-DD} date tags, a **Complete** marker in Done, and the %% kanban:settings %% block.
Never commit in the vault. The user manages the vault's git separately. Write files, then stop -- do not stage or commit anything under the vault.
Find the vault root (the directory containing .obsidian/). The plugin lives at:
.obsidian/plugins/obsidian-kanban/
main.js
manifest.json
styles.css
If you can't find .obsidian/, ask the user for the vault path.
If .obsidian/plugins/obsidian-kanban/main.js is absent, install it:
https://api.github.com/repos/mgmeyers/obsidian-kanban/releases/latestmain.js, manifest.json, styles.css -- into
.obsidian/plugins/obsidian-kanban/ (create the directory first)."obsidian-kanban" to the array in
.obsidian/community-plugins.json (create the file as ["obsidian-kanban"] if it doesn't exist).
Read-modify-write -- don't clobber other enabled plugins.Tell the user the plugin won't load until Obsidian is reloaded (Cmd/Ctrl-R or restart). If it's
already installed, skip to configuration and note the installed version from manifest.json.
The plugin's global settings live in .obsidian/plugins/obsidian-kanban/data.json. Read-modify-write
-- merge these keys into whatever is there, leave unrecognised keys untouched, and don't overwrite a
setting the user has deliberately changed without flagging it.
| Setting | Value | Why it matters for the projects boards |
|---|---|---|
date-trigger | "@" | Matches the @{YYYY-MM-DD} deadline syntax in BOARD-FORMAT |
date-format | "YYYY-MM-DD" | The on-disk date format the project skills read and write |
date-display-format | "YYYY-MM-DD" | What the rendered card shows |
show-relative-date | true | Surfaces "in 3 days" on dated milestone cards |
link-date-to-daily-note | false | Deadlines are milestones, not journal day-links |
hide-date-in-title | false | Keep deadlines visible on the card face |
archive-with-date | true | Completed cards keep their date when auto-archived from Done |
show-checkboxes | true | Cards are checkboxes -- the readable-without-the-plugin format |
new-line-trigger | "enter" | Predictable card entry during manual edits |
If data.json doesn't exist, create it with exactly these keys.
The per-board %% kanban:settings %% block (written by /new-project) overrides globals per file.
Don't rewrite existing boards. Just confirm the global defaults above don't fight the board format --
the date trigger and format are the ones that must agree, and Step 3 sets them.
obsidian-kanban {installed vX.Y.Z | already present vX.Y.Z} and configured.
- Settings written:
.obsidian/plugins/obsidian-kanban/data.json- Date syntax aligned to
@{YYYY-MM-DD}Reload Obsidian to pick up changes, then open any
<slug>.kanban.mdto verify it renders as a board.
Do not commit -- the vault's git is the user's to manage.
npx claudepluginhub xxkeefer/skills --plugin utilityProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.