posthog-automation
Automate PostHog tasks via Rube MCP (Composio): events, feature flags, projects, user profiles, annotations. Always search tools first for current schemas.
65
47%
Does it follow best practices?
Impact
100%
1.44xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.trae/skills/posthog-automation/SKILL.mdQuality
Discovery
67%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 is reasonably strong in specificity and distinctiveness, clearly naming the platform (PostHog), the integration method (Rube MCP/Composio), and specific task categories. However, it lacks an explicit 'Use when...' clause and could benefit from more natural trigger terms that users might say when needing PostHog-related help, such as 'analytics', 'tracking', or 'A/B testing'.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about PostHog analytics, tracking events, managing feature flags, or working with product analytics via Composio.'
Include additional natural trigger terms users might say, such as 'analytics', 'tracking', 'A/B testing', 'experimentation', 'product analytics', or 'Composio'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: events, feature flags, projects, user profiles, annotations. Also includes a concrete procedural instruction ('Always search tools first for current schemas'). | 3 / 3 |
Completeness | Clearly answers 'what' (automate PostHog tasks via Rube MCP with specific task types), but lacks an explicit 'Use when...' clause. The 'when' is only implied by the domain mention. Per rubric guidelines, missing 'Use when...' caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'PostHog', 'feature flags', 'events', 'annotations', 'user profiles', and 'Rube MCP (Composio)', but misses common user variations like 'analytics', 'tracking', 'A/B testing', 'experimentation', or 'product analytics' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche: PostHog automation via a specific MCP tool (Rube/Composio). The combination of the specific platform (PostHog) and specific integration method (Rube MCP/Composio) makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill content is severely bloated — it appears the evaluation rubric was accidentally pasted into the skill content multiple times, and even the legitimate content is highly repetitive with pitfalls duplicated across individual workflow sections and a consolidated section. While the structure of tool sequences and parameter documentation is reasonable, the lack of concrete executable examples and the monolithic format significantly reduce its effectiveness.
Suggestions
Remove the duplicated rubric content that was accidentally embedded in the skill body, and consolidate the repeated pitfalls into a single section or eliminate the per-workflow pitfalls in favor of the summary section.
Add concrete tool call examples showing exact input parameters and expected response shapes (e.g., a complete POSTHOG_CAPTURE_EVENT call with sample parameters and the expected response).
Split detailed per-workflow parameter lists and the feature flag targeting guide into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with the quick reference table and setup instructions.
Add validation steps to workflows — e.g., after creating a feature flag, verify it appears in the list; after capturing events, query to confirm ingestion.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and repetitive. The content is massively bloated by what appears to be the rubric itself being pasted multiple times into the skill content. Even ignoring that corruption, the actual skill content repeats pitfalls across sections and in a dedicated 'Known Pitfalls' section, explains concepts Claude already knows (pagination, ISO 8601, kebab-case), and includes unnecessary 'When to use' descriptions for each workflow. | 1 / 3 |
Actionability | Provides specific tool names, parameter lists, and a JSON example for feature flag targeting. However, there are no executable code examples or complete tool call examples showing exact input/output. The ID resolution patterns use pseudocode-style numbered steps rather than concrete tool call examples. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with numbered steps and tool names marked as Required/Optional. However, there are no validation checkpoints or error-handling feedback loops — for example, no guidance on verifying that a captured event was actually ingested, or checking that a created feature flag is working correctly before proceeding. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files. All detailed parameter lists, pitfalls, common patterns, and the quick reference table are inlined in a single massive document. The detailed per-workflow sections with full parameter lists and pitfalls should be split into separate reference files. | 1 / 3 |
Total | 6 / 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 | |
- Repository
- Lingjie-chen/MT5
- Commit
3069d33
- 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.