Skip to main content

Taku

Simple script manager for creating, running, and syncing scripts.

Publish to PyPIPyPI - Version PyPI - Python Version MIT License Status Ruff uv

Installation

uv tool install taku-cli

or

uv tool install "taku-cli[bling]" # just adds some colors

Quick Start

asciicast

Commands

  • taku new <name> [--template/-t <name>] - Create a new script from template
  • taku list - List all scripts, add -t to also list templates
  • taku get <name> - Show script details
  • taku edit <name> - Edit a script (auto-pushes to git if repository)
  • taku run <name> [args...] - Run a script with optional arguments
  • taku rm <name> - Remove a script (auto-pushes to git if repository)
  • taku install <name|all> - Install script to ~/.local/bin
  • taku uninstall <name|all> - Remove script from ~/.local/bin

Configuration

Set the scripts directory:

export TAKU_SCRIPTS=~/my-scripts

Default: ~/scripts

Templates

Create templates in <scripts-dir>/.templates/ and use with:

taku new myapp --template python

Template resolution order:

  1. <scripts-dir>/.templates/<template-name>
  2. ./<template-name> (current directory)

Templates can use ${script_name} variable for substitution.

Example Python template (~/.scripts/.templates/python):

#!/usr/bin/env -S uv run --script
# /// script
# requires-python = ">=3.12"
# dependencies = []
# ///


def main() -> None:
    print("Hello from $script_name!")


if __name__ == "__main__":
    main()

Git Integration

If your scripts directory is a Git repository, taku will automatically commit and push changes whenever you edit or remove scripts. This keeps your changes synced, but to complete the auto-sync feature you also need to set up each machine to regularly pull the latest scripts.

Using cron

  1. Open your crontab:

    crontab -e
    
  2. Add a line to pull updates every 15 minutes (adjust the path to your scripts directory):

    */15 * * * * cd /home/tobi/scripts && git pull >/dev/null 2>&1
    

Using systemd-timers

  1. Create a service file /etc/systemd/system/scripts-sync.service (adjust the path to your scripts directory):

    [Unit]
    Description=Synchronize scripts from remote
    
    [Service]
    Type=oneshot
    User=tobi
    WorkingDirectory=/home/tobi/scripts
    ExecStart=/usr/bin/git pull
    
  2. Create a timer file /etc/systemd/system/scripts-sync.timer:

    [Unit]
    Description=Periodic synchronization of scripts
    
    [Timer]
    OnBootSec=1min
    OnUnitActiveSec=15min
    Persistent=true
    
    [Install]
    WantedBy=timers.target
    
  3. Enable the timer:

    sudo systemctl daemon-reload
    sudo systemctl enable --now scripts-sync.timer
    

This will run a git pull in your scripts directory every 15 minutes.

Metadata

Release files for taku-cli 0.4.14

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for taku-cli 0.4.14
File Size Uploaded
taku_cli-0.4.14.tar.gz 8.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for taku-cli 0.4.14
File Interpreter ABI Platform
taku_cli-0.4.14-py3-none-any.whl Python 3 none any Details

Total release size: 17.9 kB

Release files / taku_cli-0.4.14.tar.gz

Download URL taku_cli-0.4.14.tar.gz
Size 8.6 kB
Tags Source
SHA-256 checksum
How to use checksums
d6828816594f08310163ffeda51e4eaf9c004acb7189300cbe13c4b1bd9f3774
BLAKE2b-256 checksum
How to use checksums
5c954f389d5b817035579773a2b2b92c38b3de48a356920bdac2818b37260ec2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Dec 13, 2025.

Transparency log

Release files / taku_cli-0.4.14-py3-none-any.whl

Download URL taku_cli-0.4.14-py3-none-any.whl
Size 9.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ece56e94791f2ed2fbe9ab4af324a599255fc47c6ed99e79024fc9e902a97442
BLAKE2b-256 checksum
How to use checksums
39d19a12109be515ee7af2fca21da56ad6a3dd524f6f1be724bef2f710ee0a4d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Dec 13, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

0.4.14 This release

2 release files

0.4.12

2 release files

0.4.11

2 release files

0.4.10

2 release files

0.4.9

2 release files

0.4.8

2 release files

0.4.7

2 release files

0.4.6

2 release files

0.4.5

2 release files

0.4.4

2 release files

0.4.3

2 release files

0.4.2

2 release files

0.4.1

2 release files

0.4.0

2 release files

0.3.1

2 release files

0.2.4

2 release files

0.2.3

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page