Signals Scout Anomaly Detection
PostHog/posthog
Signals scout that watches the project's most-viewed dashboards and insights for anomalies — bursts, drops, flat-lines, and trend breaks — against each insight's own seasonality-matched baseline.
Clay Signals — watches that detect real-world changes (job changes, new hires, promotions, funding news, job postings, topic intent) and write them as events onto a table or an audience.
No licenceAuto-check passed
Install Signals
$ npx skills add clay-run/agent-plugins --skill signals -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install clay-run/agent-plugins signals --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/clay-run/agent-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/clay/skills/signals .claude/skills/signals && 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 "signals" agent skill from https://github.com/clay-run/agent-plugins/tree/main/clay/skills/signals into .claude/skills/signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signals", 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/clay-run/agent-plugins/tree/main/clay/skills/signalsType 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 clay-run/agent-plugins --skill signals -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install clay-run/agent-plugins signals --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/clay-run/agent-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/clay/skills/signals .agents/skills/signals && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "signals" agent skill from https://github.com/clay-run/agent-plugins/tree/main/clay/skills/signals into .agents/skills/signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signals", 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 clay-run/agent-plugins --skill signals -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install clay-run/agent-plugins signals --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/clay-run/agent-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/clay/skills/signals .cursor/skills/signals && 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 "signals" agent skill from https://github.com/clay-run/agent-plugins/tree/main/clay/skills/signals into .cursor/skills/signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signals", 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/clay-run/agent-plugins.git --path clay/skills/signals--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 clay-run/agent-plugins --skill signals -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install clay-run/agent-plugins signals --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/clay-run/agent-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/clay/skills/signals .gemini/skills/signals && 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 "signals" agent skill from https://github.com/clay-run/agent-plugins/tree/main/clay/skills/signals into .gemini/skills/signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signals", 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 clay-run/agent-plugins signalsInstalls 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 clay-run/agent-plugins --skill signals -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/clay-run/agent-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/clay/skills/signals .github/skills/signals && 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 "signals" agent skill from https://github.com/clay-run/agent-plugins/tree/main/clay/skills/signals into .github/skills/signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signals", 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 clay-run/agent-plugins --skill signals -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install clay-run/agent-plugins signals --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/clay-run/agent-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/clay/skills/signals .opencode/skills/signals && 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 "signals" agent skill from https://github.com/clay-run/agent-plugins/tree/main/clay/skills/signals into .opencode/skills/signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signals", 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
signals- GitHub stars
- 130
- Token cost
- ~8.6k tokens
- SKILL.md length
- 4,959 words
- Files
- 1
- Skills in repo
- 35
- Repo updated
- First seen
- Licence
- None found
At a glance
Clay Signals — watches that detect real-world changes (job changes, new hires, promotions, funding news, job postings, topic intent) and write them as events onto a table or an audience.
- Works in 5 steps: runStatus. Only Active and Preview run.… → filter, from get. Job change and… → error, from get. Populated when… → …
- Any request about a workspaces signals: which ones exist
- SKILL.md covers The commands, Creating and updating a signal, input is not destinationTable and Signals on audiences, plus 7 more sections
- Calls jq
What it does
Signals is an agent skill from clay-run/agent-plugins. Clay Signals — watches that detect real-world changes (job changes, new hires, promotions, funding news, job postings, topic intent) and write them as events onto a table or an audience. Use for any request about a workspace's signals: which ones exist, what one watches or writes to, whether one is running, turning one on or off, and why one is or is not producing events.
Its SKILL.md is about 8.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Build with Clay in your AI coding agent - skills, MCP tools, and the clay CLI for Claude Code, Codex, and Cursor. Search companies and people, run enrichment routines, and query…
When your agent uses it
- Any request about a workspaces signals: which ones exist
- What one watches
- Whether one is running
- Is not producing events
Example prompts
- “/signals”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- runStatus. Only Active and Preview run. Testing, Paused, and
- filter, from get. Job change and promotion signals are created with a
- error, from get. Populated when runStatus is Errored.
- schedule, from get. Cadences are often weekly or monthly, so a signal
- Where the output goes. An audiences-based signal writes activities onto
What it can do on your machine
Read from SKILL.md and the folder at commit a813258. 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
Shell commands in SKILL.md call:
jq
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
Signals loads about 8.6k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 4,959 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 4,959 words (~8,596 tokens).
“A signal watches a set of records and emits an event when something changes in the real world — someone changes job, a company posts a role or raises a round. It has two halves, and telling them apart is…”
- name
- signals
Files
Just SKILL.md in clay/skills/signals of clay-run/agent-plugins.
Open the folder on GitHubat commit a813258
Compare with similar skills
Signals 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 |
|---|---|---|---|---|---|---|
| Signals this skillclay-run/agent-plugins | 130 | — | ~8.6k | Automated safety check: Pass | None | |
| Signals Scout Anomaly DetectionPostHog/posthog | 40k | — | ~4.6k | Automated safety check: Pass | Custom licence | |
| Detecting Pv Signalsmaziyarpanahi/openmed | 5.5k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Trader Signalruvnet/ruflo | 74k | — | ~605 | Automated safety check: Notes | MIT | |
| Detection SignalsLinXiaoTao/FuckClaude | 1k | — | ~716 | Automated safety check: Pass | MIT | |
| SignalsPostHog/posthog | 40k | — | ~4.3k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Detecting Pv Signals
maziyarpanahi/openmed
Computes disproportionality signals — PRR, ROR, EBGM, and IC (BCPNN) — over FAERS / OpenFDA drug-event data to flag potential safety signals.
Trader Signal
ruvnet/ruflo
Generate trading signals using npx neural-trader anomaly detection engine with Z-score scoring and neural prediction
Detection Signals
LinXiaoTao/FuckClaude
Add, adjust or remove "China user" detection signals in the FuckClaude project (browser scan + /api/check).
- Official
Signals
PostHog/posthog
How to query the documentembeddings table for raw signal data using HogQL.
Clay Hello World
jeremylongshore/tons-of-skills-marketplace
Send your first record to Clay and get enriched data back. An agent skill from jeremylongshore/tons-of-skills-marketplace.
More from clay-run/agent-plugins
All 35 skills in this repoAd Syncs
clay-run/agent-plugins
Clay ad syncs — push an audience segment to ad platforms (LinkedIn, Meta, Google, Bing, Reddit, Vibe) as a custom audience.
Clay
clay-run/agent-plugins
Clay — start here. An agent skill from clay-run/agent-plugins.
CLI
clay-run/agent-plugins
Clay CLI — the primary scripting surface (JSON output, typed errors).
Credits Quotas Plans
clay-run/agent-plugins
A skill your agent uses when the user asks about credits, quotas, or plan limits, or verified usage requires a significant-spend warning or reveals a limit.
Routines
clay-run/agent-plugins
Clay routines — create a routine from an existing function/workflow, then run a saved routine that exists in this workspace.
Schedules
clay-run/agent-plugins
GTM Agent schedules — recurring prompts the GTM Agent runs on a cadence, each occurrence starting a fresh agent task.
Questions about Signals
What does Signals do?
Clay Signals — watches that detect real-world changes (job changes, new hires, promotions, funding news, job postings, topic intent) and write them as events onto a table or an audience. Signals is an agent skill from clay-run/agent-plugins. Clay Signals — watches that detect real-world changes (job changes, new hires, promotions, funding news, job postings, topic intent) and write them as events onto a table or an audience.
When should I use Signals?
Signals fits situations like: any request about a workspaces signals: which ones exist; what one watches; whether one is running; is not producing events.
How do I install Signals in Claude Code?
Run `npx skills add clay-run/agent-plugins --skill signals -a claude-code`. Or copy the skill folder (clay/skills/signals in clay-run/agent-plugins) into .claude/skills/signals in your project. Claude Code loads it when a task matches its description.
How do I install Signals in Codex?
Run `npx skills add clay-run/agent-plugins --skill signals -a codex`. Or copy the skill folder (clay/skills/signals in clay-run/agent-plugins) into .agents/skills/signals in your project. Codex loads it when a task matches its description.
Can I use Signals 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 clay-run/agent-plugins --skill signals -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/signals, .gemini/skills/signals, .github/skills/signals and .opencode/skills/signals in your project.
What does Signals need to run?
Going by SKILL.md and its folder, Signals needs the command-line tools its instructions call (jq).
Does Signals 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 Signals 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 Signals use?
No licence was found for Signals or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Signals use?
About 8.6k tokens (SKILL.md is roughly 34k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Signals?
Skills that share tags, products or a category with Signals: Signals Scout Anomaly Detection (PostHog/posthog, 40k stars), Detecting Pv Signals (maziyarpanahi/openmed, 5.5k stars), Trader Signal (ruvnet/ruflo, 74k stars) and Detection Signals (LinXiaoTao/FuckClaude, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Signals?
clay-run (a GitHub organization) maintains it in clay-run/agent-plugins, which has 130 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 7, 2026.
Source: clay-run/agent-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.