OpenClaw Skill template generator. Create skill scaffolds, validate structure, enhance SKILL.md, generate command frameworks, tips, publish checklists.
Multi-purpose utility tool for managing entries, searching data, and exporting records. A general-purpose CLI toolkit with init, add/remove, list, search, and export capabilities — ideal as a starting point for building your own skill or as a standalone data management tool.
| Command | Description |
|---|---|
skill-template run <input> | Execute the main function with the given input |
skill-template config | Show configuration file path (config.json location) |
skill-template status | Show current status (reports "ready" when operational) |
skill-template init | Initialize the data directory and prepare for use |
skill-template list | List all entries in the data log |
skill-template add <entry> | Add a new dated entry to the data log |
skill-template remove <entry> |
| Remove a specified entry |
skill-template search <term> | Search the data log for a term (case-insensitive) |
skill-template export | Export all data from the data log to stdout |
skill-template info | Show version number and data directory path |
skill-template help | Show help message with all available commands |
skill-template version | Show version number |
skill-template manages a simple text-based data log (data.log) in its data directory. You can add entries (automatically date-stamped), list them, search through them, and export the full contents. Every command is also recorded in a separate history.log for auditing.
skill-template init to set up the data directoryskill-template add to log items with automatic date stampsskill-template list to see all entries or skill-template search to find specific onesskill-template export to output all data for backup or processingAll data is stored in $SKILL_TEMPLATE_DIR or defaults to ~/.local/share/skill-template/. The directory contains:
data.log — main data file where entries are stored (date-stamped lines)history.log — timestamped log of all commands executedconfig.json — configuration file path (referenced by config command)The tool automatically creates the data directory on first run. You can override the storage location by setting the SKILL_TEMPLATE_DIR environment variable.
date, grep, wc, cat)skill-template add "meeting notes: discussed Q2 targets" to capture timestamped entries without opening an editorskill-template search "keyword" to find them laterskill-template export to pipe all entries to another tool or save as a backup file# Initialize the data directory
skill-template init
# Add some entries
skill-template add "Project Alpha: milestone 1 complete"
skill-template add "Bug fix: resolved login timeout issue"
skill-template add "Meeting: sprint review with team"
# List all entries
skill-template list
# Search for project-related entries
skill-template search "Project"
# Check the tool status
skill-template status
# View version and data location
skill-template info
# Show configuration path
skill-template config
# Export all data to a file
skill-template export > backup.txt
# Run a custom function
skill-template run "my-task"
Set the SKILL_TEMPLATE_DIR environment variable to change the data directory:
export SKILL_TEMPLATE_DIR="$HOME/my-skill-data"
Default location: ~/.local/share/skill-template/
All command output goes to stdout in plain text. The list and export commands output the raw content of data.log, making them easy to pipe into other tools:
skill-template list | grep "2024-03"
skill-template export | wc -l
Powered by BytesAgain | bytesagain.com | [email protected]