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.
Add or extend language and framework support in the PostHog wizard, including detection, framework configuration, registration, and matching context-mill content.
OfficialMITAuto-check passed
Install Adding Framework Support
$ npx skills add PostHog/wizard --skill adding-framework-support -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/wizard adding-framework-support --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/wizard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/adding-framework-support .claude/skills/adding-framework-support && 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 "adding-framework-support" agent skill from https://github.com/PostHog/wizard/tree/main/.claude/skills/adding-framework-support into .claude/skills/adding-framework-support/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-framework-support", 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/wizard/tree/main/.claude/skills/adding-framework-supportType 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/wizard --skill adding-framework-support -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/wizard adding-framework-support --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/wizard.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/adding-framework-support .agents/skills/adding-framework-support && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "adding-framework-support" agent skill from https://github.com/PostHog/wizard/tree/main/.claude/skills/adding-framework-support into .agents/skills/adding-framework-support/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-framework-support", 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/wizard --skill adding-framework-support -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/wizard adding-framework-support --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/wizard.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/adding-framework-support .cursor/skills/adding-framework-support && 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 "adding-framework-support" agent skill from https://github.com/PostHog/wizard/tree/main/.claude/skills/adding-framework-support into .cursor/skills/adding-framework-support/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-framework-support", 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/wizard.git --path .claude/skills/adding-framework-support--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/wizard --skill adding-framework-support -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/wizard adding-framework-support --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/wizard.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/adding-framework-support .gemini/skills/adding-framework-support && 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 "adding-framework-support" agent skill from https://github.com/PostHog/wizard/tree/main/.claude/skills/adding-framework-support into .gemini/skills/adding-framework-support/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-framework-support", 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/wizard adding-framework-supportInstalls 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/wizard --skill adding-framework-support -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PostHog/wizard.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/adding-framework-support .github/skills/adding-framework-support && 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 "adding-framework-support" agent skill from https://github.com/PostHog/wizard/tree/main/.claude/skills/adding-framework-support into .github/skills/adding-framework-support/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-framework-support", 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/wizard --skill adding-framework-support -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/wizard adding-framework-support --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/wizard.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/adding-framework-support .opencode/skills/adding-framework-support && 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 "adding-framework-support" agent skill from https://github.com/PostHog/wizard/tree/main/.claude/skills/adding-framework-support into .opencode/skills/adding-framework-support/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-framework-support", 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
adding-framework-support- GitHub stars
- 197
- Token cost
- ~1.5k tokens
- SKILL.md length
- 508 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Add or extend language and framework support in the PostHog wizard, including detection, framework configuration, registration, and matching context-mill content.
- Works in 3 steps: Add the integration to Integration. Its → Add the config under… → Import the config into
- SKILL.md covers Extend the framework…, Detection and examples, Complete the content side and Verify the changed behavior
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Adding Framework Support is an agent skill from PostHog/wizard, published by the product's own GitHub organization. Add or extend language and framework support in the PostHog wizard, including detection, framework configuration, registration, and matching context-mill content.
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. Compatibility notes: Designed for coding agents working on the PostHog wizard codebase.
It works with PostHog. The repository describes itself as: Quickly add PostHog to your project using the setup wizard ✨. The licence is MIT.
Example prompts
- “/adding-framework-support”
Requirements
- Python 3
- Compatibility (from SKILL.md): Designed for coding agents working on the PostHog wizard codebase.
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Add the integration to Integration. Its
- Add the config under src/programs/frameworks//-wizard-agent.ts. Use a
- Import the config into
What it can do on your machine
Read from SKILL.md and the folder at commit 08c70dd. 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
Links to these hosts (documentation or services it may open):
github.com
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
Designed for coding agents working on the PostHog wizard codebase.
From compatibility in the SKILL.md frontmatter.
Context cost
Adding Framework Support loads about 1.5k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 508 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/wizard at commit 08c70dd, republished under its MIT licence (© PostHog). 508 words, ~1,475 tokens.
Download SKILL.mdSave it as
.claude/skills/adding-framework-support/SKILL.md (or your agent's skills folder).- name
- adding-framework-support
- description
- Add or extend language and framework support in the PostHog wizard, including detection, framework configuration, registration, and matching context-mill content.
- compatibility
- Designed for coding agents working on the PostHog wizard codebase.
- metadata.author
- posthog
- metadata.version
- 2.1
Adding Framework Support
Read wizard-development for the shared design policy and gateway contract. New agent work uses Pi and prefers the orchestrator; adding a framework extends the integration program without creating its own runner or changing existing routing defaults.
Extend the framework configuration
Start with FrameworkConfig and a nearby example under src/programs/frameworks. Framework-specific detection, context, environment conventions, and UI metadata belong here. Integration instructions and examples belong in context-mill.
- Add the integration to Integration. Its order controls first-match detection and the framework picker. Keep specific frameworks before language fallbacks and generic Node last; preserve the overlap rules in the detection checks.
- Add the config under
src/programs/frameworks/<name>/<name>-wizard-agent.ts. Use atypefor framework context so it satisfiesRecord<string, unknown>. Export the config; the integration program already supplies execution. - Import the config into
FRAMEWORK_REGISTRY.
metadata.nameis the framework's label once detection or the picker settles it.
Read the current interface for the complete required fields. In particular,
detection.detectPackageManager is required: reuse an adapter from
package-manager detection. Use
metadata.setup.questions for unresolved project variants; metadata.gatherContext
collects framework context. When the gathered context names a more specific variant,
return its label from metadata.getDetectedFrameworkLabel(context); detection sets
the label through its context. Framework configs never use the UI. Optional notices
and extra MCP servers also belong in metadata.
Use usesPackageJson: false for frameworks without a package.json dependency.
Their required getVersion callback can return undefined. Minimum-version
checking requires both minimumVersion and getInstalledVersion; unknown
versions pass. Context detection
returns unsupported-version data for the integration UI rather than aborting
itself.
Detection and examples
| Starting point | Pattern to reuse |
|---|---|
| Next.js | hasDeclaredDependency from utils/package-json, tryGetPackageJson from utils/setup-utils, and router setup questions |
| Django | Python project files, context gathering, and Python package-manager detection |
| Laravel | Composer and framework-specific filesystem signals |
| Rails | Gemfile detection and Ruby conventions |
Use bounded filesystem helpers for project
scans and reads. They bound traversal and skip dependency/build directories; add
framework-specific exclusions with extraIgnore. Keep complex parsers and
detectors beside the config so they can be checked independently.
Show full SKILL.md (180 more words)Show less
Complete the content side
Ensure context-mill supplies the matching integration reference and task-skill variants for the framework. A registry entry alone does not provide integration knowledge. The orchestrator resolves framework variants from the skill menu and rejects missing task variants; see the orchestrator runner.
Keep project-specific facts in configuration and reusable integration guidance in that content. Model IDs, reasoning efforts, and gateway-required system prompts follow the cross-repo contract in wizard-development; a framework config cannot enable a new gateway model.
Verify the changed behavior
Check detection against the target framework and the closest overlapping framework/fallback. Reuse the existing detection checks; add a focused case only for behavior they do not cover. Confirm package-manager selection and matching context-mill variants. For an end-to-end run, use a disposable test app and the exploration guide.
For prompt, environment-upload, or outro changes, inspect the current
integration program and the
selected sequence. ui.getOutroNextSteps and analytics.getEventProperties
have no consumer. Linear
post-run/outro hooks are not shared by the orchestrator; see the
program guide.
Use the proportionate validation guidance in wizard-development. Documentation-only changes need source/link checks, not an agent run.
© 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 .claude/skills/adding-framework-support of PostHog/wizard.
Open the folder on GitHubat commit 08c70dd
Compare with similar skills
Adding Framework Support 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 |
|---|---|---|---|---|---|---|
| Adding Framework Support this skillPostHog/wizard | 197 | — | ~1.5k | Automated safety check: Pass | MIT | |
| 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 | 304 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Compare Array Bundle SizePostHog/posthog-js | 613 | — | ~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/wizard
- Official
Ink Tui
PostHog/wizard
Build or modify the PostHog wizard's Ink screens, primitives, keyboard interactions, and session-driven screen flow.
- Official
Exploring The Wizard
PostHog/wizard
Drive the PostHog wizard headlessly against a throwaway app through wizard-ci MCP tools, inspect decisions, and capture the real TUI.
- Official
Wizard Development
PostHog/wizard
Architectural guidance for changes to the PostHog Wizard: program and framework boundaries, agent routing, gateway admission, security, and TUI state.
- Official
Adding Skill Program
PostHog/wizard
Add a PostHog wizard capability backed by context-mill content.
Related
Works with
Questions about Adding Framework Support
What does Adding Framework Support do?
Add or extend language and framework support in the PostHog wizard, including detection, framework configuration, registration, and matching context-mill content. Adding Framework Support is an agent skill from PostHog/wizard, published by the product's own GitHub organization. Add or extend language and framework support in the PostHog wizard, including detection, framework configuration, registration, and matching context-mill content.
How do I install Adding Framework Support in Claude Code?
Run `npx skills add PostHog/wizard --skill adding-framework-support -a claude-code`. Or copy the skill folder (.claude/skills/adding-framework-support in PostHog/wizard) into .claude/skills/adding-framework-support in your project. Claude Code loads it when a task matches its description.
How do I install Adding Framework Support in Codex?
Run `npx skills add PostHog/wizard --skill adding-framework-support -a codex`. Or copy the skill folder (.claude/skills/adding-framework-support in PostHog/wizard) into .agents/skills/adding-framework-support in your project. Codex loads it when a task matches its description.
Can I use Adding Framework Support 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/wizard --skill adding-framework-support -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/adding-framework-support, .gemini/skills/adding-framework-support, .github/skills/adding-framework-support and .opencode/skills/adding-framework-support in your project.
What does Adding Framework Support need to run?
SKILL.md names no scripts, command-line tools or credentials: Adding Framework Support is instructions for the agent only. Our summary lists: Python 3. Compatibility (from SKILL.md): Designed for coding agents working on the PostHog wizard codebase..
Does Adding Framework Support access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Adding Framework Support 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 Adding Framework Support use?
Adding Framework Support 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 Adding Framework Support use?
About 1.5k tokens (SKILL.md is roughly 5.9k 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 Adding Framework Support?
Skills that share tags, products or a category with Adding Framework Support: 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, 304 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Adding Framework Support?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/wizard, which has 197 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 6, 2026.
Source: PostHog/wizard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.