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.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

A high-quality, operationally dense skill body: concrete tooling, a complete worked example, an explicitly sequenced lifecycle with validation and error-recovery loops, and well-structured one-level references. Token-efficient with no padding of concepts Claude already knows.

DimensionReasoningScore

Conciseness

Lean and information-dense throughout; assumes Claude's competence (no explanation of what MCP/workflows are in general terms) and every clause carries operational specifics rather than padding.

5 / 5

Actionability

Fully executable guidance: concrete MCP tool names (workflows-create, workflows-test-run, workflows-patch-graph, etc.), specific patch operations, and a complete copy-paste-ready JSON worked example covering the common case.

5 / 5

Workflow Clarity

An explicit 8-step lifecycle with validation checkpoints ('Every edit invalidates your earlier test — re-run', 're-test the path you changed') and error-recovery feedback loops (skipped→fix payload→re-run; publish 409/400→preview again), satisfying the destructive/batch validation requirement.

5 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references to real bundle files ([references/graph-schema.md], [references/lifecycle-and-debugging.md]); bulk schema and tool catalog appropriately split out, leaving SKILL.md as a navigable overview.

5 / 5

Total

20

/

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.

An exemplary description: third-person voice, comprehensive concrete actions, and an explicit 'Use when' clause rich with natural synonyms, all scoped to a distinct product niche. No vague fluff or over-claims.

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 rather than vague language.

5 / 5

Completeness

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

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms — 'build, set up, automate, change, fix, or debug' plus 'workflow, campaign, broadcast, drip sequence, or event-triggered automation' — the phrases users actually say.

5 / 5

Distinctiveness Conflict Risk

Tightly scoped to 'PostHog workflows over MCP' and 'the workflows product' with product-specific triggers, giving a clear niche and minimal conflict risk with other 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.