Creator Toolkit CLI
A lightweight Python CLI for repeatable creator workflows. Generate content ideas and tags, or normalize a folder of image names from an interactive menu or scriptable subcommands.
This seven-second loop uses real CLI output, disposable sample files, and a fixed seed for reproducible suggestions.
Why Creator Toolkit?
- Preview filename changes before touching a directory, then undo applied renames from a manifest.
- Automate every scriptable workflow with stable JSON schemas and meaningful exit codes.
- Get the same CLI behavior on current Windows, macOS, and Linux systems.
- Keep small creator tasks local, inspectable, and easy to compose in scripts.
Real workflows
| Goal | Before | Example result |
|---|---|---|
| Draft a title | creator workflow |
10 Creator Workflow Tips Every Beginner Should Know |
| Pick three tags | --count 3 |
automation, productivity, tutorial |
| Preview image renames | --prefix campaign |
campaign_1.jpg, campaign_2.png — no files changed |
See the demo transcript and reproduction steps.
Features
- Generate title ideas from a keyword.
- Select unique tags from a curated list.
- Preview, apply, and undo deterministic JPEG and PNG filename changes with a safe custom prefix.
- Use automation-friendly subcommands or an interactive menu.
Requirements
- Python 3.11+
- A current Windows, macOS, or Linux system
See the platform support policy for the tested OS/Python matrix and support expectations.
Installation
Install the latest stable release from PyPI:
python -m pip install creator-toolkit-cli
Release notes and verified distribution hashes are available in the latest GitHub release.
Usage
Generate a title or tags:
creator-toolkit title "video editing"
creator-toolkit tags --count 5
Pass the same integer seed to reproduce a title or tag set; omit it for fresh suggestions:
creator-toolkit title "video editing" --seed 2026
creator-toolkit tags --count 5 --seed 2026
Add --json to any scriptable subcommand for automation-friendly output:
creator-toolkit title "video editing" --seed 2026 --json
creator-toolkit tags --count 5 --seed 2026 --json
creator-toolkit rename ./images --prefix campaign --dry-run --json
See the JSON output reference for response schemas, exit codes, error handling, and automation examples.
Preview changes to .jpg, .jpeg, and .png files without touching the directory:
creator-toolkit rename ./images --prefix campaign --dry-run
This produces names such as campaign_1.jpg. Omit --prefix to retain the default image_1.jpg
format. Unsafe filename components and cross-platform reserved names are rejected before any file
or manifest changes.
Apply the displayed plan after an interactive confirmation, using the same prefix:
creator-toolkit rename ./images --prefix campaign
For non-interactive automation, pass --yes. Every applied CLI rename writes a unique JSON
manifest in the image directory:
creator-toolkit rename ./images --prefix campaign --yes
creator-toolkit undo ./images/.creator-toolkit-renames-20260807T120000Z-a1b2c3d4.json --dry-run
creator-toolkit undo ./images/.creator-toolkit-renames-20260807T120000Z-a1b2c3d4.json
The rename command orders inputs by filename and uses a two-phase rename to avoid collisions and roll back when a filesystem step fails. Undo manifests store concrete operations, so undo does not need the original prefix. They reject path traversal and refuse to overwrite files created after the rename. Other files are left untouched, but a separate backup is still recommended for valuable assets.
Run without a subcommand to use the interactive menu:
creator-toolkit
Contributing
Looking for a first contribution? Browse open
good first issue
or help wanted
work, comment with your intended approach, and follow the
contributor guide.
Focused documentation, testing, bug-fix, and small feature pull requests are welcome.
Development
python -m pip install -e ".[dev]"
ruff check .
ruff format --check .
pytest
See CONTRIBUTING.md for setup, validation, demo generation, and pull request expectations.
Maintainers should follow the release checklist and complete the one-time trusted publishing setup before publishing a version.
License
MIT © 2026 HoungDev contributors.
Metadata
Release files for creator-toolkit-cli 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| creator_toolkit_cli-0.2.0.tar.gz | 282.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| creator_toolkit_cli-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 294.6 kB
Release files / creator_toolkit_cli-0.2.0.tar.gz
| Download URL | creator_toolkit_cli-0.2.0.tar.gz |
|---|---|
| Size | 282.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ec3caebee2c60de4abd2e7638e8b5814b9f5486acd583480fedd52c31705219
|
|
BLAKE2b-256 checksum How to use checksums |
85a3fa22768a51592771684c2313ddee3a711f593c1f8df7d1a78006d87f6a9c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 7, 2026.
Transparency logRelease files / creator_toolkit_cli-0.2.0-py3-none-any.whl
| Download URL | creator_toolkit_cli-0.2.0-py3-none-any.whl |
|---|---|
| Size | 12.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e1aa70df40d454a681948f2aede822cf21af397c45d88733462dead4e9d7d21f
|
|
BLAKE2b-256 checksum How to use checksums |
e1eac38e89bdd5e6df4397ad06342f425400bf2dc8323121a382751e3b975393
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 7, 2026.
Transparency log