CtrlK
BlogDocsLog inGet started
Tessl Logo

working-with-skills

Best practices for agents managing PostHog skills via the MCP `skill-*` tools — how to discover, read, create, update, and refactor skills efficiently, especially large skills with many bundled files. Use whenever you are about to call any `skill-*` tool, asked to author or edit a shared skill, or troubleshoot why a skill write was rejected. Pairs with `skills-store` (which covers the raw tool surface) by adding the decision-tree, efficiency, and pitfall guidance.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

—

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally actionable, concise routing guide with copy-paste tool-call examples, a clear decision tree, and explicit validation feedback loops for risky write operations. Progressive disclosure is strong but the skill is self-contained with no actual bundled files to navigate.

DimensionReasoningScore

Conciseness

Lean, routing-focused body that assumes Claude's competence — no padding, no explaining what a skill is, and tight code blocks; every section earns its place.

5 / 5

Actionability

Copy-paste-ready JSON tool-call examples cover the common cases (create, update body/edits/file_edits, file CRUD, rename, archive) with exact parameter names and a clear path-vs-file_path rule.

5 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced with a decision tree and a concrete validation/feedback loop for the destructive concurrency case (base_version mismatch → re-get → reconcile → retry).

5 / 5

Progressive Disclosure

Well-organized overview with clear sectioning and one-level-deep external pointers (skills-store skill, Agent Skills spec); no nested or buried references, though it is a self-contained routing doc rather than a split bundle.

4 / 5

Total

19

/

20

Passed

Description

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

A strong, scope-honest description that names concrete actions, provides explicit 'Use whenever...' trigger guidance, and carves out a distinct niche from its sibling skill. Trigger-term coverage is thorough though a few synonyms could broaden discoverability.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'discover, read, create, update, and refactor skills' — giving comprehensive coverage of the skill-management capability surface.

5 / 5

Completeness

Explicitly states both what it does ('best practices for agents managing PostHog skills') and when to use it ('Use whenever you are about to call any skill-* tool...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'asked to author or edit a shared skill' and 'troubleshoot why a skill write was rejected' are present, but a few common phrasings (e.g. 'skill creation', synonyms) are absent.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to PostHog 'skill-*' MCP tools and explicitly distinguished from the sibling 'skills-store' skill, giving a clear niche with minimal overlap risk.

5 / 5

Total

19

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 11 missing

Warning

Total

15

/

16

Passed

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.