
π―Skills1
πPlugins9
Invocation discipline and failure triage for running dbt β a static preflight script kills environment failures before the first command, invocation rules prevent the self-inflicted ones (sandboxed shells, piped output, silent empty selections), and a signature-indexed catalogue maps error strings to ranked causes and fixes, including dbt-fusion quirks. Bootstraps a committed per-project context file.
Forces the main thread to act as an orchestrator and delegate ALL work to subagents instead of doing it itself β plan, dispatch, verify with a separate agent, synthesize. Agent-neutral across Claude Code, Cursor, and Cortex Code.
Version-aware Prefect 3 guidance: a live docs-lookup protocol, CLI-first instance queries, and house standards. Prefect 2.x out of scope.
Take working-tree changes from branch to merged PR in one pass β branch off main, commit smart-git-commit style, open a PR, then squash-merge and delete the local and remote branch. Command-only: /ship asks before merging, /ship clean goes straight through. Detects unrelated changes and offers to split them into separate branches/PRs.
Implement a GitHub issue end-to-end: claim it, branch, code in small commits, run tests + a runtime smoke check, and open a draft PR β with explicit stop conditions instead of improvising.
Bootstrap a dlt ingestion project: install the dltHub AI Workbench project-scoped (only the toolkits the project needs), then layer Relentless Data house conventions (Snowflake, Prefect, DuckDB dev loop) as a committed always-on rule. Idempotent re-runs add new source types.
Produce a single self-contained HTML visual report β an explainer, writeup, or diagram-heavy document built with Tailwind and Mermaid via CDN plus hand-crafted CSS/SVG.
Groups changed files by affected area, creates one conventional commit per group, then pushes to remote β with safety rules against force-pushes, skipped hooks, and committed secrets.
Read-only Snowflake exploration via the snow CLI β schema discovery, profiling, hypothesis testing, and data-quality investigation. Bootstraps a committed per-project context; a guardrail wrapper hard-enforces read-only execution and stages user-requested DML/DDL as scripts for manual execution.