agentleFS
vaaynevaayne/agent-kit/skills/python-script/SKILL.md

python-script

Skill54 starsChanged 27 days agoMITView on GitHub

Create robust Python automation with full logging and safety checks. Use when tasks need complex data processing, authenticated API work, conditional file operations, or error handling beyond simple shell commands.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. buildosaurus/scripteratops★ 0same name
    2. haztecaso/skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Run with uv run --script ~/.agents/sessions/{project}/scripts/{script_name}.py and monitor logs.

    line 20
  2. Very specific:

    Add RotatingFileHandler if logs may grow large

    line 27
  3. Very specific:

    Read references/script-template.md for the full script template.

    line 31
  4. Distinctive:

    Use temporary directories for intermediates

    line 37
  5. Distinctive:

    Never run destructive steps without confirmation

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Python Scripter

Overview

Design and run Python scripts with clear requirements, safety checks, and reproducible logging.

Workflow

{project} is the git repo name (if in a git repo) or the basename of the current working directory.

  1. Confirm inputs, outputs, constraints, and preferred libraries.
  2. Identify risky operations and secure explicit approval.
  3. Scaffold a script with PEP 723 metadata and structured logging.
  4. Lint with uvx ruff check --fix ~/.agents/sessions/{project}/scripts/{script_name}.py.
  5. Run with uv run --script ~/.agents/sessions/{project}/scripts/{script_name}.py and monitor logs.
  6. Report results, risks encountered, and any follow-up steps.

Logging requirements

  • Log to ~/.agents/sessions/{project}/logs/{script_name}.log and stream to console
  • Capture start/end timestamps, parameters, file operations, and errors
  • Add RotatingFileHandler if logs may grow large

Template

Read references/script-template.md for the full script template.

Safety practices

  • Provide dry-run or rollback paths
  • Validate external inputs and API responses
  • Use temporary directories for intermediates
  • Never run destructive steps without confirmation

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.