checking-member-access

Explains what a member or a role can do in a PostHog project, using the access control MCP tools.

Skill by PostHogOfficial

IndexedLicense unknown★ 95

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/posthog-checking-member-access

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Explains what a member or a role can do in a PostHog project, using the access control MCP tools. Use when the user asks what someone can see or edit, who can edit dashboards or feature flags, why a member can or cannot open a dashboard, notebook or table, what a role grants, which properties are hidden from someone, or how the project's default access is set. Covers what each level means, how the stored rule, the enforced level and the inherited access relate, what the null values mean, which tool answers which question, and when the answer needs the role tools too.

Use cases: data, writing, agent-building

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/checking-member-access

What's inside

Skill name: checking-member-access
Description: Explains what a member or a role can do in a PostHog project, using the access control MCP tools. Use when the user asks what someone can see or edit, who can edit dashboards or feature flags, why a member can or cannot open a dashboard, notebook or table, what a role grants, which properties are hidden from someone, or how the project's default access is set. Covers what each level means, how the stored rule, the enforced level and the inherited access relate, what the null values mean, which tool answers which question, and when the answer needs the role tools too.
License: unknown
Instructions: 147 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

The license isn't open source, so the instructions aren't shown here. Read SKILL.md on GitHub

Signals

Stars: 95
Forks: 20
Open issues: 12
Last commit (this folder): Oct 16, 2026 (13 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License: License unknown
Repository: github.com/PostHog/ai-plugin
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

Same skill elsewhere

Copies of this SKILL.md published by others; search shows only one of them.

0.355score
checking-member-access
PostHogOfficial
Explains what a member or a role can do in a PostHog project, using the access control MCP tools.
SkillAFreshness: A★ 75Claude Code +9