posthog-automation
Automate PostHog tasks via Rube MCP (Composio): events, feature flags, projects, user profiles, annotations. Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill posthog-automation71
Quality
56%
Does it follow best practices?
Impact
100%
1.44xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/posthog-automation/SKILL.mdQuality
Discovery
50%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description effectively identifies specific PostHog capabilities and has a clear niche that distinguishes it from other skills. However, it critically lacks explicit trigger guidance ('Use when...') which would help Claude know when to select this skill, and could benefit from more natural user-facing keywords beyond technical feature names.
Suggestions
Add a 'Use when...' clause with trigger terms like 'PostHog', 'product analytics', 'feature flags', 'A/B testing', 'user tracking'
Include common user phrases such as 'analytics dashboard', 'track events', 'toggle feature', or 'user behavior' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'events, feature flags, projects, user profiles, annotations' and includes the actionable guidance to 'search tools first for current schemas.' | 3 / 3 |
Completeness | Describes what it does (automate PostHog tasks) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'PostHog', 'events', 'feature flags', 'projects', 'user profiles', 'annotations', but missing common variations users might say like 'analytics', 'tracking', 'A/B testing', or 'product analytics'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting PostHog via Rube MCP (Composio) - unlikely to conflict with other skills due to the specific platform and integration method mentioned. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive coverage of PostHog automation workflows with clear tool sequences and good structural organization. However, it's verbose for its purpose, lacks executable code examples (relying on parameter descriptions instead), and could benefit from splitting detailed reference material into separate files to improve scannability.
Suggestions
Add concrete executable examples showing actual tool calls with sample parameters and expected response structures, especially for common operations like capturing events and creating feature flags.
Consolidate the repeated pitfalls into a single 'Common Pitfalls' section to reduce redundancy and token usage.
Move detailed content like feature flag targeting rules, pagination patterns, and response parsing details into a separate REFERENCE.md file, keeping SKILL.md as a concise overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy (e.g., pitfalls sections repeat similar information across workflows, and some explanations like 'Events are processed asynchronously' are unnecessary for Claude). The document could be tightened by consolidating common pitfalls. | 2 / 3 |
Actionability | Provides tool names and parameter lists which are helpful, but lacks executable code examples. The ID resolution patterns use pseudocode-style numbered steps rather than actual API call examples with concrete parameters. The feature flag targeting JSON example is good but isolated. | 2 / 3 |
Workflow Clarity | Clear numbered tool sequences for each workflow with [Required] and [Optional] markers. The Setup section has explicit validation steps (verify connection, check ACTIVE status before proceeding). ID resolution patterns provide clear multi-step sequences. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections and a useful quick reference table, but the document is quite long and monolithic. Some content (like detailed feature flag targeting rules or pagination patterns) could be split into separate reference files. The external toolkit docs link is good but underutilized. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.