Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Add or edit a lerd service preset (database, cache, search engine, admin dashboard) as YAML in the lerd-services store. Use whenever the task is to add a new service, a new version of a service, or wire a service into projects — never add services in Go.
Draft and open a pull request the lerd way — issue-first, correct issue linking, human prose, none of the banned sections. Use when asked to open, prepare, or draft a PR for lerd. Never creates anything on GitHub without explicit per-action approval.
Guides using eRPC (electron-tRPC) for inter-process communication (IPC) between Electron main and renderer processes. Triggered when handling Electron IPC or tRPC-based systems.
Analyze downstream impact of dbt model changes using column-level lineage and the dependency graph. Use when evaluating the blast radius of a change before shipping. Powered by altimate-dbt.
REQUIRED before writing or modifying ANY dbt model. Invoke this skill FIRST whenever a task says "create", "build", "add", "modify", "update", "fix", or "refactor" a dbt model, staging file, mart, incremental, or snapshot. Skipping this skill is the leading cause of silent-correctness bugs — models that compile and `dbt build` cleanly but produce wrong values. It contains the patterns that prevent the most common such bugs encountered in real dbt projects: • Incremental high-water marks (`>=` vs `>` ties → silent row dropout) • Snapshot strategy selection (timestamp vs check, `unique_key` choice) • `LEFT JOIN + COUNT(*)` phantom rows from unmatched parents • Type harmonization in `COALESCE` / `CASE` / `UNION` legs • Date-spine completeness (every period present, even empty ones) • Off-by-one window boundaries (`BETWEEN d - (N-1) AND d` for N-wide) • Uniqueness enforcement when schema implies a key • Window-function `LIMIT` with deterministic tiebreaker • Verifying transformation correctness with dbt unit tests, not just `dbt build` • Enumerating every requested deliverable and checking each exists on disk Do not start writing SQL until this skill is loaded. Powered by altimate-dbt.
Compare column-level lineage between two versions of a SQL query to show added, removed, and changed data flow edges.
Write, edit, or debug JavaScript that uses the Note Toolbar `ntb` API inside Obsidian. Use this skill whenever the user wants to script a toolbar item, use ntb.prompt / ntb.suggester / ntb.fileSuggester / ntb.menu / ntb.modal, read or write note properties via ntb.getProperty / ntb.setProperty, work with toolbar items via ntb.getItem / ntb.getToolbars, or combine the ntb API with Dataview JS, JS Engine, or Templater. Also trigger for any script that references `ntb`, `NtbSuggester`, or 'Note Toolbar API'.
Translate SQL queries between database dialects (Snowflake, BigQuery, PostgreSQL, MySQL, etc.)