JSONL-based persistent audit trail. All mutating commands (sync, install, uninstall, audit, etc.) are logged automatically. Default launches interactive TUI on
The Log skill provides a JSONL-based persistent audit trail that automatically records all mutating commands such as sync, install, uninstall, and audit. It captures detailed metadata including timestamps, command names, statuses, and durations, enabling marketers to trace operational histories and diagnose issues with precision. The default mode launches an interactive terminal user interface (TUI) for real-time browsing, while options for structured JSON or plain text outputs support automation and integration with scripts.
This skill is designed for growth leads managing complex marketing tech stacks who need transparency into deployment and sync operations. PPC operators and SEO practitioners benefit from auditing install or uninstall commands to ensure campaign tracking updates are applied correctly. Agency strategists using multiple projects can leverage project-level logs to monitor changes and quickly identify errors or partial failures across client environments.
Practitioners typically start by running the log command to review recent operational history, filtering entries by command type or status to isolate issues such as failed syncs or errors during installation. Next, they might perform targeted queries with flags like `--since` to analyze activity within a defined timeframe, or `--tail` to focus on the most recent events. When automation is needed, exporting logs in JSONL format allows integration into dashboards or alerting systems. Finally, clearing logs selectively with the `--clear` flag helps maintain relevant audit trails without clutter.
How do I see only errors in my sync commands? Use the `--cmd sync --status error` flags together to filter for failed sync operations. Can I export logs for external processing? Yes, the `--json` flag outputs JSONL suitable for scripts or AI analysis. Is it possible to separate project logs from global logs? Yes, use the `-p` or `-g` flags to access project-specific or global log files respectively.
Attach the Log skill to a Metaflow agent task to automatically capture and persist all mutating command events related to that task’s lifecycle. Expect an interactive terminal interface by default for quick inspection, or configure output flags for programmatic log consumption within workflows. This enables continuous visibility into operational status, helping teams maintain audit compliance and swiftly resolve deployment issues.
For broader context, see our roundup of claude skills for marketing, and read how to create Claude skills for related setup guidance.