rpw-agent-marketplace

Use when drafting release notes or a changelog for this marketplace — "draft the release notes", "what changed since the last release", "write the changelog", "generate the release-log entry". Mines squash-merged PR titles/bodies + linked issues between the last v-tag and HEAD and renders the docs/release-log.md entry plus a PR/release description, shaped to this repo's calendar-first release flow (ADR-001).

House conventions for reviewing a diff/PR and preparing a PR for merge in this repo. Use when the user says "prep this PR", "review this diff", "review this PR", "ready to merge?", "is this mergeable?", or before opening/landing a PR. Carries the repo-specific review checklist and PR-body shape; defers review *mechanics* to the built-in /code-review, /review, and /security-review commands.

Configure Cursor with the /build command from rpw-published. Use when setting up Cursor to use the build workflow, or when the user asks to add/configure the build command in Cursor.

Build and deploy Databricks Apps using the bash-over-REST starter template. Use when scaffolding, configuring, deploying, or iterating on Databricks Apps with Lakebase connectivity.

Define, deploy, run, and debug Databricks Jobs the house way — DABs-defined (never UI-created), profile-based auth only (no PATs), with CLI log reading for the local-repro debugging loop. Use when creating or editing a Databricks job, wiring a job into a Databricks Asset Bundle (`databricks.yml`), scheduling a notebook/Python/dbt task, running a job from the CLI, or debugging a failed job run (reading run output, task logs, or `run-now` results).

Create, configure, and query Databricks Model Serving endpoints, and route every in-code LLM call through Model Serving (the `ChatDatabricks` / Model-Serving-first convention) instead of a provider SDK. Use when creating or configuring a serving endpoint, querying an endpoint, choosing how Python code should call an LLM, wiring auth passthrough for a deployed agent, or debugging the ambiguous-host-profile crash (`Use --profile to specify which profile to use` / `401 Credential was not sent`).

Classify Databricks Unity Catalog (UC) connections as MCP-native vs HTTP-proxy and pick the right one for a given MCP server. Use when wiring a UC connection into an MCP server, creating a new MCP server that needs Databricks auth, troubleshooting "Session terminated" or 32600 errors from `uc-mcp-proxy`, or deciding which UC connection name to point at on a workspace where multiple connections target the same upstream service.

Formatting and voice rules for authoring or editing Google Docs and customer-facing prose. Trigger on "write this up as a customer doc", "draft a gdoc", "format this doc", "email-style formatting", or editing any Google Doc tab or outbound customer write-up. Encodes email/technical-note structure (real headings, dashed bullets, bold scan-targets, inline code, functional emojis), customer-doc voice, pain-avoided framing, and render gotchas. NOT for plain code docs, READMEs, or code comments.

Read, create, edit, and extract from binary Office/PDF files (.pdf, .docx, .xlsx, .pptx) using open-source Python libraries. Trigger on "fill in this xlsx", "extract tables from this PDF", "draft a docx", "edit this Word doc", "build a pptx/slide deck", "read this spreadsheet", "pull text from a PDF", or any request to produce or parse an offline office document. NOT for Google-native Docs/Sheets/Slides (use the google-docs MCP) or plain-text/markdown.

Reusable APP_ENV env-file pattern for local development. Commit template.env, keep dev/test/prod env files local-only, and load the selected file at app startup.

HUMAN to-do list / personal task management — canonical operating model for the human's work backlog. Use when setting up the human's task-tracking repo, selecting or creating the GitHub repository for tasks, resuming a repo this skill already manages, updating task status, handing off work between sessions, or triaging the backlog.

