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

Extending Hobby Smoke Tests

by PostHog in PostHog/posthog

Design, extend, review, or debug PostHog Hobby end-to-end smoke tests in bin/hobby-ci.py and .github/workflows/ci-hobby.yml.

OfficialCustom licenceAuto-check passedTesting & QA

Install Extending Hobby Smoke Tests

skills CLI
$ npx skills add PostHog/posthog --skill extending-hobby-smoke-tests -a claude-code

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

GitHub CLI
$ gh skill install PostHog/posthog extending-hobby-smoke-tests --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/extending-hobby-smoke-tests .claude/skills/extending-hobby-smoke-tests && 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
extending-hobby-smoke-tests
GitHub stars
40k
Token cost
~1.5k tokens
SKILL.md length
775 words
Files
1
Skills in repo
254
Repo updated
First seen
Licence
Custom licence

At a glance

Design, extend, review, or debug PostHog Hobby end-to-end smoke tests in bin/hobby-ci.py and .github/workflows/ci-hobby.yml.

  • Works in 6 steps: Find an existing end-to-end or receiver… → Locate the consumer command and confirm… → Confirm the consumer is already started… → …
  • Adding an ingestion round trip
  • SKILL.md covers Decide whether the check belongs, Map the round trip before…, Build the smallest strong check and Validate from cheap to expensive, plus 2 more sections
  • Calls ruff, python3 and git

What it does

Extending Hobby Smoke Tests is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Design, extend, review, or debug PostHog Hobby end-to-end smoke tests in bin/hobby-ci.py and .github/workflows/ci-hobby.yml. Use when adding an ingestion round trip, deciding whether a product belongs in Hobby CI, changing the CI Hobby service topology or API-key scopes, or diagnosing a smoke test that captures data but cannot query it.

Its SKILL.md is about 1.5k 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 Testing & QA, covering QA and bug reports. It works with PostHog and GitHub Actions. 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

  • Adding an ingestion round trip
  • Deciding whether a product belongs in Hobby CI
  • Changing the CI Hobby service topology
  • Diagnosing a smoke test that captures data but cannot query it

Example prompts

  • “/extending-hobby-smoke-tests”

Requirements

  • Python 3
  • Docker

Workflow steps

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

  1. Find an existing end-to-end or receiver fixture for the ingest payload. Reuse its envelope and minimum valid data instead of inventing a…
  2. Locate the consumer command and confirm it exists in the released image used by docker-compose.hobby.yml.
  3. Confirm the consumer is already started by the default Hobby compose files.
  4. Confirm no unreleased or private feature flag is required.
  5. Find the supported read API and its personal API-key scope.
  6. Identify a unique value that can select only the captured object.

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:

    • ruff
    • python3
    • git

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

  • Network

    No URLs in SKILL.md. Its commands use git, 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.

Context cost

Extending Hobby Smoke Tests loads about 1.5k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 775 words of instructions outside code blocks.

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

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 775 words (~1,516 tokens).

“Treat Hobby CI as proof that a supported Hobby install works across real process boundaries. Keep each check small, strong, and limited to a stable product surface.”

— opening of SKILL.md by PostHog, Custom licence
name
extending-hobby-smoke-tests

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .agents/skills/extending-hobby-smoke-tests of PostHog/posthog.

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

Compare with similar skills

Extending Hobby Smoke Tests 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.

Extending Hobby Smoke Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Extending Hobby Smoke Tests this skillPostHog/posthog40k—~1.5kAutomated safety check: PassCustom licence
Instructor QAcognesy/instructor-php328—~1.3kAutomated safety check: PassMIT
Sdaf Quality AssuranceAzure/sap-automation146—~1.6kAutomated safety check: PassMIT
Persona CI Integrationjeremylongshore/tons-of-skills-marketplace2.8k—~1.2kAutomated safety check: PassMIT
Posthog Hello Worldjeremylongshore/tons-of-skills-marketplace2.8k—~1.5kAutomated safety check: PassMIT
Devops Pipelineluongnv89/skills131—~4.8kAutomated safety check: PassMIT

Similar skills

  • Instructor QA

    cognesy/instructor-php

    Run multi-dimensional quality assurance for InstructorPHP. An agent skill from cognesy/instructor-php.

    328 GitHub stars~1.3k tokensUpdated 2 days ago
    Testing & QAAuto-check passed

  • Sdaf Quality Assurance

    Azure/sap-automation

    Official

    Validate a deployed SDAF SAP system through the SDAF-owned QA entry points: the local quality-assurance menu and the documented Azure DevOps pipeline 13 path.

    146 GitHub stars~1.6k tokensUpdated 2 days ago
    Testing & QAAuto-check passed

  • Persona CI Integration

    jeremylongshore/tons-of-skills-marketplace

    Build Persona CI around offline contract fixtures and bounded sandbox smoke tests without production identity data.

    2.8k GitHub stars~1.2k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Posthog Hello World

    jeremylongshore/tons-of-skills-marketplace

    Verify a minimal PostHog integration with one controlled event, one identified test user, and one feature-flag fallback.

    2.8k GitHub stars~1.5k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Devops Pipeline

    luongnv89/skills

    Configure pre-commit hooks and lean GitHub Actions for shift-left quality assurance.

    131 GitHub stars~4.8k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Algolia CI Integration

    jeremylongshore/tons-of-skills-marketplace

    Build and review a bounded CI gate for Algolia index configuration and disposable-index smoke tests.

    2.8k GitHub stars~994 tokensUpdated yesterday
    Backend & APIsAuto-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

Works with

Categories

Questions about Extending Hobby Smoke Tests

What does Extending Hobby Smoke Tests do?

Design, extend, review, or debug PostHog Hobby end-to-end smoke tests in bin/hobby-ci.py and .github/workflows/ci-hobby.yml. Extending Hobby Smoke Tests is an agent skill from PostHog/posthog, published by the product's own GitHub organization.yml.

When should I use Extending Hobby Smoke Tests?

Extending Hobby Smoke Tests fits situations like: adding an ingestion round trip; deciding whether a product belongs in Hobby CI; changing the CI Hobby service topology; diagnosing a smoke test that captures data but cannot query it.

How do I install Extending Hobby Smoke Tests in Claude Code?

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

How do I install Extending Hobby Smoke Tests in Codex?

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

Can I use Extending Hobby Smoke Tests 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 extending-hobby-smoke-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/extending-hobby-smoke-tests, .gemini/skills/extending-hobby-smoke-tests, .github/skills/extending-hobby-smoke-tests and .opencode/skills/extending-hobby-smoke-tests in your project.

What does Extending Hobby Smoke Tests need to run?

Going by SKILL.md and its folder, Extending Hobby Smoke Tests needs the command-line tools its instructions call (ruff, python3 and git). Our summary lists: Python 3; Docker.

Does Extending Hobby Smoke Tests access the network?

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

Is Extending Hobby Smoke Tests 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 Extending Hobby Smoke Tests use?

Extending Hobby Smoke Tests 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 Extending Hobby Smoke Tests use?

About 1.5k tokens (SKILL.md is roughly 6.1k 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 Extending Hobby Smoke Tests?

Skills that share tags, products or a category with Extending Hobby Smoke Tests: Instructor QA (cognesy/instructor-php, 328 stars), Sdaf Quality Assurance (Azure/sap-automation, 146 stars), Persona CI Integration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Posthog Hello World (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Extending Hobby Smoke Tests?

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.