Skip to content
anyai.fyi

exploring-mcp-tool-original-user-motive

Skill from PostHog/ai-plugin

Agents & Workflows Worth a look curated contains scripts mcpagents

Install

npx skills add PostHog/ai-plugin --skill exploring-mcp-tool-original-user-motive

Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.

As a Claude Code plugin

/plugin marketplace add anthropics/claude-plugins-official /plugin install posthog@posthog

This skill is part of the plugin “posthog”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.

What does the exploring-mcp-tool-original-user-motive skill do?

Build a starting-point taxonomy for an MCP tool — what users were trying to accomplish before they reached the tool — and publish it as a PostHog notebook. Reconstructs each session's goal from its opening tool calls, then clusters those goals into named categories with size, share, and facet mix. Use when the user asks "why do people use this tool?", "what are users actually trying to do?", "what problem brings people here?", "where do these sessions start?", "segment usage of <tool> by goal", or wants a Clio-style taxonomy of MCP usage. Complements exploring-mcp-intent-clusters, which groups what agents did per call rather than why the session began. The agent running this skill writes the goal labels itself, reading the corpus query output session by session — the bundled scripts cover the mechanical facets but measurably lose the goal's altitude, so do not delegate that field to them.

Description from the SKILL.md in the source repository.

Questions about exploring-mcp-tool-original-user-motive

What does the exploring-mcp-tool-original-user-motive skill do?

Build a starting-point taxonomy for an MCP tool — what users were trying to accomplish before they reached the tool — and publish it as a PostHog notebook. Reconstructs each session's goal from its opening tool calls, then clusters those goals into named categories with size, share, and facet mix. Use when the user asks "why do people use this tool?", "what are users actually trying to do?", "what problem brings people here?", "where do these sessions start?", "segment usage of <tool> by goal", or wants a Clio-style taxonomy of MCP usage. Complements exploring-mcp-intent-clusters, which groups what agents did per call rather than why the session began. The agent running this skill writes the goal labels itself, reading the corpus query output session by session — the bundled scripts cover the mechanical facets but measurably lose the goal's altitude, so do not delegate that field to them.

How do I install exploring-mcp-tool-original-user-motive?

In a terminal: npx skills add PostHog/ai-plugin --skill exploring-mcp-tool-original-user-motive. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.

Which agents can use exploring-mcp-tool-original-user-motive?

Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.

Is exploring-mcp-tool-original-user-motive safe to use?

Our automatic check found patterns worth a look (see “Check”). That is not proof of anything bad – read the SKILL.md and scripts before installing.

More skills from PostHog/ai-plugin

setting-up-ai-visibility
PostHog/ai-plugin

Set up AI visibility (AI citation tracking) for a PostHog project over the PostHog MCP: confirm the project's own site and brand, review competitor brands, choose which AI answer engines run and …

Design & Media curated
No risky patterns found
migrating-from-fivetran
PostHog/ai-plugin

Move a user's Fivetran connectors into PostHog data warehouse sources. Use when the user says "migrate from Fivetran", "import my Fivetran setup", "replace Fivetran with PostHog", or asks what of their Fivetran …

Data & Databases curated
No risky patterns found
measuring-email-performance
PostHog/ai-plugin

Reports how a PostHog workflow email performs, read-only over MCP: sends, deliveries, opens, clicks, bounces and spam complaints per email step, version comparisons, clicked links, product outcomes after the send, and one …

Writing & Marketing curated
No risky patterns found
managing-llm-prompts
PostHog/ai-plugin

Create, version, release, and wire up LLM prompts with PostHog prompt management. Use when a user asks to create or edit a prompt in PostHog, move hardcoded prompts out of their code …

Development curated
Worth a look
instrument-reverse-proxy
PostHog/ai-plugin

Route PostHog's browser traffic through the app's own domain, so ad blockers don't drop events, session replays, and feature flag calls.

Frontend & UI curated
Worth a look
writing-streamlit-apps
PostHog/ai-plugin

Write Streamlit app source code that runs well in a PostHog sandbox — the posthog_apps.query() bridge for reading PostHog data, the packages baked into the sandbox image, caching and session state across …

Data & Databases curated
No risky patterns found
writing-simplified-technical-english
PostHog/ai-plugin

Write English that a reader cannot misread: one meaning per word, active voice, simple tenses, one idea per sentence, short sentences.

Writing & Marketing curated
No risky patterns found
working-with-task-comments
PostHog/ai-plugin

Read and use comments attached to the current PostHog task, its artifacts, and any canvas through the PostHog MCP exec dispatcher.

Design & Media curated
No risky patterns found

Related skills in Agents & Workflows