Agent skill · software engineering · lobehub
agent-signal
Use for Agent Signal sources, actions, policies, middleware, workflow handoff and deduplication.
Why this skill is useful
Adds executable scripts and detailed workflows for implementing event-driven background work in agent systems, which are not covered in general programming knowledge.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 81,352 stars on the source repository.
What this skill does
Agent Signal Use this skill to implement event-driven background work for agents without coupling the work to the foreground chat request. Agent Signal has one consistent runtime shape: source event -> signal interpretation -> action execution -> built-in result signals Durable self-iteration work has one extra completion branch: memory/skill action -> execAgent enqueue -> agent.execution.completed -> selfIteration receipt projection Start Here 1. Read references/architecture.md to map the package boundary, runtime queue, scope model, and async workflow handoff. 2. Read references/handlers.md before writing any new policy, source handler, signal handler, or action handler. 3. Read references/observability.md when you need tracing, metrics, debugging, or workflow snapshot visibility. Use The Right Entry Point Use emitAgentSignalSourceEvent(...) when a server-owned producer should execute the pipeline immediately. Use executeAgentSignalSourceEvent(...) when a worker or controlled backend path already owns execution timing and may inject a runtime guard backend. Use enqueueAgentSignalSourceEvent(...) when the caller should return quickly and let Upstash Workflow process the event out-of-band. Use emitAgentSignalSourceEventWithStore(...) for isolated tests or evals that should avoid ambient Redis state. Read: apps/server/src/services/agentSignal/index.ts apps/server/src/workflows/agentSignal/index.ts apps/server/src/workflows/agentSignal/run.ts Core Model source: A normalized fact that happened. Sources come from producers such as runtime lifecycle events, user messages, or bot ingress. signal: A semantic interpretation derived from one source or from another signal. Signals express meaning, routing, or policy state. action: A concrete side effect planned from one signal. Actions do the work. policy: An installable middleware bundle that registers source, signal, and action handlers. procedure: Not a distinct runtime node. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills lobehub/agent-signal