Name: skills-store
Rating: 68 (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

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

76%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 reference for the PostHog skills API with comprehensive executable examples. Its main gaps are the missing validation/confirmation checkpoints around destructive operations and an inlined bridge-skill template that would be better as a bundled reference file.

Suggestions

Add an explicit validation/confirmation checkpoint to the skill-archive and full-bundle-replace workflows (e.g., 'Confirm the skill name with the user before archiving, since it cannot be undone') so destructive operations are not executed without verification.

Move the embedded local-bridge SKILL.md template into a bundled reference file (e.g. references/bridge-skill-template.md) and link to it, reducing body length and improving progressive disclosure.

Trim mildly chatty prose such as 'The whole point of descriptions is that you can pick the right skill without loading any bodies' to keep the body lean and token-efficient.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly actionable with little concept over-explanation, but the fully embedded local-bridge SKILL.md template (~45 lines) and a few chatty lines ('The whole point of descriptions is...') could be trimmed or moved to a reference, fitting 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	It provides copy-paste-ready JSON tool-call examples covering every operation (list, get, file-get, create, update via body/edits/file_edits, file CRUD, rename, archive) plus concrete parameter-naming gotchas, fully covering the common cases.	5 / 5
Workflow Clarity	Workflows are well sequenced with base_version concurrency checks, but destructive operations (skill-archive 'cannot be undone' and the `files` full-bundle replace that drops unlisted files) lack explicit validation/confirm checkpoints, so the rubric's destructive-operation cap applies.	3 / 5
Progressive Disclosure	The body is well organized into clearly headed sections with no nested references and a helpful tool table, but at ~270 lines with no bundle files the inlined bridge-skill template is content that could be split into a reference, leaving minor organization gaps rather than ideal content separation.	4 / 5
	Total	16 / 20 Passed

Description

90%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 description that clearly communicates both purpose and trigger conditions with natural, synonym-rich language. The only weakness is that the capability verbs ('discover and use') are somewhat generic rather than enumerating concrete operations.

Dimension	Reasoning	Score
Specificity	The description names the domain clearly ('shared team skills stored in PostHog') and gives 1-2 actions ('Discover and use'), but the verbs are generic rather than a list of several concrete capabilities, fitting the anchor for naming a domain with 1-2 concrete actions.	3 / 5
Completeness	It explicitly states what the skill does ('Discover and use shared team skills stored in PostHog') and when to use it ('Use when the user asks to list, browse, load, or manage...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	It covers multiple natural action verbs users would say ('list, browse, load, or manage') plus synonyms ('shared skills'/'team skills', 'skills store'/'skill store'), giving comprehensive natural-term coverage with variations.	5 / 5
Distinctiveness Conflict Risk	The PostHog-specific niche and distinctive triggers ('skills store', 'skill store', 'shared/team skills') make it clearly distinguishable with minimal risk of triggering the wrong skill.	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: 9 missing	Warning

	Total	15 / 16 Passed

Repository: PostHog/posthog
Path: products/skills/skills/skills-store/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.