agentleFS
mihai-dinculescumihai-dinculescu/tapo/.claude/skills/update-maturin/SKILL.md

update-maturin

Skill877 starsChanged 6 days agoMITView on GitHub

Bump maturin to the latest release and regenerate `.github/workflows/tapo-py.yml`, preserving local customizations

  • Installs packages

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Test sdist step: keep this step between Build sdist and Upload sdist in the sdist job:

    line 42
  2. Very specific:

    Verify: Run git diff .github/workflows/tapo-py.yml.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Update Maturin

Bump the maturin build tool to the latest version and regenerate .github/workflows/tapo-py.yml from maturin generate-ci github, re-applying all local customizations.

Steps

  1. Bump the maturin dependency. From tapo-py/:

    uv lock --upgrade-package maturin
    uv sync
    uv run maturin --version

    Confirm the new version in the last command's output. If it didn't change, maturin is already at the latest — stop and tell the user.

  2. Regenerate the workflow baseline. From tapo-py/, run uv run maturin generate-ci github and capture the stdout (skip the 📦/🍹/🔗 progress lines). This is the baseline — do NOT overwrite .github/workflows/tapo-py.yml with it directly.
  3. Apply the baseline to .github/workflows/tapo-py.yml, re-applying each customization below. After editing, diff the updated file against the baseline — the only remaining differences should be exactly the items listed here. Anything in the committed file that is not on this list should be replaced with the baseline value, even if the committed file differs; treat those as stale upstream defaults, not deliberate customizations.

    • Workflow name: name: "Tapo Python" (baseline: name: CI).
    • Triggers under on::
      • push.branches: only main (baseline includes master).
      • push.tags: "v*" (baseline: '*').
      • pull_request.paths: keep the existing list (tapo/**, tapo-py/**, Cargo.lock, Cargo.toml, .github/workflows/tapo-py.yml). Baseline has no path filter.
    • --manifest-path ./tapo-py/Cargo.toml: append this flag to every args: line in each PyO3/maturin-action@v1 step (linux, musllinux, windows, macos, and sdist jobs).
    • manylinux: 2_28: in the linux job (baseline: auto).
    • GitHub Actions versions: never downgrade. For each uses: <action>@vN line, keep the higher of the two versions between the current file and the baseline (e.g. if the file pins actions/upload-artifact@v7 but the baseline emits @v6, keep @v7). To make this mechanical, compare with diff <(grep 'uses: actions/' .github/workflows/tapo-py.yml) <(grep 'uses: actions/' <baseline-file>) and reconcile each differing line by picking the higher @vN.
    • Job display names: each job has a name: using the Python / ... prefix convention. The baseline emits no name: on the matrix jobs and name: Release on the release job — re-add these after regeneration:
      • linux: name: Python / Linux wheel (${{ matrix.platform.target }})
      • musllinux: name: Python / Musllinux wheel (${{ matrix.platform.target }})
      • windows: name: Python / Windows wheel (${{ matrix.platform.target }})
      • macos: name: Python / macOS wheel (${{ matrix.platform.target }})
      • sdist: name: Python / Sdist
      • release: name: Python / Publish to PyPI (baseline: Release)
    • --check-url on publish: in the release job's Publish to PyPI step, keep run: uv publish --check-url https://pypi.org/simple/ 'wheels-*/*' (baseline: no --check-url). It makes a re-run publish skip files already on PyPI.
    • Test sdist step: keep this step between Build sdist and Upload sdist in the sdist job:

      - name: Test sdist
        run: |
          pip install --force-reinstall --verbose dist/*.tar.gz
          python -c 'from tapo import ApiClient'
  4. Verify. Run git diff .github/workflows/tapo-py.yml. Every line change should be either (a) the maturin v<old> → v<new> version bump in the header comment, (b) an upstream structural change introduced by the new maturin release, or (c) one of the preserved customizations above. Flag anything else before handing back.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.