AGENT SKILL

pypi-maintainer

Switch a PyPI package install between the production index, TestPyPI pre-release builds, and a local editable checkout. Use when an agent maintains a package and needs to verify a TestPyPI dev build before promoting to production, or when the user says "install from test-pypi", "switch to local", "change package source", or "install from pypi".

License 许可
Apache-2.0
最近更新
2026-09-29
Stars
★ 3
Forks
0

01 前言 Front Matter

name
pypi-maintainer
type
command
description
Switch a PyPI package install between the production index, TestPyPI pre-release builds, and a local editable checkout. Use when an agent maintains a package and needs to verify a TestPyPI dev build before promoting to production, or when the user says "install from test-pypi", "switch to local", "change package source", or "install from pypi".

02 资源文件 1

03 SKILL.md 正文

PyPI Maintainer

Switch the install source for a package the agent maintains. Three sources are supported: production PyPI, TestPyPI (pre-release / dev builds), and a local editable checkout. The same script works for any package an AgentCulture sibling publishes — pass the package name as the first argument.

When to use

  • Verifying a PR's TestPyPI dev build before merging.
  • Reproducing a user-reported bug against the published version.
  • Hot-patching against a local checkout while a fix is in flight.
  • Restoring the production install after local-mode debugging.

Usage

# Production PyPI
bash .claude/skills/pypi-maintainer/scripts/switch-source.sh <package> pypi

# TestPyPI (pre-release dev builds)
bash .claude/skills/pypi-maintainer/scripts/switch-source.sh <package> test-pypi

# TestPyPI, pinned to a specific dev version
bash .claude/skills/pypi-maintainer/scripts/switch-source.sh <package> test-pypi --version 0.4.0.dev42

# Local editable checkout (defaults to current directory)
bash .claude/skills/pypi-maintainer/scripts/switch-source.sh <package> local

# Local editable from an explicit path
bash .claude/skills/pypi-maintainer/scripts/switch-source.sh <package> local --path ../<package>

Prerequisites

The script requires the following tools on PATH:

  • bash
  • uv — the script delegates to uv tool install and uv tool list (or uv pip install for local).

Why TestPyPI needs special flags

When a package is published to both PyPI and TestPyPI, uv tool install finds the production version on PyPI first and never looks at TestPyPI. The script passes --index-strategy unsafe-best-match so uv compares the two index sets and picks the highest version, plus --prerelease=allow because TestPyPI builds carry dev suffixes (e.g. 0.4.0.dev42).

After running

The script prints the resolved version once install completes — cross-check that against the expected version (PR run number, local pyproject.toml) before continuing.

Arguments

Position / flag Meaning
<package> (required) The PyPI distribution name, e.g. steward-cli, culture, daria-cli.
<source> (required) One of pypi, test-pypi, local.
--version VERSION Pin to a specific version (TestPyPI builds typically need this).
--path PATH Local-source-only: path to the editable checkout (default: cwd).

04 同仓库更多 Skills

agentculture
agentculture/culture-nodes

sample

Fixture skill proving the .qwen/skills leg carries at least one skill.

★ 3
agentculture
agentculture/culture-nodes

sample

Fixture skill proving the .qwen/skills leg carries at least one skill.

★ 3
agentculture
agentculture/culture-nodes

sample

Fixture skill proving the .qwen/skills leg carries at least one skill.

★ 3
agentculture
agentculture/culture-nodes

think

Think a vague feature idea into a buildable spec by working backwards (the idea→spec leg; drives the `devague` CLI). Start from the announcement ("pretend it shipped"), capture and classify claims, interrogate them with honesty conditions and hard questions, park open vagueness as a first-class object, and export a spec only once the frame *converges*. Use when the user says "think this through", "spec this", "work backwards", "turn this idea into a spec", "announcement frame", or "devague", or when a feature request is too vague to build yet. Explore scope first when the idea touches an existing codebase — the sibling `scope` skill is the optional opening leg ahead of `think`. Once a spec exports, hand off to the sibling `spec-to-plan` skill to turn it into a plan. Authored and maintained in agentculture/devague (origin = devague); guildmaster pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from guildmaster like the other skills here.

★ 3
agentculture
agentculture/culture-nodes

summarize-delivery

Close the loop after an `assign-to-workforce` run by turning what actually happened into an accountability artifact — planned versus actual delivery, mid-work decisions, plan drift, evidence-backed delivery claims, and remaining work. The plan the user confirmed is the contract; this skill records where execution obeyed it, where it changed, and what is genuinely safe to claim as delivered. Runs on complete, partial, AND failed runs — failure is reported faithfully, never smoothed over. Use when the user says "summarize delivery", "delivery summary", "wrap up", "close the loop", "what did we actually ship", or "plan versus actual", or after `assign-to-workforce` merges (or fails to merge) a plan's waves. Authored and maintained in agentculture/devague (origin = devague); guildmaster pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from guildmaster like the inbound skills here.

★ 3
agentculture
agentculture/culture-nodes

spec-to-plan

Turn a converged devague spec into a buildable plan by working forwards (the spec→plan leg; drives the `devague plan` CLI group). Seed a plan from a converged frame, add tasks that collectively cover every coverage target (the frame's confirmed claims + honesty conditions), give each task acceptance criteria and an honest dependency order, park genuine unknowns as first-class risks, and export a plan only once it *converges*. Use when the user says "spec to plan", "stp", "turn this spec into a plan", "plan this spec", "make a build plan", or after the `think` skill exports a spec. Authored and maintained in agentculture/devague (origin = devague); guildmaster pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from guildmaster like the other skills here.

★ 3