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:Lingjie-chen/MT5 --skill posthog-automation64
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 technical niche, but critically lacks explicit trigger guidance for when Claude should select this skill. The operational instruction about searching tools first doesn't help with skill selection. Adding natural user language variations would improve discoverability.
Suggestions
Add a 'Use when...' clause with trigger terms like 'PostHog', 'product analytics', 'feature flag management', 'event tracking', or 'user behavior analysis'
Include common user phrases such as 'analytics dashboard', 'A/B testing', 'track events', or 'user segmentation' to improve trigger term coverage
Move the operational guidance ('Always search tools first') to the skill body rather than the description, as it doesn't aid skill selection
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'events, feature flags, projects, user profiles, annotations' - these are distinct, actionable capabilities within the PostHog domain. | 3 / 3 |
Completeness | Describes what it does (PostHog tasks via Rube MCP) but completely lacks a 'Use when...' clause or explicit trigger guidance. The instruction to 'search tools first' is operational guidance, not usage triggers. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'PostHog', 'feature flags', 'events', 'user profiles', but missing common variations users might say like 'analytics', 'tracking', 'A/B testing', or 'product analytics'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche - PostHog via Rube MCP/Composio is highly distinctive. The combination of platform (PostHog) and integration method (Rube MCP) makes conflicts with other skills unlikely. | 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 via Rube MCP with clear workflow sequences and good structural organization. However, it's verbose for a skill file, lacks executable code examples (relying on tool names and parameter descriptions instead), and could benefit from splitting detailed workflows into separate reference files.
Suggestions
Add concrete executable examples showing actual tool calls with sample parameters and expected response structures
Consolidate the repeated pitfalls into a single 'Common Pitfalls' section to reduce redundancy
Split detailed workflow sections (Capture Events, Feature Flags, etc.) into separate reference files, keeping only quick-start summaries in SKILL.md
Remove explanatory content Claude already knows (e.g., 'Events are processed asynchronously; ingestion delay is typically seconds')
| 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 key parameters clearly, but lacks executable code examples. The ID resolution patterns use pseudocode-style numbered steps rather than actual API call examples with concrete parameter values. The feature flag targeting JSON example is helpful but isolated. | 2 / 3 |
Workflow Clarity | Clear numbered tool sequences for each workflow with explicit [Required] and [Optional] markers. The Setup section has a clear 4-step validation flow including checking connection status before proceeding. ID resolution patterns are well-sequenced. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a useful quick reference table, but the document is quite long and monolithic. The detailed workflow sections could be split into separate files, with SKILL.md serving as a concise overview pointing to them. | 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.