smithery/vaayne

python-script

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.

Installation

$ npx skills add smithery/vaayne --skill python-script

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,465 B
  • docs SUMMARY.md 235 B

History

  1. First recorded snapshot · 0 installs

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