Foundatio
FoundatioFx/Foundatio
A skill your agent uses when working with Foundatio infrastructure abstractions for .NET -- caching, queuing, messaging, file storage, distributed locking, or background jobs.
Guides building event-driven background work for LobeHub agents, with sources, signals, actions, policies, workflow handoff and deduplication.
Install Agent Signal Pipeline
$ npx skills add lobehub/lobehub --skill agent-signal -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install lobehub/lobehub agent-signal --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/lobehub/lobehub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/agent-signal .claude/skills/agent-signal && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "agent-signal" agent skill from https://github.com/lobehub/lobehub/tree/canary/.agents/skills/agent-signal into .claude/skills/agent-signal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-signal", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/lobehub/lobehub/tree/canary/.agents/skills/agent-signalType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add lobehub/lobehub --skill agent-signal -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install lobehub/lobehub agent-signal --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lobehub/lobehub.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/agent-signal .agents/skills/agent-signal && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "agent-signal" agent skill from https://github.com/lobehub/lobehub/tree/canary/.agents/skills/agent-signal into .agents/skills/agent-signal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-signal", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add lobehub/lobehub --skill agent-signal -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install lobehub/lobehub agent-signal --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lobehub/lobehub.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/agent-signal .cursor/skills/agent-signal && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "agent-signal" agent skill from https://github.com/lobehub/lobehub/tree/canary/.agents/skills/agent-signal into .cursor/skills/agent-signal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-signal", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/lobehub/lobehub.git --path .agents/skills/agent-signal--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add lobehub/lobehub --skill agent-signal -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install lobehub/lobehub agent-signal --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lobehub/lobehub.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/agent-signal .gemini/skills/agent-signal && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "agent-signal" agent skill from https://github.com/lobehub/lobehub/tree/canary/.agents/skills/agent-signal into .gemini/skills/agent-signal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-signal", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install lobehub/lobehub agent-signalInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add lobehub/lobehub --skill agent-signal -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/lobehub/lobehub.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/agent-signal .github/skills/agent-signal && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "agent-signal" agent skill from https://github.com/lobehub/lobehub/tree/canary/.agents/skills/agent-signal into .github/skills/agent-signal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-signal", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add lobehub/lobehub --skill agent-signal -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install lobehub/lobehub agent-signal --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lobehub/lobehub.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/agent-signal .opencode/skills/agent-signal && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "agent-signal" agent skill from https://github.com/lobehub/lobehub/tree/canary/.agents/skills/agent-signal into .opencode/skills/agent-signal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-signal", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
agent-signal- GitHub stars
- 83k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 617 words
- Files
- 5 (incl. references)
- Skills in repo
- 50
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Guides building event-driven background work for LobeHub agents, with sources, signals, actions, policies, workflow handoff and deduplication.
- Works in 3 steps: Read references/architecture.md to map… → Read references/handlers.md before… → Read references/observability.md when…
- Adding a new source, signal or action handler to Agent Signal
- SKILL.md covers Start Here, Use The Right Entry Point, Core Model and Implementation Workflow, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Agent Signal separates background work from the foreground chat request through one runtime shape: a source event is interpreted into signals, signals plan actions, actions execute, and built-in result signals come back. Durable self-iteration work adds a completion branch that queues an agent execution and projects a receipt when it finishes.
The skill defines the core vocabulary. A source is a normalized fact from a producer such as a lifecycle event, user message or bot ingress; a signal is a semantic interpretation; an action is a planned side effect; a policy is an installable middleware bundle that registers handlers; and a procedure is simply the end-to-end flow for one use case. New sources, signals and actions are added only when the outside world, the system's meaning or the runtime's side effects change.
Four entry points suit different callers: emit for server-owned producers that run immediately, execute for workers that control timing, enqueue to return quickly and let Upstash Workflow process the event later, and a store-backed variant for tests and evals that should avoid ambient Redis state. Reference notes cover architecture, handlers and observability, and the handlers note is read before writing new handlers.
When your agent uses it
- Adding a new source, signal or action handler to Agent Signal
- Choosing between emitting, executing and enqueueing a source event
- Debugging an Agent Signal workflow with traces or workflow snapshots
Example prompts
- “Add a policy that turns completed agent runs into a memory action using Agent Signal.”
- “Pick the right Agent Signal entry point for a webhook producer that must return quickly.”
- “Write an eval for the signal handler that avoids Redis state.”
Requirements
- A checkout of the LobeHub repository
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Read references/architecture.md to map the package boundary, runtime queue, scope model, and async workflow handoff.
- Read references/handlers.md before writing any new policy, source handler, signal handler, or action handler.
- Read references/observability.md when you need tracing, metrics, debugging, or workflow snapshot visibility.
What it can do on your machine
Read from SKILL.md and the folder at commit 1e86647. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Agent Signal Pipeline loads about 1.7k tokens when it runs, and up to ~6.5k if it reads all its reference files. Until then it costs about 27 tokens; SKILL.md has 617 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 617 words (~1,669 tokens).
“Use this skill to implement event-driven background work for agents without coupling the work to the foreground chat request.”
- name
- agent-signal
Files
SKILL.md and 4 other files (references) in .agents/skills/agent-signal of lobehub/lobehub.
- SKILL.md
- agents/openai.yaml
- references/architecture.md
- references/handlers.md
- references/observability.md
Open the folder on GitHubat commit 1e86647
Compare with similar skills
Agent Signal Pipeline next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Agent Signal Pipeline this skilllobehub/lobehub | 83k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| FoundatioFoundatioFx/Foundatio | 2.1k | — | ~3.9k | Automated safety check: Pass | Apache-2.0 | |
| Upstash Qstashdavila7/claude-code-templates | 33k | 5 repos | ~597 | Automated safety check: Pass | MIT | |
| Bullmq Specialistsickn33/agentic-awesome-skills | 47k | 2 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Using Message Queuesancoleman/ai-design-components | 525 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Upstash Qstashsickn33/agentic-awesome-skills | 47k | 2 repos | ~349 | Automated safety check: Pass | MIT |
Similar skills
Upstash Qstash
davila7/claude-code-templates
Upstash QStash expert for serverless message queues, scheduled jobs, and reliable HTTP-based task delivery without managing infrastructure.
Bullmq Specialist
sickn33/agentic-awesome-skills
BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications.
Using Message Queues
ancoleman/ai-design-components
Async communication patterns using message brokers and task queues.
Upstash Qstash
sickn33/agentic-awesome-skills
Upstash QStash expert for serverless message queues, scheduled jobs, and reliable HTTP-based task delivery without managing infrastructure.
Understanding Funboost Concepts
ydf0509/funboost
当 AI 首次接触 funboost 或需要建立正确心智模型时使用。触发场景：AI 准备编写 funboost 代码前、对框架设计理念不清楚时、容易把 funboost 当成 Celery 时。关键词：funboost 是什么, 怎么理解, 框架设计, BoosterParams, 配置文件, push vs publish, 消费模型, 入门概念。
More from lobehub/lobehub
All 50 skills in this repoLobeHub Interactive Prototype
lobehub/lobehub
Builds single-file interactive HTML prototypes rendered with the real LobeHub UI components and written as production-style React, so they can later be split into files.
Acceptance Evidence for Deliveries
lobehub/lobehub
Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.
Git Worktree Cleanup
lobehub/lobehub
Audits stale Git worktrees and branches with a bundled script, classifies each one, and deletes only after you approve the exact candidates.
LobeHub Alint Rule Set Maintenance
lobehub/lobehub
Maintains LobeHub's model-backed alint rule set: writing rules, removing false positives against real code, deciding warn versus error and tracking token cost.
LobeHub Builtin Tool Authoring
lobehub/lobehub
Guides building LobeHub builtin agent tools, from the manifest and execution runtime to executors, chat UI renders and registry wiring.
LobeHub Data Fetching Layers
lobehub/lobehub
Explains how LobeHub client code fetches data through services, SWR store hooks and cache keys, and when to avoid useEffect fetching or duplicated state.
Related
Categories
Questions about Agent Signal Pipeline
What does Agent Signal Pipeline do?
Guides building event-driven background work for LobeHub agents, with sources, signals, actions, policies, workflow handoff and deduplication. Agent Signal separates background work from the foreground chat request through one runtime shape: a source event is interpreted into signals, signals plan actions, actions execute, and built-in result signals come back. Durable self-iteration work adds a completion branch that queues an agent execution and projects a receipt when it finishes.
When should I use Agent Signal Pipeline?
Agent Signal Pipeline fits situations like: adding a new source, signal or action handler to Agent Signal; choosing between emitting, executing and enqueueing a source event; debugging an Agent Signal workflow with traces or workflow snapshots.
How do I install Agent Signal Pipeline in Claude Code?
Run `npx skills add lobehub/lobehub --skill agent-signal -a claude-code`. Or copy the skill folder (.agents/skills/agent-signal in lobehub/lobehub) into .claude/skills/agent-signal in your project. Claude Code loads it when a task matches its description.
How do I install Agent Signal Pipeline in Codex?
Run `npx skills add lobehub/lobehub --skill agent-signal -a codex`. Or copy the skill folder (.agents/skills/agent-signal in lobehub/lobehub) into .agents/skills/agent-signal in your project. Codex loads it when a task matches its description.
Can I use Agent Signal Pipeline in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add lobehub/lobehub --skill agent-signal -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-signal, .gemini/skills/agent-signal, .github/skills/agent-signal and .opencode/skills/agent-signal in your project.
What does Agent Signal Pipeline need to run?
SKILL.md names no scripts, command-line tools or credentials: Agent Signal Pipeline is instructions for the agent only. Our summary lists: A checkout of the LobeHub repository.
Does Agent Signal Pipeline access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Agent Signal Pipeline safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Agent Signal Pipeline use?
Agent Signal Pipeline has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Agent Signal Pipeline use?
About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.9k tokens, read only when the agent opens those files.
What are the alternatives to Agent Signal Pipeline?
Skills that share tags, products or a category with Agent Signal Pipeline: Foundatio (FoundatioFx/Foundatio, 2.1k stars), Upstash Qstash (davila7/claude-code-templates, 33k stars), Bullmq Specialist (sickn33/agentic-awesome-skills, 47k stars) and Using Message Queues (ancoleman/ai-design-components, 525 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Agent Signal Pipeline?
lobehub (a GitHub organization) maintains it in lobehub/lobehub, which has 83,095 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 10, 2026.
Source: lobehub/lobehub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.