ワンクリックで
self-contained-python-scripts
Use uv and PEP 723 to write self-installing autocontained Python scripts
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use uv and PEP 723 to write self-installing autocontained Python scripts
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | self-contained -python-scripts |
| description | Use uv and PEP 723 to write self-installing autocontained Python scripts |
Use this to write Python tools / scripts / clis as single files.
Using PEP 723 inline metadata, you can create self-contained Python scripts that declare their own dependencies. This allows you to run your scripts in isolated environments without needing to manually set up virtual environments or install dependencies.
To do that, embed the invocation of the uv command right in the shebang line.
#!/usr/bin/env -S uv run --script
# /// script
# requires-python = ">=3.13"
# dependencies = [
# "httpx",
# ]
# ///
import httpx
.
.
.
Add beui-style loading animations (spinner, bouncing dots, bars, dot-matrix, dither, terminal/ascii spinners, shape morph, comet, scramble text, metaballs, newton's cradle, helix, percent counter) to any project as vanilla HTML/CSS/JS — no React, no build step, no dependency. Use this skill whenever the user wants a loader, spinner, loading indicator, progress animation, or "loading..." state in a non-React project — server-rendered templates (Go, Rails, Django, Flask/Jinja, PHP), HTMX, Web Components, static HTML, or plain JS apps — even if they don't mention beui by name. Also use it when the user asks to port or copy a beui motion component.
Audit a codebase for health issues — oversized files, duplicated logic, dead code, unused parameters, test coverage gaps, and documentation/config drift — and report findings ordered by severity. Use this skill whenever the user invokes "/check-code-health", asks about "code health", "tech debt", "code quality audit", "find dead code", "what needs cleanup", or wants a maintenance overview of the repo.
Update project dependencies safely — list outdated packages, upgrade minors/patches in bulk and majors individually with changelog review, verify with build and tests, and commit in clean chore(deps) commits. Use this skill whenever the user says "update dependencies", "upgrade deps", "bump packages", "are my dependencies outdated", "update to the latest version of X", or mentions dependabot/renovate-style maintenance. Not for adding a brand-new dependency.
Diagnose and fix a bug or GitHub issue with test-backed verification — reproduce, root-cause, fix, and guard with a red-green or regression test so it can't silently return. Use this skill whenever the user says "fix this bug", "there's a bug in", "this is broken", "fix issue
Get a failing build back to green — run the project's build, test, and lint commands, then fix every reported compile error, test failure, and lint violation until all pass. Use this skill whenever the user invokes "/fix-build", says "the build is broken", "fix the build", "it doesn't compile", "CI is red", "make the tests pass", or pastes build/compiler errors asking for them to be resolved.
Generate or update CLAUDE.md for a codebase the thorough way — discover architecture, workflows, and project-specific conventions, merge with existing AI-agent instruction files, and iterate with the user. Use this skill whenever the user invokes "/initialise", says "set up CLAUDE.md", "update the CLAUDE.md", "initialise this repo for Claude", or wants AI-agent onboarding docs written for a project. Prefer this over the built-in /init when the user asks for the fancy/thorough version.