Shipping personal MCP servers and skills

Workflow for repos whose entire purpose is producing an MCP server or a skill for personal, cross-project use (not a library other code imports) — e.g. olx-polite-mcp, emag-polite-mcp, altex-polite-mcp, temu-polite-mcp, product-research-pipeline. Covers going from a working repo to "loadable by Claude Code in any project," and how that differs between the dev machine and everywhere else.

Per-repo dev loop

Every repo in this family takes repo-tasks as a dev dependency (git-as-artifact-store, no PyPI — uv add --dev git+https://github.com/TheodoreAD/repo-tasks) instead of hand-rolled tasks.py logic; the repo's own tasks.py is then just from repo_tasks import ns. See that repo's own README for the full task catalog (one invoke module per facility — quality, venv, deps, direnv, agents, docs, ...) — the two that matter for day-to-day work here: