Name: skills-store
Rating: 67.2 (1 reviews)
Author: PostHog

skills-store

Discover and use shared team skills stored in PostHog. Use when the user asks to list, browse, load, or manage "shared skills", "team skills", or references the "skills store" / "skill store".

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

75%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 MCP skill guide with comprehensive copy-paste examples and clear workflows. Its main weakness is conciseness — editorial commentary and an inlined duplicate bridge-skill block could be trimmed or split out.

Suggestions

Trim editorial asides such as 'The whole point of descriptions is that you can pick the right skill without loading any bodies' that restate concepts Claude already knows.

Move the full inline bridge-skill markdown block into a bundled reference file (e.g. references/bridge-skill.md) and keep only a short pointer plus the key fields in the body, reducing duplication and body length.

Add an explicit confirm/validate step before the irreversible `skill-archive` and full-bundle `skill-update` replace operations (e.g. 'fetch and re-list to confirm the target before archiving') to close the validation gap for destructive actions.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with dense executable examples, but editorial asides ('The whole point of descriptions is...') and a fully duplicated inline bridge-skill block add padding that could be trimmed, fitting the 'mostly efficient but could be tightened' anchor.	3 / 5
Actionability	Every tool is shown with copy-paste-ready JSON examples covering list, search, get, file-get, create, update (body/edits/file_edits), per-file CRUD, archive, and porting, fully covering the common cases.	5 / 5
Workflow Clarity	Numbered sequences (Loading Step 1-3, Porting 1-3) and a base_version concurrency checkpoint give a clear sequence with most checkpoints present; destructive archive/replace ops carry explicit warnings but lack a formal validate-before-proceed loop, capping it just below 5.	4 / 5
Progressive Disclosure	The skill is self-contained with no bundle files and is well-organized into clearly signaled sections with no nested references; the ~40-line inline bridge-skill example is content that could plausibly live in a separate reference file, a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

87%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, well-targeted description that clearly states both purpose and triggers with natural synonyms and third-person voice. Minor room to expand the action list and add a couple more natural variants to reach full specificity and trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('shared team skills stored in PostHog') and lists several concrete actions ('list, browse, load, or manage'), with only minor coverage gaps versus a fully comprehensive action list.	4 / 5
Completeness	Explicitly answers both what ('Discover and use shared team skills stored in PostHog') and when ('Use when the user asks to list, browse, load, or manage...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural user phrases with synonyms ('shared skills', 'team skills', 'skills store', 'skill store'); a few additional natural variants are missing and there are no file-extension-style triggers, so it stops just short of 5.	4 / 5
Distinctiveness Conflict Risk	A clear PostHog skills-store niche with distinct triggers ('skills store', 'team skills') makes conflict with other skills unlikely, matching the top anchor.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 11 missing	Warning

	Total	15 / 16 Passed

Repository: PostHog/posthog
Path: products/skills/skills/skills-store/SKILL.md
Commit: 130f3a1

Reviewed: 9 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.