triggers

Manage trigger lifecycles for Claude sessions via CLI commands.

2|2|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/mxzinke/atlas --skill triggers-mxzinke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triggers
Source: https://github.com/mxzinke/atlas/tree/main/app/defaults/skills/triggers
Command: npx skills add https://github.com/mxzinke/atlas --skill triggers-mxzinke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CLI-driven orchestration of autonomous agent triggers to wake Claude sessions on cron, webhook, or manual events, enabling predictable, event-driven execution without polling.

Core Features & Use Cases

  • Trigger lifecycle management: create, update, enable/disable, delete triggers via simple CLI commands.
  • Multi-channel support: define triggers that work across cron, webhooks, manual triggers, and channel-backed prompts (Signal, WhatsApp, Telegram, Email).
  • Prompt and wiring: per-trigger prompt.md files and optional scripts for filtering, plus optional background services for persistent listeners.
  • Deployment and operations: scaffold triggers in ~/triggers/, configure webhook relay, and manage crontab and supervisor integrations.
  • Use Case: orchestrate a daily status report by a cron trigger that prompts an agent to summarize system health.

Quick Start

Create a cron trigger named daily-report and place its prompt at ~/triggers/daily-report/prompt.md.

Frequently Asked Questions about triggers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Claude sessions to run on a cron schedule from the CLI?

The triggers Skill supports multi-channel automation, allowing you to define triggers across cron schedules, webhooks, and manual events, with optional background services for persistent listeners like Signal, WhatsApp, Telegram, or Email.

How do I set up a webhook to wake an autonomous agent?

Yes, you can filter webhook or cron events by placing optional filter scripts alongside the per-trigger prompt.md file in the ~/triggers/ directory to ensure only specific events wake the Claude session.

Can I use manual triggers alongside scheduled cron jobs for agent orchestration?

This Skill manages the entire trigger lifecycle, allowing you to enable or disable specific triggers via simple CLI commands, effectively pausing autonomous agent execution without deleting the trigger configuration.

What do I need to deploy event-driven agent triggers in my environment?

You need a CLI environment to run trigger commands, a ~/triggers/ directory for scaffolding prompt files and scripts, and optional supervisor or crontab integrations to manage persistent background services for reliable operation.