
Interact with an Obsidian vault via the Obsidian CLI. Use when the user asks to read, search, create, update, or inspect notes, daily notes, links, tasks, tags, or other vault content from the terminal.
Use when coordinating multi-iteration work with explicit `_working/{TOPIC}/` handoffs, binary sprint contracts, and independent reviewer gating after implementation.
Periodically maintain a shallow PARA workspace using specialised sub-agents. The skill surveys the repo, classifies files into PARA containers, distils atomic notes using the CODE method, and safely proposes or applies maintenance actions.
Analyse several example projects to synthesise a reusable coding fingerprint. Use when the user wants to capture a person's coding style, engineering principles, project-shaping preferences, architectural tendencies, or implementation habits so agents can reproduce them consistently.
Query and tidy Clockify time entries using the Clockify REST API via `curl`, authenticated with the 1Password CLI.
Wait for a GitHub Actions run to finish with minimal terminal output and a reliable exit code. Use when an agent must wait for CI to pass (e.g. after push, after opening a PR, or when verifying a specific run). Prefer gh run watch with --exit-status and --compact to avoid flooding context with poll output.
When generating or editing markdown content, actively look for existing pages to link to and incorporate relevant wikilinks so content is interconnected. Use when writing notes, docs, or any .md content.
Write, refactor, and review code in Michael's style; explicit contracts, thin entrypoints, practical boundaries, anti-ceremony abstractions, deterministic tooling, and architecture that scales from function internals to repository shape.
Use when handling multi-step tasks, investigations, or long sessions where working notes, interim findings, and scratch planning are needed to keep context and handoffs clear.
Query a structured repository knowledge base intelligently using ontology-aware routing, manifests, indexes, metadata, shortlist-based retrieval, and bounded deep reads. Prefer navigation and recognition over blind grep.
Adds a summary callout at the start of markdown notes using the format `> [!summary]`. Use when creating or editing markdown notes, docs, or knowledge-base content that should open with a concise overview.
Use when drafting, editing, or evaluating communication that should sound like Michael across public technical prose, internal notes, agent prompts, engineering feedback, and concise operational updates.
Design, implement, and refactor high-quality Temporal workflows and activities in Python. Use when building or changing Temporal Python applications; when designing activities (injectable deps, Pydantic params/result, business logic outside); when implementing workflows with dynamic inputs or Continue-As-New; or when configuring reliability (timeouts, retries, idempotency), determinism, or testing. Covers boundaries, typed contracts, bounded history, and progressive disclosure via resources.
Use when an Obsidian meeting note includes audio recording embeds and needs source-grounded minutes, chapters, and a polished diarised transcript written back into the note.