CtrlK
BlogDocsLog inGet started
Tessl Logo

building-workflows

Build, edit, test, enable, and monitor PostHog workflows over MCP. Author the action/edge graph so it runs and opens cleanly in the visual editor, then change drafts surgically with patch operations. Use when asked to build, set up, automate, change, fix, or debug a workflow, campaign, broadcast, drip sequence, or event-triggered automation in the workflows product.

77

Quality

96%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 a high-quality, executable skill: concrete MCP tool calls, a complete worked JSON example, and rigorously sequenced lifecycle and publish/rollback workflows with validation checkpoints. It earns top marks on actionability, workflow clarity, and progressive disclosure, with only minor conciseness trimming possible in the caveat-heavy prose.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence (no generic 'what is a workflow' padding), but the lifecycle, publish, and rollback sections are dense with caveats and edge-case prose that could be trimmed slightly.

4 / 5

Actionability

Provides concrete, executable guidance throughout: a full copy-paste-ready JSON graph example, exact MCP tool names with their parameter semantics, and step-by-step test-run instructions ('omit current_action_id', 'set mock_async_functions=false').

5 / 5

Workflow Clarity

The 8-stage lifecycle is a clear, explicitly sequenced workflow with validation checkpoints (test-run step-by-step, re-test after every patch) and feedback loops; the live-change publish cycle and rollback path are equally rigorous, well above the destructive/batch cap of 3.

5 / 5

Progressive Disclosure

SKILL.md is an overview that signals one-level-deep references to two real files ([references/graph-schema.md], [references/lifecycle-and-debugging.md]) with clear in-body navigation; the bulk schema and tool catalog live in those files, not inlined.

5 / 5

Total

19

/

20

Passed

Description

100%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 excellent: third person, specific, comprehensive in both capabilities and triggers, and tightly scoped to the PostHog workflows product. It answers what and when clearly and reads as natural user phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Build, edit, test, enable, and monitor', 'Author the action/edge graph', 'change drafts surgically with patch operations') giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (build/edit/test/enable/monitor workflows over MCP, author the graph, patch drafts) and 'when' ('Use when asked to build, set up, automate, change, fix, or debug...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrasings ('build, set up, automate, change, fix, or debug') plus concrete nouns ('workflow, campaign, broadcast, drip sequence, or event-triggered automation'), covering synonyms and common variations users would actually say.

5 / 5

Distinctiveness Conflict Risk

Scoped tightly to 'PostHog workflows over MCP' with product-specific terms (action/edge graph, drafts, patch operations), giving it a clear niche and minimal overlap risk with unrelated skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
PostHog/posthog
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.