Name: growth-book
Rating: 51.2 (1 reviews)
Author: membranedev

growth-book

Growth Book integration. Manage data, records, and automate workflows. Use when the user wants to interact with Growth Book data.

Quality

56%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/growth-book/SKILL.md

Quality

Content

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

The body is highly actionable with executable CLI commands and a clear connection-state workflow, but it loses conciseness to product-knowledge restatements and inlines reference-style material that has no supporting bundle files to offload it.

Suggestions

Remove or condense the opening 'Growth Book is an open-source...' paragraph and overview bullet list, which explain concepts Claude already knows.

Move the proxy flag options table and the detailed clientAction state reference into separate reference files (e.g. references/proxy.md, references/connection-states.md) with clearly signaled links.

Add an explicit validation/retry checkpoint after running actions or proxy requests, e.g. check the response state and handle errors before proceeding.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with command blocks and a lean options table, but sections like the Growth Book overview and the 'What is Growth Book' intro restate product knowledge Claude already has, and the connection-state explanations are somewhat padded.	3 / 5
Actionability	It provides copy-paste-ready commands throughout — install, login, connection ensure, connection get --wait, action list/run, and proxy requests — with concrete flags and example JSON inputs covering the common cases.	5 / 5
Workflow Clarity	The connect-to-ready flow is clearly sequenced with a polling loop and state-by-state guidance including CLIENT_ACTION_REQUIRED handling, but it lacks an explicit validate-after-action checkpoint for operations that mutate or run actions.	4 / 5
Progressive Disclosure	There is reasonable section structure but no bundle files exist, so the proxy options table and clientAction reference are inlined in SKILL.md rather than split into separate reference files with clearly signaled one-level links.	3 / 5
	Total	15 / 20 Passed

Description

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

The description is anchored to a named product, which helps distinctiveness, but the capability verbs are generic and the trigger phrasing omits the feature-flag/experimentation vocabulary users would actually say.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Growth Book actions such as 'toggle feature flags, run and analyze A/B experiments, and manage organizations and users'.

Add natural trigger terms like 'feature flags', 'A/B tests', and 'experimentation' to the 'Use when' clause so it matches what users say.

Tighten 'interact with Growth Book data' to reference the specific entities (experiments, feature results, attributes) rather than generic 'data'.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the domain but the actions are minimal and generic — 'manage data, records' and 'automate workflows' carry no Growth Book-specific verbs like 'toggle feature flags' or 'analyze experiment results'.	2 / 5
Completeness	It gives a weak 'what' ('Manage data, records, and automate workflows') and an explicit but generic 'when' ('Use when the user wants to interact with Growth Book data'), so the when is present yet unspecific, capping completeness below 4.	3 / 5
Trigger Term Quality	'Use when the user wants to interact with Growth Book data' surfaces the product name as the main trigger, but it lacks the natural synonyms users say such as 'feature flags', 'A/B tests', or 'experiments' that the body itself references.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Growth Book' gives it a clear niche with minimal conflict risk, though the generic 'data/records/workflows' phrasing leaves slight overlap with other integration skills.	4 / 5
	Total	12 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/growth-book/SKILL.md
Commit: f484c82

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