← Back to Skills Marketplace
bytesagain3

Deploy Tool

by bytesagain3 · GitHub ↗ · v2.0.0 · MIT-0
cross-platform ✓ Security Clean
167
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install deploy-tool
Description
The PHP deployment tool with support for popular frameworks out of the box deploy-tool, php, deploy, deployment, php, provision.
README (SKILL.md)

Deploy Tool

Deploy Tool v2.0.0 — a utility toolkit for logging, tracking, and managing deployment-related entries from the command line.

Commands

All commands accept optional input arguments. Without arguments, they display recent entries from the corresponding log. With arguments, they record a new timestamped entry.

Command Description
run \x3Cinput> Record or view run entries
check \x3Cinput> Record or view check entries
convert \x3Cinput> Record or view convert entries
analyze \x3Cinput> Record or view analyze entries
generate \x3Cinput> Record or view generate entries
preview \x3Cinput> Record or view preview entries
batch \x3Cinput> Record or view batch entries
compare \x3Cinput> Record or view compare entries
export \x3Cinput> Record or view export entries
config \x3Cinput> Record or view config entries
status \x3Cinput> Record or view status entries
report \x3Cinput> Record or view report entries
stats Show summary statistics across all log files
search \x3Cterm> Search all log entries for a keyword (case-insensitive)
recent Display the 20 most recent history log entries
help Show usage information
version Print version (v2.0.0)

Data Storage

All data is stored locally in ~/.local/share/deploy-tool/:

  • Per-command logs — Each command (run, check, convert, etc.) writes to its own .log file with pipe-delimited timestamp|value format.
  • history.log — A unified activity log recording every write operation with timestamps.
  • Export formats — The export utility function supports JSON, CSV, and TXT output, written to ~/.local/share/deploy-tool/export.\x3Cfmt>.

No external services, databases, or API keys are required. Everything is flat-file and human-readable.

Requirements

  • Bash (v4+ recommended)
  • No external dependencies — uses only standard Unix utilities (date, wc, du, tail, grep, sed, basename, cat)

When to Use

  • When you need to log and track deployment-related activities from the command line
  • To maintain a searchable history of deployment operations
  • For batch recording of deployment tasks with timestamps
  • When you want to export deployment logs in JSON, CSV, or TXT format
  • As part of a larger automation pipeline for tracking deployment workflows
  • To get quick statistics and summaries of past deployment activities

Examples

# Record a new run entry
deploy-tool run "deployed v1.2.3 to production"

# View recent run entries (no args = show history)
deploy-tool run

# Check something and log it
deploy-tool check "nginx config validated"

# Analyze and record
deploy-tool analyze "memory usage at 72%"

# Search across all logs
deploy-tool search "production"

# View summary statistics
deploy-tool stats

# Show recent activity across all commands
deploy-tool recent

# Show tool version
deploy-tool version

# Show full help
deploy-tool help

How It Works

Each command follows the same pattern:

  1. With arguments — Timestamps the input, appends it to the command-specific log file, prints confirmation, and logs to history.log.
  2. Without arguments — Shows the last 20 entries from that command's log file.

The stats command iterates all .log files, counts entries per file, and reports totals plus disk usage. The search command performs case-insensitive grep across all log files. The recent command tails the last 20 lines of history.log.


Powered by BytesAgain | bytesagain.com | [email protected]

Usage Guidance
This skill appears coherent and local-only, but review these before installing: 1) It will create and write logs under ~/.local/share/deploy-tool — check and backup/remove that directory if needed. 2) Do not enter secrets or credentials into logged entries; all entries are stored in plaintext and exported by the export command. 3) The package provides a Bash script but no automated installer — confirm how the agent will execute or install the script (it may require you to place it on PATH or run it manually). 4) If you need networked deployment capabilities, this tool does not provide them; prefer a different tool that explicitly integrates with your deployment target. If any of the above is unacceptable, do not install or run the script.
Capability Analysis
Type: OpenClaw Skill Name: deploy-tool Version: 2.0.0 The 'deploy-tool' is a simple Bash-based logging utility that records timestamped entries to local flat files in ~/.local/share/deploy-tool/. While the SKILL.md description hyperbolically claims it is a 'PHP deployment tool', the actual implementation in scripts/script.sh is limited to basic text logging, searching, and exporting of activity logs using standard Unix utilities. There are no network calls, credential access, or execution of external payloads.
Capability Assessment
Purpose & Capability
Name/description (PHP deployment/logging tool) align with the provided implementation: a Bash script that records and reads timestamped deployment-related entries. There are no unrelated requirements (no cloud creds, no external binaries).
Instruction Scope
SKILL.md and the script are consistent: all operations are local file reads/writes and simple text processing (grep, tail, wc, du). Note: the tool will record any user-provided text to logs, so logging secrets or sensitive deployment credentials into entries would persist in plain text under the data directory.
Install Mechanism
No install spec (instruction-only) and the included script is a plain Bash file. Nothing is downloaded or executed from external URLs.
Credentials
The skill asks for no environment variables, no credentials, and no config paths. The only side effect is creating/writing files under the user's home directory (~/.local/share/deploy-tool), which is proportional to a local logging tool.
Persistence & Privilege
always:false (normal). The tool persists data by creating files in the user's home directory. This is expected, but users should be aware logs are stored locally and persist until removed.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install deploy-tool
  3. After installation, invoke the skill by name or use /deploy-tool
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v2.0.0
publish v2.0.0
Metadata
Slug deploy-tool
Version 2.0.0
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is Deploy Tool?

The PHP deployment tool with support for popular frameworks out of the box deploy-tool, php, deploy, deployment, php, provision. It is an AI Agent Skill for Claude Code / OpenClaw, with 167 downloads so far.

How do I install Deploy Tool?

Run "/install deploy-tool" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Deploy Tool free?

Yes, Deploy Tool is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Deploy Tool support?

Deploy Tool is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Deploy Tool?

It is built and maintained by bytesagain3 (@bytesagain3); the current version is v2.0.0.

💬 Comments