Landing Craft
EliasOulkadi/shokunin
Build conversion-optimized landing pages with CRO frameworks (Conversion Research, LIFT Model), scroll effects, A/B testing, personalization, form optimization, and Core Web Vitals (INP, LCP, CLS).
Resolves a PostHog experiment reference from natural language to a concrete experiment ID by browsing experiment-list (not feature-flag tools), with disambiguation when multiple experiments match.
Install Finding Experiments
$ npx skills add PostHog/posthog-foss --skill finding-experiments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog-foss finding-experiments --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-foss.git skills-src && mkdir -p .claude/skills && cp -r skills-src/products/experiments/skills/finding-experiments .claude/skills/finding-experiments && 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 "finding-experiments" agent skill from https://github.com/PostHog/posthog-foss/tree/master/products/experiments/skills/finding-experiments into .claude/skills/finding-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-experiments", 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-foss/tree/master/products/experiments/skills/finding-experimentsType 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-foss --skill finding-experiments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog-foss finding-experiments --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .agents/skills && cp -r skills-src/products/experiments/skills/finding-experiments .agents/skills/finding-experiments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "finding-experiments" agent skill from https://github.com/PostHog/posthog-foss/tree/master/products/experiments/skills/finding-experiments into .agents/skills/finding-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-experiments", 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-foss --skill finding-experiments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog-foss finding-experiments --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/products/experiments/skills/finding-experiments .cursor/skills/finding-experiments && 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 "finding-experiments" agent skill from https://github.com/PostHog/posthog-foss/tree/master/products/experiments/skills/finding-experiments into .cursor/skills/finding-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-experiments", 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-foss.git --path products/experiments/skills/finding-experiments--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-foss --skill finding-experiments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog-foss finding-experiments --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/products/experiments/skills/finding-experiments .gemini/skills/finding-experiments && 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 "finding-experiments" agent skill from https://github.com/PostHog/posthog-foss/tree/master/products/experiments/skills/finding-experiments into .gemini/skills/finding-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-experiments", 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-foss finding-experimentsInstalls 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-foss --skill finding-experiments -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .github/skills && cp -r skills-src/products/experiments/skills/finding-experiments .github/skills/finding-experiments && 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 "finding-experiments" agent skill from https://github.com/PostHog/posthog-foss/tree/master/products/experiments/skills/finding-experiments into .github/skills/finding-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-experiments", 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-foss --skill finding-experiments -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-foss finding-experiments --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/products/experiments/skills/finding-experiments .opencode/skills/finding-experiments && 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 "finding-experiments" agent skill from https://github.com/PostHog/posthog-foss/tree/master/products/experiments/skills/finding-experiments into .opencode/skills/finding-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-experiments", 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
finding-experiments- GitHub stars
- 721
- Token cost
- ~783 tokens
- SKILL.md length
- 302 words
- Files
- 1
- Skills in repo
- 213
- Repo updated
- First seen
- Licence
- MIT
At a glance
Resolves a PostHog experiment reference from natural language to a concrete experiment ID by browsing experiment-list (not feature-flag tools), with disambiguation when multiple experiments match.
- Quotes an experiment (split test demo
- SKILL.md covers How to find an experiment, After finding matches, Get full details if needed and Examples, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The File engagement boost experiment
What it does
Finding Experiments is an agent skill from PostHog/posthog-foss, published by the product's own GitHub organization. Resolves a PostHog experiment reference from natural language to a concrete experiment ID by browsing experiment-list (not feature-flag tools), with disambiguation when multiple experiments match. Use when the user names or quotes an experiment ("split test demo", "the File engagement boost experiment", "onboarding retention test", "landing page hero experiment", "pricing experiment"), describes it loosely ("the signup experiment", "my pricing test", "the one with the new checkout"), uses a relative reference…
Its SKILL.md is about 780 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 Frontend & Design, covering Landing pages and A/B testing. It works with PostHog. The repository describes itself as: PostHog FOSS is a read-only mirror of PostHog, with all proprietary code removed. NOTE: This repo is synced automatically from the main PostHog repo. Please raise any issues and… The licence is MIT.
When your agent uses it
- Quotes an experiment (split test demo
- The File engagement boost experiment
- Onboarding retention test
- Landing page hero experiment
Example prompts
- “split test demo”
- “the File engagement boost experiment”
- “onboarding retention test”
- “/finding-experiments”
What it can do on your machine
Read from SKILL.md and the folder at commit 2c48221. 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.
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
Finding Experiments loads about 783 tokens when it runs. Until then it costs about 188 tokens; SKILL.md has 302 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
The full file from PostHog/posthog-foss at commit 2c48221, republished under its MIT licence (© PostHog). 302 words, ~783 tokens.
Download SKILL.mdSave it as
.claude/skills/finding-experiments/SKILL.md (or your agent's skills folder).- name
- finding-experiments
- description
- Resolves a PostHog experiment reference from natural language to a concrete experiment ID by browsing `experiment-list` (not feature-flag tools), with disambiguation when multiple experiments match. Use when the user names or quotes an experiment ("split test demo", "the File engagement boost experiment", "onboarding retention test", "landing page hero experiment", "pricing experiment"), describes it loosely ("the signup experiment", "my pricing test", "the one with the new checkout"), uses a relative reference ("latest", "most recent", "the one I created yesterday"), filters by status (running, draft, paused, exposure frozen, stopped, archived), or otherwise refers to an experiment by anything other than its concrete ID.
Finding experiments
Users refer to experiments by name, description, or relative references — not by ID. This skill resolves natural language references to concrete experiment IDs.
How to find an experiment
Use the experiment-list tool from the Posthog-local MCP server.
IMPORTANT: Do NOT use feature-flag-get-all or any feature flag tool to find
experiments. Use the dedicated experiment list tool: experiment-list.
This tool returns experiments with their id, name, status, feature_flag_key, start_date, end_date, and created_at. Browse the returned list to find the experiment matching the user's reference:
- By name: scan the
namefield for matches - By recency: results are ordered newest first by default
- By status: match the
statusfield (draft, running, paused, exposure_frozen, stopped) - By flag key: skip the list and call
experiment-get-by-flag-keywith the key. It returns the full experiment, orfound: falsewith areason.no_flagandno_experimentmean the key is free, so this is also the existence check to run beforeexperiment-create.ambiguousmeans several experiments share the flag and none is the single live one: show thecandidatesand pick one withexperiment-getrather than creating another.
After finding matches
- Exactly one match: Use it. Confirm with the user by name before destructive actions (delete, ship, end).
- Multiple matches: List them with name, status, and creation date. Ask the user to pick.
- No matches: Tell the user. Suggest checking archived experiments or different terms.
Get full details if needed
After resolving to an ID, call experiment-get for the full object (metrics, flag details, parameters).
Examples
User: "pause my signup experiment"
Agent:
1. Calls experiment-list
2. Scans results, finds "New signup process" (ID: 1371, status: running)
3. Proceeds to pause experiment 1371When NOT to search
- You already have the experiment ID from earlier in the conversation
- The user just created the experiment — you have the ID from the create response
- The user provided the ID directly
Related skills
managing-experiment-lifecycle— act on the experiment once you've resolved its IDdiagnosing-experiment-health— investigate the experiment you found
© PostHog, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in products/experiments/skills/finding-experiments of PostHog/posthog-foss.
Open the folder on GitHubat commit 2c48221
Compare with similar skills
Finding Experiments 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 |
|---|---|---|---|---|---|---|
| Finding Experiments this skillPostHog/posthog-foss | 721 | — | ~783 | Automated safety check: Pass | MIT | |
| Landing CraftEliasOulkadi/shokunin | 114 | — | ~4.5k | Automated safety check: Pass | MIT | |
| Htmldropooiyeefei/ccc | 494 | — | ~5.2k | Automated safety check: Warn | MIT | |
| Ecommerce Landing Pagenexscope-ai/eCommerce-Skills | 1.1k | — | ~617 | Automated safety check: Pass | MIT | |
| Shopify Landing Page Buildernexscope-ai/eCommerce-Skills | 1.1k | — | ~476 | Automated safety check: Pass | MIT | |
| Product Appeal Analyzercuriositech/some_claude_skills | 243 | 1 repos | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
Htmldrop
ooiyeefei/ccc
Reach for this skill when an HTML artifact — report, deck, brief, mockup, dashboard, proposal, spec, or landing page, whether the user already has it or you just generated it — needs to reach other…
Ecommerce Landing Page
nexscope-ai/eCommerce-Skills
Audit and optimize e-commerce landing pages for conversion. An agent skill from nexscope-ai/eCommerce-Skills.
Shopify Landing Page Builder
nexscope-ai/eCommerce-Skills
High-converting landing pages — campaign pages, collection pages, seasonal promos, A/B testing
Product Appeal Analyzer
curiositech/some_claude_skills
Evaluate product desirability, market positioning, and emotional resonance—the complement to friction analysis.
Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
More from PostHog/posthog-foss
All 213 skills in this repo- Official
Authoring Log Alerts
PostHog/posthog-foss
Author useful, low-noise log alerts on services in a PostHog project.
- Official
Autoresolving PR Conflicts
PostHog/posthog-foss
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-foss
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-foss
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.
- Official
Exploring LLM Traces
PostHog/posthog-foss
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
- Official
Investigate Metric
PostHog/posthog-foss
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Related
Works with
Categories
Questions about Finding Experiments
What does Finding Experiments do?
Resolves a PostHog experiment reference from natural language to a concrete experiment ID by browsing experiment-list (not feature-flag tools), with disambiguation when multiple experiments match. Finding Experiments is an agent skill from PostHog/posthog-foss, published by the product's own GitHub organization. Resolves a PostHog experiment reference from natural language to a concrete experiment ID by browsing experiment-list (not feature-flag tools), with disambiguation when multiple experiments match.
When should I use Finding Experiments?
Finding Experiments fits situations like: quotes an experiment (split test demo; the File engagement boost experiment; onboarding retention test; landing page hero experiment.
How do I install Finding Experiments in Claude Code?
Run `npx skills add PostHog/posthog-foss --skill finding-experiments -a claude-code`. Or copy the skill folder (products/experiments/skills/finding-experiments in PostHog/posthog-foss) into .claude/skills/finding-experiments in your project. Claude Code loads it when a task matches its description.
How do I install Finding Experiments in Codex?
Run `npx skills add PostHog/posthog-foss --skill finding-experiments -a codex`. Or copy the skill folder (products/experiments/skills/finding-experiments in PostHog/posthog-foss) into .agents/skills/finding-experiments in your project. Codex loads it when a task matches its description.
Can I use Finding Experiments 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-foss --skill finding-experiments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/finding-experiments, .gemini/skills/finding-experiments, .github/skills/finding-experiments and .opencode/skills/finding-experiments in your project.
What does Finding Experiments need to run?
SKILL.md names no scripts, command-line tools or credentials: Finding Experiments is instructions for the agent only.
Does Finding Experiments 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 Finding Experiments 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 Finding Experiments use?
Finding Experiments is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Finding Experiments use?
About 783 tokens (SKILL.md is roughly 3.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 Finding Experiments?
Skills that share tags, products or a category with Finding Experiments: Landing Craft (EliasOulkadi/shokunin, 114 stars), Htmldrop (ooiyeefei/ccc, 494 stars), Ecommerce Landing Page (nexscope-ai/eCommerce-Skills, 1.1k stars) and Shopify Landing Page Builder (nexscope-ai/eCommerce-Skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Finding Experiments?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog-foss, which has 721 GitHub stars. The repository holds 213 skills in this directory. The repository was last updated on October 7, 2026.
Source: PostHog/posthog-foss on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.