CtrlK
BlogDocsLog inGet started
Tessl Logo

posthog-automation

Automate PostHog tasks via Rube MCP (Composio): events, feature flags, projects, user profiles, annotations. Always search tools first for current schemas.

56

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/posthog-automation/SKILL.md

The canonical home for this skill is posthog-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-organized and actionable, with concrete tool sequences, parameters, and a quick-reference table. Its weaknesses are redundant pitfalls across sections and missing validation feedback loops for destructive/batch operations like feature flag creation.

Suggestions

Consolidate the 'Known Pitfalls' section so it references rather than repeats the per-workflow pitfalls, cutting token redundancy.

Add explicit verify->fix->retry checkpoints for destructive/batch operations (e.g. after POSTHOG_CREATE_FEATURE_FLAGS_FOR_PROJECT, retrieve the flag to confirm key and active state before proceeding).

Add a 'When to use' framing in the body intro that mirrors the intended trigger phrasing, and consider extracting the flag-targeting JSON spec into a reference file to lighten the overview.

DimensionReasoningScore

Conciseness

Mostly efficient API-specific guidance, but the 'Known Pitfalls' section duplicates per-workflow pitfalls (the $-prefix rule, kebab-case flag keys, project_id requirement), which could be tightened rather than restated.

3 / 5

Actionability

Concrete tool slugs (POSTHOG_CAPTURE_EVENT, etc.), key parameters, a JSON flag-targeting example, and a quick-reference table give mostly executable guidance; not a 5 because actual schemas are dynamic via RUBE_SEARCH_TOOLS and some parameter detail is left to that lookup.

4 / 5

Workflow Clarity

Setup has an explicit checkpoint ('Confirm connection status shows ACTIVE before running'), but batch/destructive operations (creating flags with active:true, event batching) lack verify->fix->retry feedback loops, capping workflow clarity at 3.

3 / 5

Progressive Disclosure

No bundle files exist; the single body is well-structured (Setup, Core Workflows, Common Patterns, Known Pitfalls, Quick Reference) with a navigation table, but at ~220 lines it exceeds the simple-skill threshold and has minor organizational redundancy, so not a 5.

4 / 5

Total

14

/

20

Passed

Description

66%Weight 40%Scale 1-5

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 specific and reasonably distinctive, naming PostHog and five concrete capability areas via a named MCP integration. Its main weakness is the absence of an explicit 'when to use' trigger clause, which caps completeness at 3.

Suggestions

Add an explicit trigger clause, e.g. 'Use when automating PostHog analytics, creating or managing feature flags, or querying events/projects via Composio's Rube MCP.'

Vary the action verbs per capability (e.g. 'capture events, manage feature flags, list projects, fetch user profiles') to lift specificity toward 5.

Include common synonyms users say ('feature flags / rollouts / flags') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Enumerates five concrete capability areas ('events, feature flags, projects, user profiles, annotations') under a single 'Automate' verb, matching 'lists several specific actions; minor gaps' rather than 5's varied/comprehensive verbs.

4 / 5

Completeness

Has a clear 'what' ('Automate PostHog tasks via Rube MCP...') but no 'Use when...' trigger clause; 'Always search tools first for current schemas' is an instruction, not a when-to-use trigger, so completeness is capped at 3.

3 / 5

Trigger Term Quality

'PostHog', 'events', 'feature flags', 'projects', 'annotations' are terms users naturally say; good coverage but missing common synonyms (e.g. 'rollouts', 'flags'), so not a 5.

4 / 5

Distinctiveness Conflict Risk

Names a specific product plus integration path ('PostHog via Rube MCP (Composio)'), but generic nouns like 'events' and 'feature flags' carry minor overlap risk with other analytics/flag skills, so not a 5.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.