Trigger

Trigger - command-line tool for everyday use

Security Scan

The skill is a local command‑line productivity tool that reads/writes files under the user's home directory and does not request credentials or perform network access in the included code.

Purpose & Capability

Name/description (a local CLI 'trigger' toolkit) matches the included shell script which implements add/plan/track/etc and stores data under ~/.local/share/trigger. No unexpected services or cloud credentials are requested.

Instruction Scope

SKILL.md usage and examples align with the script behavior (run, status, export, etc). The README mentions an optional TRIGGER_DIR env var which the script honors indirectly via its DATA_DIR default; instructions do not ask the agent to read unrelated system files or exfiltrate data.

Install Mechanism

There is no install spec (instruction-only), but the skill bundle includes a shell script (scripts/script.sh). This means the agent or user could execute that script from the bundle; no external downloads or installers are used. Consider that code in the bundle will be present on disk when installed.

Credentials

The skill requires no credentials or special environment variables. It uses HOME to build a per‑user data directory and optionally respects TRIGGER_DIR; this is reasonable for a local CLI. Note: all data is stored in plaintext logs under the data directory, so sensitive content should not be saved there.

Persistence & Privilege

The skill does not request always:true, does not modify other skills or system-wide settings, and confines writes to its own data directory. Autonomous invocation is allowed by platform default but is not combined with broad privileges here.

Assessment

This skill appears coherent and local-only, but review a few things before installing: (1) inspect the full script for any network calls or commands not shown in the truncated portion; (2) be aware it stores logs and exports plaintext files under ~/.local/share/trigger by default—do not save secrets there; (3) you can set TRIGGER_DIR to a location you control; (4) note the SKILL.md shows v2.0.0 while the registry lists 1.0.2 and the bundle has no homepage/source URL—if provenance matters, ask the publisher for a verified source; (5) if you want stronger isolation, run the script in a restricted environment (container or limited‑permission user) before trusting it with real data.

Event trigger toolkit — webhook handlers, file watchers, condition-based automation, event logging, and chain triggers.

Commands

Command	Description
trigger run	Execute main function
trigger list	List all items
trigger add <item>	Add new item
trigger status	Show current status
trigger export <format>	Export data
trigger help	Show help

Usage

# Show help
trigger help

# Quick start
trigger run

Examples

# Run with defaults
trigger run

# Check status
trigger status

# Export results
trigger export json

How It Works

Tips

• Run trigger help for all commands
• Data stored in ~/.local/share/trigger/

When to Use

• to automate trigger tasks in your workflow
• for batch processing trigger operations

Output

Returns formatted output to stdout. Redirect to a file with trigger run > output.txt.

Configuration

Set TRIGGER_DIR environment variable to change the data directory. Default: ~/.local/share/trigger/

---

Powered by BytesAgain | bytesagain.com Feedback & Feature Requests: https://bytesagain.com/feedback