LI

Queues work events by writing JSON request files for automated background processing.

Install

mkdir -p .claude/skills/listener-inbox && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18687" && unzip -o skill.zip -d .claude/skills/listener-inbox && rm skill.zip

Installs to .claude/skills/listener-inbox

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Queue local TerMinal automation listener events. Use when an integration, script, agent, or user wants to drop a JSON request into TerMinal's local automation inbox to trigger Activity, tickets, HITL, agent runs, or background tasks.
233 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • Queue local TerMinal automation listener events
  • Write JSON requests to the automation inbox
  • Trigger Activity, tickets, HITL, or agent runs
  • Trigger background tasks
  • Use `terminal-cli listener enqueue` command
  • Specify event source, type, and requested action

How it works

The skill queues local TerMinal automation events by writing JSON requests to a designated inbox directory, which TerMinal watches for processing.

Inputs & outputs

You give it
JSON request for TerMinal automation
You get back
JSON file written to `~/.config/TerMinal/automation-inbox/new/` for processing

When to use listener-inbox

  • Queueing repository health checks
  • Creating tickets via automation
  • Triggering background agent tasks

About this skill

Listener Inbox

Use TerMinal's local automation inbox when work should be requested by writing a durable JSON file instead of running immediately. The app watches:

~/.config/TerMinal/automation-inbox/new/

Files move through processing/, then done/, failed/, or dead-letter/. The Schedules tab's Listeners subtab shows queue counts and recent request -> action results. Listeners are paused by default; enable them in TerMinal before relying on automatic processing.

Preferred enqueue command

terminal-cli listener enqueue '{"source":"local-script","type":"automation.requested","title":"Run repo health","repoRoot":"'"$(pwd)"'","requestedAction":{"kind":"run-agent","agentId":"health","engine":"codex","mode":"agent"}}'

You may also write a .json file directly into automation-inbox/new/.

Envelope

Required:

  • source: integration or producer id, such as local-script, slack, github.
  • type: event type, such as automation.requested or merge_request.opened.

Recommended:

  • id: stable event id. If omitted, the CLI assigns one.
  • dedupeKey: stable idempotency key for external events.
  • repoRoot: absolute repo path for actions that touch a repo.
  • title, body: human-readable request text.
  • requestedAction: one allowlisted action.

Actions

{ "kind": "activity", "activityKind": "info", "title": "Observed event", "detail": "..." }
{ "kind": "file-ticket", "title": "Fix webhook", "body": "...", "type": "bug", "priority": "medium" }
{ "kind": "file-hitl", "title": "Approval needed", "action": "Approve deploy" }
{ "kind": "run-agent", "agentId": "health", "engine": "codex", "mode": "agent" }
{ "kind": "run-agent", "agentId": "health", "engine": "codex", "mode": "background", "prompt": "..." }
{ "kind": "background-task", "engine": "claude", "prompt": "..." }

Do not put arbitrary shell in listener events. If shell is needed, create an agent/script first and trigger it by id.

Safety

  • Use dedupeKey for polling/webhook integrations.
  • Unknown or invalid events should be allowed to land in failed/ or dead-letter/; do not retry by rewriting the same bad file in a loop.
  • For destructive/costly actions, file HITL instead of running directly.

When not to use it

  • When work should be run immediately instead of queued
  • When TerMinal listeners are paused
  • When arbitrary shell commands are needed in listener events

Limitations

  • Requires TerMinal listeners to be enabled for automatic processing
  • Does not support arbitrary shell in listener events
  • Unknown or invalid events may land in `failed/` or `dead-letter/`

How it compares

This skill enables deferred task execution by queuing JSON events for TerMinal, unlike direct execution of commands.

Compared to similar skills

listener-inbox side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
listener-inbox (this skill)01moReviewIntermediate
linear101moNo flagsBeginner
zapier-workflows118moReviewBeginner
attio-skill-generator77moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

linear

lobehub

Linear issue management guide. Use when working with Linear issues, creating issues, updating status, or adding comments. Triggers on Linear issue references (LOBE-xxx), issue tracking, or project management tasks. Requires Linear MCP tools to be available.

10117

zapier-workflows

davila7

Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.

11101

attio-skill-generator

kesslerio

Generate use-case-specific Attio workflow skills from templates. Use when creating new skills for lead qualification, deal management, customer onboarding, or custom Attio workflows.

7100

automation-brainstorm

MacroMan5

Interactive workflow design advisor for Power Automate, n8n, Make, Zapier and other platforms. Guides users through planning automation workflows with smart questions about triggers, actions, data flow, and error handling. Uses research sub-agent to find best practices and generates detailed implementation plan. Triggers when user mentions "create workflow", "build flow", "design automation", "need ideas for", or describes workflow requirements without having a complete design.

778

daily-briefing

anthropics

Start your day with a prioritized sales briefing. Works standalone when you tell me your meetings and priorities, supercharged when you connect your calendar, CRM, and email. Trigger with "morning briefing", "daily brief", "what's on my plate today", "prep my day", or "start my day".

761

jira

davila7

Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.

1152

Search skills

Search the agent skills registry