listener-inbox
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.zipInstalls 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.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
When to use listener-inbox
- →Queueing repository health checks
- →Creating tickets via automation
- →Triggering background agent tasks
About listener-inbox
Handles TerMinal automation requests by enqueuing events in the local filesystem inbox. Enables deferred task execution for agent runs or ticketing.
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.
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.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| listener-inbox (this skill) | 0 | 3mo | Review | Intermediate |
| linear | 10 | 3mo | No flags | Beginner |
| zapier-workflows | 11 | 9mo | Review | Beginner |
| attio-skill-generator | 7 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by trevormil
View all by trevormil →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.
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.
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.
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.
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".
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.