New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Signals Scout PR Follow Up

by PostHog in PostHog/posthog

Follow-up Signals scout for recently merged pull requests. An agent skill from PostHog/posthog.

OfficialCustom licenceAuto-check passedDevelopment

Install Signals Scout PR Follow Up

skills CLI
$ npx skills add PostHog/posthog --skill signals-scout-pr-follow-up -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install PostHog/posthog signals-scout-pr-follow-up --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-pr-follow-up .claude/skills/signals-scout-pr-follow-up && rm -rf skills-src

Use ~/.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/

Facts

Skill name
signals-scout-pr-follow-up
GitHub stars
40k
Token cost
~8.7k tokens
SKILL.md length
5,054 words
Files
4 (incl. references)
Skills in repo
254
Repo updated
First seen
Licence
Custom licence

At a glance

Follow-up Signals scout for recently merged pull requests. An agent skill from PostHog/posthog.

  • Works in 4 steps: Pinned checkout: the trees the harness… → GitHub warehouse source:… → Connected GitHub integration:… → …
  • Tasks that involve Pull requests
  • SKILL.md covers Quick close-out: is there…, How a run works, Disqualifiers (skip these) and MCP tools, plus 1 more section
  • Calls gh

What it does

Signals Scout PR Follow Up is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Follow-up Signals scout for recently merged pull requests. Works out whether each one has deployed, then checks the project's telemetry for whether it did what it claimed, had the impact it expected, or caused a side effect that needs a look.

