Opik Analytics Instrumentation
comet-ml/opik
Shows how to add product analytics events to Opik's frontend, Java backend and Python SDK, all reporting through Segment to PostHog with an opik_ name prefix.
Signals scout for PostHog workflows. An agent skill from PostHog/posthog.
OfficialCustom licenceAuto-check passed
Install Signals Scout Workflows
$ npx skills add PostHog/posthog --skill signals-scout-workflows -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog signals-scout-workflows --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/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/products/signals/skills/signals-scout-workflows .claude/skills/signals-scout-workflows && 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-scout-workflows" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/signals-scout-workflows into .claude/skills/signals-scout-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signals-scout-workflows", 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/PostHog/posthog/tree/master/products/signals/skills/signals-scout-workflowsType 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 PostHog/posthog --skill signals-scout-workflows -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog signals-scout-workflows --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/products/signals/skills/signals-scout-workflows .agents/skills/signals-scout-workflows && 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-scout-workflows" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/signals-scout-workflows into .agents/skills/signals-scout-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signals-scout-workflows", 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 PostHog/posthog --skill signals-scout-workflows -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog signals-scout-workflows --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/products/signals/skills/signals-scout-workflows .cursor/skills/signals-scout-workflows && 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-scout-workflows" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/signals-scout-workflows into .cursor/skills/signals-scout-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signals-scout-workflows", 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/PostHog/posthog.git --path products/signals/skills/signals-scout-workflows--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 PostHog/posthog --skill signals-scout-workflows -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog signals-scout-workflows --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/products/signals/skills/signals-scout-workflows .gemini/skills/signals-scout-workflows && 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-scout-workflows" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/signals-scout-workflows into .gemini/skills/signals-scout-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signals-scout-workflows", 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 PostHog/posthog signals-scout-workflowsInstalls 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 PostHog/posthog --skill signals-scout-workflows -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .github/skills && cp -r skills-src/products/signals/skills/signals-scout-workflows .github/skills/signals-scout-workflows && 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-scout-workflows" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/signals-scout-workflows into .github/skills/signals-scout-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signals-scout-workflows", 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 PostHog/posthog --skill signals-scout-workflows -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PostHog/posthog signals-scout-workflows --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/products/signals/skills/signals-scout-workflows .opencode/skills/signals-scout-workflows && 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-scout-workflows" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/signals-scout-workflows into .opencode/skills/signals-scout-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signals-scout-workflows", 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-scout-workflows- GitHub stars
- 40k
- Token cost
- ~3.7k tokens
- SKILL.md length
- 2,031 words
- Files
- 1
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Signals scout for PostHog workflows. An agent skill from PostHog/posthog.
- SKILL.md covers Quick close-out: is anyone…, How a run works, Why this scout files no reports and Disqualifiers, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Signals Scout Workflows is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Signals scout for PostHog workflows. Looks at the workflows whose owner asked for suggestions, reads each email step's per-version delivery metrics, and proposes one concrete change a person can approve, filed through the workflows suggestions API. It files no report and emits no signal: the suggestion on the workflow page is the output.
Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: PostHog Signals agent (Claude sandbox). Read-only analytics + signalscoutinternal:write (scratchpad) + hogflowproposal:write (declared below, granted to this…
It works with PostHog. The repository describes itself as: :hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error…
Example prompts
- “Use the signals-scout-workflows skill to signal scout for PostHog workflows. An agent skill from PostHog/posthog”
- “/signals-scout-workflows”
Requirements
- Compatibility (from SKILL.md): PostHog Signals agent (Claude sandbox). Read-only analytics + signal_scout_internal:write (scratchpad) + hog_flow_proposal:write (declared below, granted to this scout only), plus the workflows tools in the MCP tools section. The suggestion tools exist only on projects with the `self-optimising-workflows` flag; hold the scout back from a team with the `signals-scout` flag's `withheld_skills` until the project has it. Deliberately on neither output channel - see "Why this scout files no reports".
What it can do on your machine
Read from SKILL.md and the folder at commit 812e5c6. 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 (its code samples are json).
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.
Compatibility
PostHog Signals agent (Claude sandbox). Read-only analytics + signal_scout_internal:write (scratchpad) + hog_flow_proposal:write (declared below, granted to this scout only), plus the workflows tools in the MCP tools section. The suggestion tools exist only on projects with the `self-optimising-workflows` flag; hold the scout back from a team with the `signals-scout` flag's `withheld_skills` until the project has it. Deliberately on neither output channel - see "Why this scout files no reports".
From compatibility in the SKILL.md frontmatter.
Context cost
Signals Scout Workflows loads about 3.7k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 2,031 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 2,031 words (~3,676 tokens).
“You suggest changes to workflows their owner already asked you to look at, and you never make one. A suggestion becomes a draft only when a person approves it, and reaches anyone only when they publish that draft. That gate…”
- name
- signals-scout-workflows
- compatibility
- PostHog Signals agent (Claude sandbox). Read-only analytics + signal_scout_internal:write (scratchpad) + hog_flow_proposal:write (declared below, granted to this scout only), plus the workflows tools in the MCP tools section. The suggestion tools exist only on projects with the `self-optimising-workflows` flag; hold the scout back from a team with the `signals-scout` flag's `withheld_skills` until the project has it. Deliberately on neither output channel - see "Why this scout files no reports".
- scout-display-name
- Workflows
- metadata.owner_team
- workflows
- metadata.scope
- workflows
Files
Just SKILL.md in products/signals/skills/signals-scout-workflows of PostHog/posthog.
Open the folder on GitHubat commit 812e5c6
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in PostHog/posthog, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Signals Scout Workflows 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 Scout Workflows this skillPostHog/posthog | 40k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Opik Analytics Instrumentationcomet-ml/opik | 22k | — | ~4.4k | Automated safety check: Pass | Apache-2.0 | |
| C15tc15t/c15t | 1.9k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Define Feature Flagmacro-inc/macro | 4.6k | — | ~780 | Automated safety check: Pass | AGPL-3.0 | |
| Soku CLIAbout-Intelligence/soku-cli | 305 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Compare Array Bundle SizePostHog/posthog-js | 628 | — | ~599 | Automated safety check: Pass | Custom licence |
Similar skills
C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Define Feature Flag
macro-inc/macro
Define a frontend feature flag with defineFlag and wire its readers.
Soku CLI
About-Intelligence/soku-cli
Guides an agent through the soku command line tool for ads, GA4 and PostHog data reads, ads writes, SEO hosting, automations, files and skill management.
- Official
Compare Array Bundle Size
PostHog/posthog-js
Quickly compare the posthog-js array.js bundle size in the current working tree against a git baseline using the repository's esbuild proxy.
Telemetry Analytics
OpenHands/OpenHands
This skill should be used when the user asks to "add tracking", "add a PostHog event", "change telemetry consent", "instrument onboarding", "debug analytics", or changes telemetry.ts…
More from PostHog/posthog
All 252 skills in this repo- Official
Authoring Log Alerts
PostHog/posthog
Author useful, low-noise log alerts on services in a PostHog project.
- Official
Autoresolving PR Conflicts
PostHog/posthog
Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…
- Official
Diagnosing Stacktrace Symbolication
PostHog/posthog
Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).
- Official
Exploring Apm Traces
PostHog/posthog
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.
- Official
Exploring LLM Traces
PostHog/posthog
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
- Official
Investigate Metric
PostHog/posthog
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Related
Works with
Questions about Signals Scout Workflows
What does Signals Scout Workflows do?
Signals scout for PostHog workflows. An agent skill from PostHog/posthog. Signals Scout Workflows is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Signals scout for PostHog workflows.
How do I install Signals Scout Workflows in Claude Code?
Run `npx skills add PostHog/posthog --skill signals-scout-workflows -a claude-code`. Or copy the skill folder (products/signals/skills/signals-scout-workflows in PostHog/posthog) into .claude/skills/signals-scout-workflows in your project. Claude Code loads it when a task matches its description.
How do I install Signals Scout Workflows in Codex?
Run `npx skills add PostHog/posthog --skill signals-scout-workflows -a codex`. Or copy the skill folder (products/signals/skills/signals-scout-workflows in PostHog/posthog) into .agents/skills/signals-scout-workflows in your project. Codex loads it when a task matches its description.
Can I use Signals Scout Workflows 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 PostHog/posthog --skill signals-scout-workflows -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-scout-workflows, .gemini/skills/signals-scout-workflows, .github/skills/signals-scout-workflows and .opencode/skills/signals-scout-workflows in your project.
What does Signals Scout Workflows need to run?
SKILL.md names no scripts, command-line tools or credentials: Signals Scout Workflows is instructions for the agent only. Compatibility (from SKILL.md): PostHog Signals agent (Claude sandbox). Read-only analytics + signal_scout_internal:write (scratchpad) + hog_flow_proposal:write (declared below, granted to this scout only), plus the workflows tools in the MCP tools section. The suggestion tools exist only on projects with the `self-optimising-workflows` flag; hold the scout back from a team with the `signals-scout` flag's `withheld_skills` until the project has it. Deliberately on neither output channel - see "Why this scout files no reports". .
Does Signals Scout Workflows 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 Scout Workflows 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 Scout Workflows use?
Signals Scout Workflows 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 Signals Scout Workflows use?
About 3.7k tokens (SKILL.md is roughly 15k 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 Scout Workflows?
Skills that share tags, products or a category with Signals Scout Workflows: Opik Analytics Instrumentation (comet-ml/opik, 22k stars), C15t (c15t/c15t, 1.9k stars), Define Feature Flag (macro-inc/macro, 4.6k stars) and Soku CLI (About-Intelligence/soku-cli, 305 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Signals Scout Workflows?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,200 GitHub stars. The repository holds 252 skills in this directory. The repository was last updated on October 9, 2026.
Source: PostHog/posthog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.