piglet
Manage PostHog feature flags, cohorts, dashboards, and insights via the `piglet` CLI. Use when the user needs to list, create, update, or delete PostHog resources, check flag status, manage rollouts, or export configuration.
86
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies the tool (piglet CLI), the platform (PostHog), the specific resource types it manages, and the concrete actions it supports. It includes an explicit 'Use when' clause with well-chosen trigger terms. The description is concise yet comprehensive, making it easy for Claude to select this skill appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'list, create, update, or delete PostHog resources, check flag status, manage rollouts, or export configuration' across multiple resource types (feature flags, cohorts, dashboards, insights). | 3 / 3 |
Completeness | Clearly answers both 'what' (manage PostHog feature flags, cohorts, dashboards, and insights via piglet CLI) and 'when' (explicit 'Use when' clause listing trigger scenarios: list, create, update, delete, check flag status, manage rollouts, export configuration). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'PostHog', 'feature flags', 'cohorts', 'dashboards', 'insights', 'piglet', 'rollouts', 'flag status', 'export configuration'. Good coverage of domain-specific terms a user would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: PostHog-specific resources managed via the 'piglet' CLI. The combination of the specific tool name and specific platform makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, highly actionable skill with excellent concrete CLI examples covering all major PostHog resource types. Its main weaknesses are moderate verbosity (the 'When to activate' and 'Best practices' sections add limited value), and missing verification steps after destructive or state-changing operations. The content could benefit from moving detailed command listings to the referenced reference.md file.
Suggestions
Add verification steps after mutations: e.g., after 'piglet flags update 123 --rollout-percentage 50', suggest running 'piglet flags get 123' to confirm the change took effect.
Remove or significantly trim the 'When to activate' section — Claude can infer when to use a PostHog management CLI from context.
Move the detailed command listings for cohorts, dashboards, insights, and projects into reference.md, keeping only flags (the primary use case) and a summary table in SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good command examples, but includes some unnecessary sections like 'When to activate' (Claude can infer this), 'Best practices' that largely repeat what's already shown, and explanations of output formats that are somewhat verbose. The 'Common pitfalls' section adds value but could be tighter. | 2 / 3 |
Actionability | Excellent actionability throughout — every section provides concrete, copy-paste-ready CLI commands with clear flags and arguments. Installation, configuration, and all CRUD operations are fully specified with executable examples. | 3 / 3 |
Workflow Clarity | The core workflow has a reasonable sequence (confirm context → operate on resources), and the gradual rollout example shows a multi-step process. However, destructive operations like delete lack explicit validation/verification steps beyond the built-in --yes flag, and there's no feedback loop for verifying changes were applied correctly (e.g., 'after updating, run get to confirm'). | 2 / 3 |
Progressive Disclosure | References to reference.md and the GitHub repo are present, but the SKILL.md itself is quite long (~150 lines of content) with inline details that could be split out (e.g., the full command reference for cohorts/dashboards/insights could live in reference.md). The reference.md file is mentioned but not provided in the bundle, making it unclear if it exists. | 2 / 3 |
Total | 9 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- cased/claude-code-plugins
- Commit
a026516
- 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.