API Designer
Jeffallan/claude-skills
Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.
How to gate a PostHog API endpoint with project secret API key (PSAK) auth — a project-scoped, user-less service credential.
$ npx skills add PostHog/posthog --skill adding-project-secret-api-key-auth -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog adding-project-secret-api-key-auth --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.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/adding-project-secret-api-key-auth .claude/skills/adding-project-secret-api-key-auth && 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-project-secret-api-key-auth" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/adding-project-secret-api-key-auth into .claude/skills/adding-project-secret-api-key-auth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-project-secret-api-key-auth", 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/tree/master/.agents/skills/adding-project-secret-api-key-authType 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 --skill adding-project-secret-api-key-auth -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog adding-project-secret-api-key-auth --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/adding-project-secret-api-key-auth .agents/skills/adding-project-secret-api-key-auth && 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-project-secret-api-key-auth" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/adding-project-secret-api-key-auth into .agents/skills/adding-project-secret-api-key-auth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-project-secret-api-key-auth", 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 --skill adding-project-secret-api-key-auth -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog adding-project-secret-api-key-auth --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/adding-project-secret-api-key-auth .cursor/skills/adding-project-secret-api-key-auth && 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-project-secret-api-key-auth" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/adding-project-secret-api-key-auth into .cursor/skills/adding-project-secret-api-key-auth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-project-secret-api-key-auth", 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.git --path .agents/skills/adding-project-secret-api-key-auth--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 --skill adding-project-secret-api-key-auth -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog adding-project-secret-api-key-auth --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/adding-project-secret-api-key-auth .gemini/skills/adding-project-secret-api-key-auth && 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-project-secret-api-key-auth" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/adding-project-secret-api-key-auth into .gemini/skills/adding-project-secret-api-key-auth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-project-secret-api-key-auth", 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 adding-project-secret-api-key-authInstalls 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 --skill adding-project-secret-api-key-auth -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/adding-project-secret-api-key-auth .github/skills/adding-project-secret-api-key-auth && 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-project-secret-api-key-auth" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/adding-project-secret-api-key-auth into .github/skills/adding-project-secret-api-key-auth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-project-secret-api-key-auth", 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 --skill adding-project-secret-api-key-auth -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 adding-project-secret-api-key-auth --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/adding-project-secret-api-key-auth .opencode/skills/adding-project-secret-api-key-auth && 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-project-secret-api-key-auth" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/adding-project-secret-api-key-auth into .opencode/skills/adding-project-secret-api-key-auth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-project-secret-api-key-auth", 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.
adding-project-secret-api-key-authHow to gate a PostHog API endpoint with project secret API key (PSAK) auth — a project-scoped, user-less service credential.
Adding Project Secret API Key Auth is an agent skill from PostHog/posthog, published by the product's own GitHub organization. How to gate a PostHog API endpoint with project secret API key (PSAK) auth — a project-scoped, user-less service credential. Use when adding PSAK support to a viewset action, allowing a new scope for PSAKs, handling synthetic users (ProjectSecretAPIKeyUser), or choosing PSAK-aware rate throttles. Trigger terms: PSAK, ProjectSecretAPIKey, project secret API key, phs token, service auth, programmatic endpoint auth.
Its SKILL.md is about 1.6k 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 Backend & APIs, covering REST APIs. It works with PostHog. 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…
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 10f9ad7. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
curlFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
us.posthog.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
PROJECT_SECRET_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Adding Project Secret API Key Auth loads about 1.6k tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 603 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.
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.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 603 words (~1,578 tokens).
“A ProjectSecretAPIKey is a project-scoped, user-less service credential (posthog/models/project_secret_api_key.py). It behaves like a personal API key but survives users leaving the project, carries its own scopes, and authenticates as a synthetic user — not a real User row.”
Just SKILL.md in .agents/skills/adding-project-secret-api-key-auth of PostHog/posthog.
Open the folder on GitHubat commit 10f9ad7
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.
Adding Project Secret API Key Auth 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 Project Secret API Key Auth this skillPostHog/posthog | 40k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| API DesignerJeffallan/claude-skills | 12k | 2 repos | ~2k | Automated safety check: Pass | MIT | |
| Paperclippaperclipai/paperclip | 99k | — | ~9.6k | Automated safety check: Pass | MIT | |
| Nodejs Backend Patternsever-works/ever-works | 158 | 18 repos | ~4k | Automated safety check: Pass | AGPL-3.0 | |
| OpenAPI to MCP Servermcp-use/mcp-use | 11k | — | ~5.2k | Automated safety check: Pass | Apache-2.0 | |
| Use Yaakmountain-loop/yaak | 19k | — | ~1.9k | Automated safety check: Pass | MIT |
Jeffallan/claude-skills
Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.
paperclipai/paperclip
Interact with the Paperclip control plane API for task coordination and governance.
ever-works/ever-works
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.
mcp-use/mcp-use
Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.
mountain-loop/yaak
A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…
ruvnet/RuView
Covers the RuView `wifi-densepose` command line binary, its Axum REST API and the WebAssembly builds for browsers and ESP32, for embedding or scripting RuView.
PostHog/posthog
Author useful, low-noise log alerts on services in a PostHog project.
PostHog/posthog
Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…
PostHog/posthog
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).
PostHog/posthog
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.
PostHog/posthog
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
PostHog/posthog
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Works with
Categories
How to gate a PostHog API endpoint with project secret API key (PSAK) auth — a project-scoped, user-less service credential. Adding Project Secret API Key Auth is an agent skill from PostHog/posthog, published by the product's own GitHub organization. How to gate a PostHog API endpoint with project secret API key (PSAK) auth — a project-scoped, user-less service credential.
Adding Project Secret API Key Auth fits situations like: adding PSAK support to a viewset action; allowing a new scope for PSAKs; handling synthetic users (ProjectSecretAPIKeyUser); choosing PSAK-aware rate throttles.
Run `npx skills add PostHog/posthog --skill adding-project-secret-api-key-auth -a claude-code`. Or copy the skill folder (.agents/skills/adding-project-secret-api-key-auth in PostHog/posthog) into .claude/skills/adding-project-secret-api-key-auth in your project. Claude Code loads it when a task matches its description.
Run `npx skills add PostHog/posthog --skill adding-project-secret-api-key-auth -a codex`. Or copy the skill folder (.agents/skills/adding-project-secret-api-key-auth in PostHog/posthog) into .agents/skills/adding-project-secret-api-key-auth in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PostHog/posthog --skill adding-project-secret-api-key-auth -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-project-secret-api-key-auth, .gemini/skills/adding-project-secret-api-key-auth, .github/skills/adding-project-secret-api-key-auth and .opencode/skills/adding-project-secret-api-key-auth in your project.
Going by SKILL.md and its folder, Adding Project Secret API Key Auth needs the command-line tools its instructions call (curl) and credentials named PROJECT_SECRET_API_KEY. Our summary lists: Python 3; A credential in PROJECT_SECRET_API_KEY.
SKILL.md names 1 domain. In commands or code: us.posthog.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
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.
Adding Project Secret API Key Auth has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Adding Project Secret API Key Auth: API Designer (Jeffallan/claude-skills, 12k stars), Paperclip (paperclipai/paperclip, 99k stars), Nodejs Backend Patterns (ever-works/ever-works, 158 stars) and OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.