managing-endpoint-versions

Work safely with endpoint versions — preview a draft in the playground, roll back to an older version, update settings on one version without bumping query history, deactivate a specific version. Use when the user asks "how do I roll back my endpoint", "preview my changes before publishing", "I want to fix v5 without bumping the version", or anything involving the version history. Calls out today's limitations honestly: there is no pointer flip; "rollback" means forking the old query into a new top version.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%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 highly actionable, well-structured guide with concrete tool calls and validation steps for destructive operations. Its main weakness is redundancy between the workflow sections and the closing Important notes, plus the absence of explicit error-recovery feedback loops.

Suggestions

Consolidate the 'Important notes' section: remove points already established in the workflows (no pointer flip, query changes cut a new version, materialisation is per-version) and keep only genuinely new caveats.

Add an explicit error-recovery feedback loop to the rollback workflow, e.g. 'if endpoint-run ?version=N returns the wrong shape, re-edit the query and cut a fresh version rather than patching history'.

Consider extracting the per-workflow tool-call details into a references file so SKILL.md stays a lean overview, which would also let progressive_disclosure reach the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes competence without explaining basics, but the 'Important notes' section restates several points already made in the workflows (no pointer flip, query changes cut a version, materialisation is per-version), which could be trimmed.	4 / 5
Actionability	Concrete tool calls with parameters (endpoint-update {version: 3, is_active: false}, endpoint-get ?version=N) and a fully worked example interaction make the guidance copy-paste ready across the common cases.	5 / 5
Workflow Clarity	Each workflow is numbered and includes verification checkpoints (endpoint-run to confirm shape, user confirmation before retiring a version), satisfying the destructive-ops validation requirement, but explicit error-recovery feedback loops are absent.	4 / 5
Progressive Disclosure	Well-organized into clear sections (When to use, Versioning model, Available tools, Workflows, Example, Notes) with a clearly signaled pointer to the auditing-endpoints sibling skill, but at ~150 lines with no reference split it sits just above the simple-skill exception.	4 / 5
	Total	17 / 20 Passed

Description

83%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, specific description that pairs concrete capabilities with natural quoted trigger phrases and an explicit 'Use when' clause. It is held back only by a minor coverage gap (no pruning trigger) and slight overlap risk within the endpoint skill family.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions ("preview a draft in the playground", "roll back to an older version", "update settings on one version without bumping query history", "deactivate a specific version"), but omits the pruning/dead-version workflow covered in the body, leaving a minor coverage gap.	4 / 5
Completeness	Clearly states what the skill does (the four actions) and when to use it via an explicit "Use when..." clause with concrete trigger phrases, matching the anchor that requires both.	5 / 5
Trigger Term Quality	Quoted triggers like "how do I roll back my endpoint", "preview my changes before publishing", and "I want to fix v5 without bumping the version" are natural user phrasings with a catch-all ("anything involving the version history"), but synonyms such as "revert" or "disable a version" are missing.	4 / 5
Distinctiveness Conflict Risk	The endpoint-versioning niche is distinct with specific triggers, but the body references sibling skills (auditing-endpoints) indicating a family of endpoint skills, so minor overlap risk remains.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: PostHog/posthog
Path: products/endpoints/skills/managing-endpoint-versions/SKILL.md
Commit: 6fca5f8

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.