bulletjournal:init
Initialize bulletjournal plugin settings for this vault. Use when the user says "init bulletjournal", "setup bulletjournal", "configure bulletjournal", or "/bulletjournal:init". Writes .claude/bulletjournal.local.md with vault paths and tool paths so other bulletjournal skills work without hardcoded values.
What this skill does
# bulletjournal:init Write `.claude/bulletjournal.local.md` with vault layout and integration paths. Run once per vault. All other bulletjournal skills read this file — without it they fall back to conventional defaults (which work for standard Obsidian PARA vaults). ## Arguments | Flag | Description | Default | |------|-------------|---------| | `--daily PATH` | Prefix for daily notes | `daily` | | `--journal PATH` | Prefix for journal notes | `journal` | | `--templates PATH` | Obsidian templates folder | `Templates` | | `--projects PATH` | Projects folder | `10-Projects` | | `--inbox PATH` | Inbox folder | `00-Inbox` | | `--areas PATH` | Areas folder | `20-Areas` | | `--resources PATH` | Resources folder | `30-Resources` | | `--archive PATH` | Archive folder | `40-Archive` | | `--openclaw PATH` | Absolute path to OpenClaw workspace | (none — skips OpenClaw integration) | | `--qmd PATH` | Path to qmd CLI binary | auto-detect | ## Steps ### 1. Parse arguments Extract any `--flag value` pairs from the invocation arguments. Store as variables alongside defaults: ``` daily_path = --daily or "daily" journal_path = --journal or "journal" templates_path = --templates or "Templates" projects_path = --projects or "10-Projects" inbox_path = --inbox or "00-Inbox" areas_path = --areas or "20-Areas" resources_path = --resources or "30-Resources" archive_path = --archive or "40-Archive" openclaw_ws = --openclaw or "" qmd_bin = --qmd or (auto-detect in step 2) ``` ### 2. Auto-detect qmd binary Run: ```bash which qmd 2>/dev/null || find "$HOME/.local" "$HOME/.mise" /usr/local -name 'qmd' -type f 2>/dev/null | head -1 ``` If `which qmd` succeeds, set `qmd_bin = "qmd"`. If find locates it, use that full path. If neither finds it, set `qmd_bin = "qmd"` and note it may need to be set manually. ### 3. Check for existing settings ```bash cat .claude/bulletjournal.local.md 2>/dev/null ``` If the file exists, display its current content and ask: > "Settings already exist. Overwrite? (yes/no)" Stop if the user says no. ### 4. Prompt for missing values If `--openclaw` was not provided, ask: > "OpenClaw workspace path? (leave blank to skip OpenClaw integration)" Accept the user's answer. If blank, `openclaw_ws` remains empty. ### 5. Show proposed configuration Display all values before writing: ``` Setting Value ------------------- ---------------------------------------- daily_path daily journal_path journal templates_path Templates projects_path 10-Projects inbox_path 00-Inbox areas_path 20-Areas resources_path 30-Resources archive_path 40-Archive qmd_bin qmd openclaw_workspace /path/to/openclawy/workspace ``` Ask: "Write these settings? (yes/no)" Stop if the user says no. ### 6. Write settings file Create `.claude/` directory if needed: ```bash mkdir -p .claude ``` Write `.claude/bulletjournal.local.md` using the confirmed values: ```markdown --- daily_path: daily journal_path: journal templates_path: Templates projects_path: 10-Projects inbox_path: 00-Inbox areas_path: 20-Areas resources_path: 30-Resources archive_path: 40-Archive qmd_bin: qmd openclaw_workspace: "" --- # bulletjournal settings Vault-specific configuration for the bulletjournal plugin. Edit paths to match your Obsidian vault layout. Changes take effect immediately for skills (no Claude Code restart needed). ``` Substitute the actual confirmed values for each field. If `openclaw_workspace` is empty, write `openclaw_workspace: ""`. ### 7. Update .gitignore ```bash grep -q '\.claude/\*\.local\.md' .gitignore 2>/dev/null || echo '.claude/*.local.md' >> .gitignore ``` ### 8. Confirm ``` bulletjournal settings written → .claude/bulletjournal.local.md ``` If qmd was not found in step 2, add a note: ``` ⚠ qmd not found on PATH — set qmd_bin manually in .claude/bulletjournal.local.md ```
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.