Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

pypi-maintainer

Étoiles28

Forks6

Mis à jour2 juin 2026 à 19:06

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".

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

agentculture

agentculture/reachy-mini-mcp

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

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".

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).

Plus depuis ce dépôt

même dépôt

recall

agentculture/reachy-mini-mcp

Search the shared eidetic memory store and get back ranked, provenanced records. Drives `eidetic recall` with four search modes — exact (verbatim substring), approximate (vector/semantic), keyword (BM25 lexical), and hybrid (a weighted blend of vector+keyword, the default) — each hit carrying its text, full metadata, a relevance `score`, and a freshness `signal`. Recall passively reinforces matched records (bumps last_recall + recall_count). Shadowed and archived records are excluded by default; use --include-shadowed / --include-archived to retrieve them. The store lives at ~/.eidetic/memory (a home-dir path outside any git worktree); the wrapper defaults queries to this agent's PERSONAL, PRIVATE scope (`--scope reachy-mini-mcp --visibility private`, suffix read from culture.yaml) — matching where /remember writes — so a no-flag recall returns this agent's own private records plus the shared public pool, and Claude and the colleague backend recall each other's memories because both resolve the same suffix vi

2026-06-2328

remember

agentculture/reachy-mini-mcp

Ingest records into the shared eidetic memory store so they can be recalled later. Drives `eidetic remember`: accepts one record as a JSON object, or a batch as NDJSON on stdin for bulk ingest. Upsert is idempotent by id (and dedups by content hash) — re-remembering updates in place, never duplicates. Stamps a `created` date on every record at ingest time. Accepts `supersedes` (id of the record this one replaces, for within-scope shadowing via `sweep`) and `links` (list of related-memory ids). The store lives at ~/.eidetic/memory (a home-dir path outside any git worktree), and the wrapper defaults records to this agent's PERSONAL, PRIVATE scope (`--scope reachy-mini-mcp --visibility private`, suffix read from culture.yaml) so they don't leak to a default/other-scope recall — Claude and the colleague backend still share them because both resolve the same suffix via this skill. Pass `--visibility public` to contribute to the shared public pool instead. Use when the user says "remember this", "store this", "save

2026-06-2328

agent-config

agentculture/reachy-mini-mcp

Show a Culture agent's full configuration in one read-only view: its system-prompt file (CLAUDE.md / AGENTS.md / GEMINI.md), the parallel culture.yaml, and the agent's local .claude/skills index. Use when an operator says "show agent <name>", "what does <agent> look like", or before teaching/onboarding an agent and you need to see its current kit + config. Backs the `guild show` verb. Vendored from steward (cite-don't-import); inventory only — it reports, it does not judge alignment or drift.

2026-06-0228

assign-to-workforce

agentculture/reachy-mini-mcp

Fan out a converged devague plan's dependency waves to parallel agents in isolated git worktrees, one agent per task per wave, with TDD-gated merges by the main agent. Human gates: the exported spec, the implementation split plan (task map + per-task agent/model proposal + go/no-go), and the final PR. The devague CLI stays deterministic and non-orchestrating (#20) — it only *describes* the graph via `devague plan waves`; the operator (main agent) performs the fan-out. Use when the user says "assign to workforce", "fan out the plan", "parallel subagents", or after /spec-to-plan exports a plan. Authored and maintained in agentculture/devague (origin = devague); steward pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from steward like the other skills here.

2026-06-0228

cicd

agentculture/reachy-mini-mcp

reachy-mini-mcp's CI/CD lane, layered on `devex pr`. Delegates lint / open / read / reply / delta to devex; adds two extensions — `status` (SonarCloud quality gate + hotspots + unresolved-thread tally) and `await` (read --wait + status with non-zero exit on Sonar ERROR or unresolved threads). Use when: creating PRs in reachy-mini-mcp, handling review feedback, polling CI status, or the user says "create PR", "review comments", "address feedback", "resolve threads". Renamed from `pr-review` in steward 0.7.0; rebased on devex in 0.12.0.

2026-06-0228

communicate

agentculture/reachy-mini-mcp

Cross-repo + mesh communication from reachy-mini-mcp: file tracked GitHub issues on sibling repos, fetch issues from sibling repos to inline current state into briefs, and send live messages to Culture mesh channels. Use when the next step lives outside reachy-mini-mcp (a brief for a sibling-repo agent, a status ping for a Culture channel, or pulling an issue body + comments into context). Issue posts auto-sign with `- reachy-mini-mcp (Claude)`; mesh messages are unsigned (the IRC nick is the speaker). Not for in-reachy-mini-mcp issues — use `gh issue create` or the `cicd` skill for those. Renamed from `coordinate` in steward 0.8.0; absorbed `gh-issues` in 0.9.1. Issue I/O is backed by `agtag` (>=0.1) starting in 0.11.0.

2026-06-0228

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".

PyPI Maintainer

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

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).