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

Debugging Local Task Agent Runs

by PostHog in PostHog/posthog

Debug the output of local PostHog task runs — the wizard cloud-run path that executes inside a Docker sandbox under the local Temporal process-task workflow (the wizard that integrates PostHog, then…

OfficialCustom licenceAuto-check: notesDevelopment

Install Debugging Local Task Agent Runs

skills CLI
$ npx skills add PostHog/posthog --skill debugging-local-task-agent-runs -a claude-code

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

GitHub CLI
$ gh skill install PostHog/posthog debugging-local-task-agent-runs --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/.agents/skills/debugging-local-task-agent-runs .claude/skills/debugging-local-task-agent-runs && 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
debugging-local-task-agent-runs
GitHub stars
40k
Token cost
~2.1k tokens
SKILL.md length
665 words
Files
1
Skills in repo
252
Repo updated
First seen
Licence
Custom licence

At a glance

Debug the output of local PostHog task runs — the wizard cloud-run path that executes inside a Docker sandbox under the local Temporal process-task workflow (the wizard that integrates PostHog, then…

  • Works in 3 steps: find the task UUID → tail live logs inside the sandbox (while… → read the durable per-run console log…
  • A local run looks stuck
  • SKILL.md covers Prerequisites: env for local…, Step 1 — find the task UUID, Step 2 — tail live logs inside… and Step 3 — read the durable…, plus 1 more section
  • Calls docker; needs LLM_GATEWAY_ANTHROPIC_API_KEY and SANDBOX_JWT_PRIVATE_KEY

What it does

Debugging Local Task Agent Runs is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Debug the output of local PostHog task runs — the wizard cloud-run path that executes inside a Docker sandbox under the local Temporal process-task workflow (the wizard that integrates PostHog, then the coding agent that commits and opens the PR). Use when a local run looks stuck, failed, or silent, or when you need to read the wizard or agent logs. Covers the .env.local keys + aifeatures intent required for cloud runs locally, finding the task UUID (docker ps, temporal CLI, Temporal UI at localhost:8081)…

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Model routing and gateways, Debugging and Containers. It works with PostHog, Docker, Cloud Run and GitHub. 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

  • A local run looks stuck
  • You need to read the wizard
  • Terms: task-sandbox
  • SANDBOXPROVIDER

Example prompts

  • “/debugging-local-task-agent-runs”

Requirements

  • Python 3
  • Docker
  • A credential in SANDBOX_JWT_PRIVATE_KEY
  • A credential in GITHUB_APP_CLIENT_SECRET

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. find the task UUID
  2. tail live logs inside the sandbox (while it's running)
  3. read the durable per-run console log (after teardown)

What it can do on your machine

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

    • docker

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

  • Network

    No URLs in SKILL.md. Its commands use docker, 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 these keys or tokens, usually read from environment variables:

    • LLM_GATEWAY_ANTHROPIC_API_KEY
    • SANDBOX_JWT_PRIVATE_KEY
    • GITHUB_APP_CLIENT_SECRET
    • GITHUB_APP_PRIVATE_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Debugging Local Task Agent Runs loads about 2.1k tokens when it runs. Until then it costs about 220 tokens; SKILL.md has 665 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~220
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:3
    ad the wizard or agent logs. Covers the `.env.local` keys + `ai_features` intent required for cloud runs locally, findin
  • NoteMentions a .env fileSKILL.md:17
    locally if **all** of these are set in `.env.local` (values shown are the local targets — never commit real secrets). I
  • NoteMentions a .env fileSKILL.md:36
    After editing `.env.local`, **restart the stack** — env is read at process start, not hot-reloaded.

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 665 words (~2,125 tokens).

“A "cloud run" of the Tasks product (e.g. the setup-wizard cloud_run endpoint) executes as the Temporal process-task workflow on the development-task-queue. Locally (SANDBOX_PROVIDER=docker) each run gets a Docker sandbox container in which two things happen in sequence:”

— opening of SKILL.md by PostHog, Custom licence
name
debugging-local-task-agent-runs

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .agents/skills/debugging-local-task-agent-runs of PostHog/posthog.

Open the folder on GitHubat commit 10f9ad7

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

Debugging Local Task Agent Runs 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.

Debugging Local Task Agent Runs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Debugging Local Task Agent Runs this skillPostHog/posthog40k—~2.1kAutomated safety check: NotesCustom licence
Debug Firewallgithub/gh-aw-firewall148—~1.2kAutomated safety check: NotesMIT
CI Act Runchewiebug/GCViewer4.6k—~2.4kAutomated safety check: NotesCustom licence
Dotnet Debuggingnovotnyllc/dotnet-artisan233—~2.1kAutomated safety check: PassMIT
Review PRmicrosoft/vscode-containers141—~900Automated safety check: PassCustom licence
Linux Vm Testnubjs/nub4.4k—~986Automated safety check: PassMIT

Similar skills

  • Debug Firewall

    github/gh-aw-firewall

    Official

    Debug the AWF firewall by inspecting Docker containers (awf-squid, awf-agent), analyzing Squid access logs, checking iptables rules, and troubleshooting blocked domains or network issues.

    148 GitHub stars~1.2k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • CI Act Run

    chewiebug/GCViewer

    Run the full build-and-deploy.yaml workflow locally via act + Docker.

    4.6k GitHub stars~2.4k tokensUpdated 3 mo ago
    DevelopmentAuto-check: notes

  • Dotnet Debugging

    novotnyllc/dotnet-artisan

    Debugs Windows and Linux/macOS applications (native, .NET/CLR, mixed-mode) with WinDbg MCP (crash dumps, !analyze, !syncblk, !dlk, !runaway, !dumpheap, !gcroot, BSOD), dotnet-dump, lldb with SOS…

    233 GitHub stars~2.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Review PR

    microsoft/vscode-containers

    Official

    Review a specific vscode-containers pull request on demand from the CLI (or any interactive agent), the way a Container Tools maintainer would.

    141 GitHub stars~900 tokensUpdated today
    DevelopmentAuto-check passed

  • Linux Vm Test

    nubjs/nub

    Run ad-hoc Nub tests and debugging probes on real local Linux guests.

    4.4k GitHub stars~986 tokensUpdated today
    DevelopmentAuto-check passed

  • Localnet

    boundless-xyz/boundless

    Start and interact with the Boundless localnet (docker compose-based local development network).

    193 GitHub stars~1.8k tokensUpdated 1 mo ago
    DevelopmentAuto-check: notes

More from PostHog/posthog

All 252 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

Works with

Categories

Questions about Debugging Local Task Agent Runs

What does Debugging Local Task Agent Runs do?

Debug the output of local PostHog task runs — the wizard cloud-run path that executes inside a Docker sandbox under the local Temporal process-task workflow (the wizard that integrates PostHog, then…. Debugging Local Task Agent Runs is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Debug the output of local PostHog task runs — the wizard cloud-run path that executes inside a Docker sandbox under the local Temporal process-task workflow (the wizard that integrates PostHog, then the coding agent that commits and opens the PR).

When should I use Debugging Local Task Agent Runs?

Debugging Local Task Agent Runs fits situations like: A local run looks stuck; you need to read the wizard; terms: task-sandbox; SANDBOXPROVIDER.

How do I install Debugging Local Task Agent Runs in Claude Code?

Run `npx skills add PostHog/posthog --skill debugging-local-task-agent-runs -a claude-code`. Or copy the skill folder (.agents/skills/debugging-local-task-agent-runs in PostHog/posthog) into .claude/skills/debugging-local-task-agent-runs in your project. Claude Code loads it when a task matches its description.

How do I install Debugging Local Task Agent Runs in Codex?

Run `npx skills add PostHog/posthog --skill debugging-local-task-agent-runs -a codex`. Or copy the skill folder (.agents/skills/debugging-local-task-agent-runs in PostHog/posthog) into .agents/skills/debugging-local-task-agent-runs in your project. Codex loads it when a task matches its description.

Can I use Debugging Local Task Agent Runs 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 debugging-local-task-agent-runs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debugging-local-task-agent-runs, .gemini/skills/debugging-local-task-agent-runs, .github/skills/debugging-local-task-agent-runs and .opencode/skills/debugging-local-task-agent-runs in your project.

What does Debugging Local Task Agent Runs need to run?

Going by SKILL.md and its folder, Debugging Local Task Agent Runs needs the command-line tools its instructions call (docker) and credentials named LLM_GATEWAY_ANTHROPIC_API_KEY, SANDBOX_JWT_PRIVATE_KEY, GITHUB_APP_CLIENT_SECRET and GITHUB_APP_PRIVATE_KEY. Our summary lists: Python 3; Docker; A credential in SANDBOX_JWT_PRIVATE_KEY; A credential in GITHUB_APP_CLIENT_SECRET.

Does Debugging Local Task Agent Runs access the network?

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

Is Debugging Local Task Agent Runs safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Debugging Local Task Agent Runs use?

Debugging Local Task Agent Runs 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 Debugging Local Task Agent Runs use?

About 2.1k tokens (SKILL.md is roughly 8.5k 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 Debugging Local Task Agent Runs?

Skills that share tags, products or a category with Debugging Local Task Agent Runs: Debug Firewall (github/gh-aw-firewall, 148 stars), CI Act Run (chewiebug/GCViewer, 4.6k stars), Dotnet Debugging (novotnyllc/dotnet-artisan, 233 stars) and Review PR (microsoft/vscode-containers, 141 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Debugging Local Task Agent Runs?

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