Its SKILL.md is about 8.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/deploy-ladder.md`, `references/probes.md` and `references/sources.md`). Compatibility notes: PostHog Signals agent (Claude sandbox). Read-only analytics + signalscoutinternal:write (scratchpad) + signalscoutreport:write (report channel), plus the…

It sits in Development, covering Pull requests. 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…

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/signals-scout-pr-follow-up”

Requirements

  • Compatibility (from SKILL.md): PostHog Signals agent (Claude sandbox). Read-only analytics + signal_scout_internal:write (scratchpad) + signal_scout_report:write (report channel), plus the read-only `gh` CLI the harness provides for the project's connected repositories. Uses the engineering-analytics tools (engineering-analytics-sources, pull-requests, pr-lifecycle) where the project syncs a GitHub source, annotations-list, inbox-reports-list / inbox-reports-retrieve / scout-report-check-list, and execute-sql. Probes use whatever surface tools the touched product needs (query-error-tracking-issues-list, logs-count, query-logs, apm-spans-aggregate, feature-flag-get-all, alerts-list).

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Pinned checkout: the trees the harness cloned, for diffs and touched paths; the listing still comes from gh.
  2. GitHub warehouse source: engineering-analytics-sources, then pull-requests and the github_* tables.
  3. Connected GitHub integration: integrations-list, then integrations-github-repos-retrieve paged with has_more, then one update-sorted REST…
  4. PRs the inbox already knows: the pull requests linked from resolved reports (inbox-reports-list).

What it can do on your machine

Read from SKILL.md and the folder at commit c012c8d. 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:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    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) + signal_scout_report:write (report channel), plus the read-only `gh` CLI the harness provides for the project's connected repositories. Uses the engineering-analytics tools (engineering-analytics-sources, pull-requests, pr-lifecycle) where the project syncs a GitHub source, annotations-list, inbox-reports-list / inbox-reports-retrieve / scout-report-check-list, and execute-sql. Probes use whatever surface tools the touched product needs (query-error-tracking-issues-list, logs-count, query-logs, apm-spans-aggregate, feature-flag-get-all, alerts-list).

    From compatibility in the SKILL.md frontmatter.

Context cost

Signals Scout PR Follow Up loads about 8.7k tokens when it runs, and up to ~18k if it reads all its reference files. Until then it costs about 67 tokens; SKILL.md has 5,054 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~8.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~18k

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 5,054 words (~8,692 tokens).

“You follow up on pull requests after they merge. A team ships a change, mentally closes the ticket, and moves on; you are the one who comes back a day or a week later and asks three questions the author…”

— opening of SKILL.md by PostHog, Custom licence
name
signals-scout-pr-follow-up
compatibility
PostHog Signals agent (Claude sandbox). Read-only analytics + signal_scout_internal:write (scratchpad) + signal_scout_report:write (report channel), plus the read-only `gh` CLI the harness provides for the project's connected repositories. Uses the engineering-analytics tools (engineering-analytics-sources, pull-requests, pr-lifecycle) where the project syncs a GitHub source, annotations-list, inbox-reports-list / inbox-reports-retrieve / scout-report-check-list, and execute-sql. Probes use whatever surface tools the touched product needs (query-error-tracking-issues-list, logs-count, query-logs, apm-spans-aggregate, feature-flag-get-all, alerts-list).
scout-display-name
PR follow-up
metadata.owner_team
signals
metadata.scope
pr_follow_up

Read the full SKILL.md on GitHub

Files

SKILL.md and 3 other files (references) in products/signals/skills/signals-scout-pr-follow-up of PostHog/posthog.

  • SKILL.md
  • references/deploy-ladder.md
  • references/probes.md
  • references/sources.md

Open the folder on GitHubat commit c012c8d

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 8, 2026.

Compare with similar skills

Signals Scout PR Follow Up 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.

Signals Scout PR Follow Up compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Signals Scout PR Follow Up this skillPostHog/posthog40k—~8.7kAutomated safety check: PassCustom licence
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands91k—~2.4kAutomated safety check: PassMIT
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    91k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Record PR Demo

    payloadcms/payload

    A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.

    45k GitHub stars~1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from PostHog/posthog

All 254 skills in this repo

  • Authoring Log Alerts

    PostHog/posthog

    Official

    Author useful, low-noise log alerts on services in a PostHog project.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Autoresolving PR Conflicts

    PostHog/posthog

    Official

    Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…

    40k GitHub stars~4.2k tokensUpdated today
    Auto-check passed

  • Diagnosing Stacktrace Symbolication

    PostHog/posthog

    Official

    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).

    40k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Exploring Apm Traces

    PostHog/posthog

    Official

    Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.

    40k GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • Exploring LLM Traces

    PostHog/posthog

    Official

    Debug and inspect LLM/AI agent traces using PostHog's MCP tools.

    40k GitHub stars~4.4k tokensUpdated today
    Auto-check passed

  • Investigate Metric

    PostHog/posthog

    Official

    Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.

    40k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Categories

Questions about Signals Scout PR Follow Up

What does Signals Scout PR Follow Up do?

Follow-up Signals scout for recently merged pull requests. An agent skill from PostHog/posthog. Signals Scout PR Follow Up is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Follow-up Signals scout for recently merged pull requests.

When should I use Signals Scout PR Follow Up?

Signals Scout PR Follow Up fits situations like: tasks that involve Pull requests.

How do I install Signals Scout PR Follow Up in Claude Code?

Run `npx skills add PostHog/posthog --skill signals-scout-pr-follow-up -a claude-code`. Or copy the skill folder (products/signals/skills/signals-scout-pr-follow-up in PostHog/posthog) into .claude/skills/signals-scout-pr-follow-up in your project. Claude Code loads it when a task matches its description.

How do I install Signals Scout PR Follow Up in Codex?

Run `npx skills add PostHog/posthog --skill signals-scout-pr-follow-up -a codex`. Or copy the skill folder (products/signals/skills/signals-scout-pr-follow-up in PostHog/posthog) into .agents/skills/signals-scout-pr-follow-up in your project. Codex loads it when a task matches its description.

Can I use Signals Scout PR Follow Up 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-pr-follow-up -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-pr-follow-up, .gemini/skills/signals-scout-pr-follow-up, .github/skills/signals-scout-pr-follow-up and .opencode/skills/signals-scout-pr-follow-up in your project.

What does Signals Scout PR Follow Up need to run?

Going by SKILL.md and its folder, Signals Scout PR Follow Up needs the command-line tools its instructions call (gh). Compatibility (from SKILL.md): PostHog Signals agent (Claude sandbox). Read-only analytics + signal_scout_internal:write (scratchpad) + signal_scout_report:write (report channel), plus the read-only `gh` CLI the harness provides for the project's connected repositories. Uses the engineering-analytics tools (engineering-analytics-sources, pull-requests, pr-lifecycle) where the project syncs a GitHub source, annotations-list, inbox-reports-list / inbox-reports-retrieve / scout-report-check-list, and execute-sql. Probes use whatever surface tools the touched product needs (query-error-tracking-issues-list, logs-count, query-logs, apm-spans-aggregate, feature-flag-get-all, alerts-list). .

Does Signals Scout PR Follow Up access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Signals Scout PR Follow Up 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 PR Follow Up use?

Signals Scout PR Follow Up 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 PR Follow Up use?

About 8.7k tokens (SKILL.md is roughly 35k 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 9.2k tokens, read only when the agent opens those files.

What are the alternatives to Signals Scout PR Follow Up?

Skills that share tags, products or a category with Signals Scout PR Follow Up: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 91k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Signals Scout PR Follow Up?

PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,209 GitHub stars. The repository holds 254 skills in this directory. The repository was last updated on October 10, 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.