checking-member-access — Claude Code skill: PostHog access
The checking-member-access Claude Code skill explains member and role permissions in a PostHog project through access-control MCP tools. It answers who can view or edit dashboards, flags, and data.
no license 122 installs ★ 101 updated 2026-10-24
npx skills add PostHog/ai-plugin --skill checking-member-access -a claude-codeWhat checking-member-access does
The skill reads access-control tool results and explains the effective permissions for a member, a role, or the project as a whole. It covers access at project, tool, object, and property levels, including where an effective permission comes from. Questions about roles can require the separate role tools.
Use it to find out who can edit a dashboard or feature flag, why a member cannot open a table, or which properties a role cannot see. It also explains the project’s default access. Free and pay-as-you-go plans do not include access-control tools; role rules are available only on Enterprise. To change a rule, the workflow prepares the change first and runs it only after the user confirms.
What it helps with
- check what actions a project member can take
- find who can edit a dashboard or feature flag
- explain why a member cannot open a table or notebook
- identify properties hidden from a role
- inspect the project’s default access
Example prompts for the agent
- What can this project member do, and can they edit feature flags?
- Why can’t this member open the dashboard?
- Which properties are hidden from the support role?
How to install checking-member-access
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill checking-member-access -a claude-code2Manually: put the files in place
~/.claude/skills/checking-member-access/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/checking-member-access/
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill checking-member-access -a codex2Manually: put the files in place
.agents/skills/checking-member-access/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill checking-member-access -a cursor2Manually: put the files in place
.cursor/skills/checking-member-access/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install PostHog/ai-plugin skills/checking-member-access2Manually: put the files in place
.github/skills/checking-member-access/SKILL.md1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill checking-member-access -a gemini-cli2Platform CLI
gemini skills install https://github.com/PostHog/ai-plugin --path skills/checking-member-accessManually: put the files in place
.devin/skills/checking-member-access/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill checking-member-access -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about checking-member-access
How do I install checking-member-access in Claude Code?
Run npx skills add PostHog/ai-plugin --skill checking-member-access -a claude-code. The skill file is installed at ~/.claude/skills/checking-member-access/SKILL.md.
What does checking-member-access do?
It interprets access-control tool results to explain effective permissions for PostHog members and roles. It also covers object and property access, plus project defaults.
What does checking-member-access need to work?
It needs a PostHog project and access to the access-control MCP tools. Free and pay-as-you-go plans do not include those tools; role rules require Enterprise.