agentjido/jido_run/jido-signal

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Builder-oriented guidance for the upstream `jido_signal` package. Use when Codex needs to define signal schemas, route or dispatch events, bridge Jido signals to buses or transports, or review `jido_signal` boundaries versus `jido`, `jido_messaging`, and application code.

Install

npx vskill@latest install agentjido/jido_run/jido-signal

SKILL.md

Jido Signal

jido_signal is the upstream Hex package name.

Start Here

Use this skill when the task is about signal structure, validation, dispatch, or event boundaries.

Good triggers:

  • "Define the signal shape for this workflow."
  • "Bridge agent events onto PubSub, webhooks, or another bus."
  • "Turn the signal docs into a runnable example."
  • "Review whether this event contract belongs in jido_signal or in app code."

Read references/builder-notes.md before implementing when the task touches CloudEvents-like structure, signal versioning, or external delivery boundaries.

Primary Workflows

Define signal contracts
  • Start with event intent: what happened, who emitted it, and what downstream consumers must rely on.
  • Keep the public signal shape stable even if internal producers change.
  • Prefer explicit type, source, subject, and data conventions over loose maps.
Build routing and dispatch flows
  • Separate signal creation from transport delivery.
  • Keep signal validation close to the producer boundary.
  • Translate into PubSub, queues, or webhooks in adapter code, not in the signal definition itself.
Turn docs into runnable examples
  • Show one producer, one signal payload, and one consumer.
  • Include serialization or validation only when it changes the design.
  • Demonstrate failure handling for malformed or missing fields when that is central to the example.
Review boundaries
  • Keep event contracts and signaling semantics in jido_signal.
  • Keep transport-specific adapters in jido-messaging or app code.
  • Keep agent planning and execution control in jido.

Build Checklist

  • Name the event in domain language.
  • Define the minimum stable payload.
  • Choose versioning or compatibility rules before publishing widely.
  • Test serialization, validation, and consumer expectations.

Boundaries

  • Do not use this skill to design an entire broker stack.
  • Do not overload one signal type with unrelated payload shapes.
  • Do not let consumer-specific fields leak back into the core signal contract.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
44
Repository forks
20
7-day trend score
19

Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 19 May 2026, 5 months ago.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/agentjido/jido_run/jido-signal/badge)](https://verified-skill.com/skills/agentjido/jido_run/jido-signal)

Something wrong with this skill or its page? Tell us.