Use when filing a bug, feature request, docs gap, or friction report AGAINST the rpw-agent-marketplace itself — its plugins, skills, commands, or MCP servers (not the user's own projects). Trigger on "file a bug about this plugin / the marketplace", "report feedback on rpw", "this MCP tool is broken", or the /feedback command. Resolves the target repo, classifies the report, applies house labels, and drafts the issue in the standard body shape.

End-to-end MCP server setup — diagnoses servers, bootstraps gcloud + databricks CLIs, authenticates both the UC-connections workspace and the user's own secrets workspace, and writes reference-based config that resolves credentials at startup. No secrets stored on disk unless the user explicitly opts out of Databricks.

Use when creating or modifying MCP servers in this repo. Enforces secret-free configs, uv/uvx entrypoints, and the APP_ENV / template.env credential-loading pattern.

Use when setting up Python projects, installing packages, running Python scripts, or managing dependencies - enforces UV package manager workflow with automatic virtual environment handling, replacing pip and manual venv management

Use when building Raycast extensions, especially with Python/uv dependencies, encountering venv corruption, authentication issues, or path race conditions - provides critical patterns from production fixes including .gitignore, lazy initialization, and validation

One-command post-merge close-out for an approved PR. Trigger on "ship it", "land this PR", "close out PR

Formatting rules for composing Slack messages so they render correctly (mrkdwn, not Markdown). Trigger on "post this to Slack", "format this for Slack", "send a Slack message", "reply in the thread", or before any slack_chat_post_message call. Covers mrkdwn vs Markdown, code blocks, link `<url|label>` and mention `<@Uxxx>`/`<#Cxxx>` syntax, no-Markdown-tables, and thread-vs-channel etiquette. NOT for email or Google Docs (use doc-styling); NOT for choosing which channel/thread to target.

Naming conventions, dispatch templates, and guardrails for spawning subagents — both Build Workers inside /build and ad-hoc research/debug/minion dispatch outside it. Use when dispatching an Agent, deciding whether a request should fan out to subagents, or picking a subagent model. Trigger on "dispatch a worker/agent", "research X" / "compare X vs Y" (multi-source), "why is X broken?" / "debug this", or a bounded minion task (issue creation, renames, metadata updates).

Use to file a GitHub issue and kick off a fresh Superset workspace with a Claude agent, dispatch an existing issue as the next task, or manage workspaces locally — rename, delete/clean up, or self-terminate a finished one. Trigger on "file a github issue and kickoff a workspace", "spin up a superset workspace to fix X", "dispatch the next task", "delegate this to a fresh agent", "rename this workspace", "delete this workspace", "clean up my workspace", or "kill this workspace when done".

Use when debugging a failure, diagnosing a bug, or when the user says "debug this", "why is X failing", "this is broken", "it errors", or reports something not working. Hypothesis-driven loop whose hard rule is to reproduce the failure locally BEFORE asking the user to retest. Pairs with tdd for locking the fix in with a regression test.

Use when writing tests first, doing test-driven development, or when the user says "write tests first", "this test should fail", "red-green", "TDD", or "add a failing test before the fix". House RED-GREEN-REFACTOR loop with this repo's test invocations and gates. Pairs with systematic-debugging for the fix side.

Use when setting up versioning for a project, comparing versions between components, or implementing version checks. Enforces git-hash-based versioning standard across all projects.

This skill should be used to create a visual explanation of a concept as a styled Mermaid diagram. Trigger on phrases like "visualize X", "make a diagram of Y", "explain Z visually", "draw the architecture of W", "show me how X works", or when a multi-noun concept would be clearer with a picture than prose. Outputs a self-contained SVG using the canonical Mono Bold theme — pure white canvas, full black text, 1.25px borders, tri-color gradient fills with neon glow on highlighted nodes.

Supervise a multi-issue wave — batch-dispatch backlog issues to parallel workers in superset workspaces, monitor liveness, serialize merges through a wave branch, and report until the list or backlog is done. Trigger on "run a wave", "dispatch a wave of issues", "batch-dispatch these issues", "work the backlog in parallel", "run through the backlog", "supervise the wave", "merge the wave back". NOT for a single issue (superset-launch) or subagent fan-out in one task (subagent-dispatch).