Script creator

Skill jehrhardt/agents/skills/script-creator

My agent skills

Install

npx -y skills add jehrhardt/agents --skill script-creator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use it when the user asks for creating a script or a tool to extend the agent. Also use it when a script should be added to a skill or an existing script or tool should be improved.

SKILL.md

1.9 KB, 401 tokens by cl100k_base, as published. Nobody here has run it

Script Creator

When a script (e.g. as part of a skill) should be created, Python is the preferred programming language. When a tool for an agent should be created, a skill with a Python script is the preferred approach.

For Python, the uv package manager is used to create and run scripts. It is also used to add dependencies to scripts.

General Workflow

Check, if uv has been installed. Ask the user to install it, if it is not available.
Create a skill to provide instructions on how to use the script.
Create a new script with uv in the scripts directory of the skill:
```
uv init --script example.py --python 3.14
```
This will create a script with Python inline meta data.
Add dependencies to the script with uv:
```
uv add --script example.py 'Typer'
```
This will add the Python library to the script's inline meta data.
Add the script to the file.
Test the script with uv:
```
uv run --script example.py
```
uv will automatically ensure the required Python version and dependencies are installed to run the script.

Rules for Scripts

Make sure that the following rules are followed, when creating a script:

Add a CLI to the script via Typer
Use CLI arguments instead of environment variables for scripts
CLI arguments should have default values, if possible (ask the user for the right defaults)
After editing a script ALWAYS format it via uvx ruff format
After editing a script ALWAYS check it via uvx ruff check, and fix all warnings
ALWAYS include examples and instructions in skills to use uv run --script to run a script