Weekly digest

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Create and edit Obsidian Bases (.base files): database-like views of your notes with filters, formulas, summaries and table, cards, list or map views. Part of kepano/obsidian-skills.

Lets agents drive a running Obsidian app through the official Obsidian CLI: read, create, append to and search notes, manage tasks and properties, and reload plugins, run JavaScript or capture errors while developing plugins and themes.

Teaches agents to write valid Obsidian Flavored Markdown: wikilinks, embeds, callouts, properties (frontmatter), block IDs and comments, on top of standard CommonMark and GFM. From the official kepano/obsidian-skills set.

Use the Defuddle CLI to turn a web page into clean Markdown, stripping navigation, ads and clutter so agents spend fewer tokens than with a raw web fetch. Part of kepano/obsidian-skills.

Create and edit JSON Canvas (.canvas) files for Obsidian: nodes, edges, groups and connections for mind maps, flowcharts and visual boards, following JSON Canvas Spec 1.0.

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when you have a spec or requirements for a multi-step task, before touching code

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when implementing any feature or bugfix, before writing implementation code

Use when executing implementation plans with independent tasks in the current session

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Writing, explore — mine raw fragments, no structure yet.

Writing, exploit — shape raw material into an article, paragraph by paragraph.

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

Writing, exploit — assemble raw material into a journey of beats, grounding each term before a beat leans on it.

Teach the user a new skill or concept, within this workspace.

Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.

Implement a piece of work based on a spec or set of tickets.