Name: outgrow
Rating: 61.6 (1 reviews)
Author: membranedev

outgrow

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

Quality

72%

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/outgrow/SKILL.md

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.

The body is highly actionable with comprehensive executable Membrane CLI commands and solid validation feedback loops for connection state. The main gaps are minor: a vague Overview bullet list, inconsistent step numbering, and no progressive disclosure into reference files despite the file length.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and code with only minor over-explanation (e.g. the vaguely actionable 'Outgrow Overview' bullet list and a few explanatory sentences about Membrane), fitting 'efficient; minor instances of over-explanation that could be trimmed'; not a 5 because the Overview bullets and some prose could be cut.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action discovery, action execution, and proxying, plus a flags table and JSON-input examples covering the common cases, matching 'fully executable; copy-paste ready; specific examples cover the common cases'.	5 / 5
Workflow Clarity	A clear sequence (install -> auth -> connect -> poll for ready -> search -> run) with feedback loops (polling connection state, re-polling after CLIENT_ACTION_REQUIRED, checking error fields) is present, but step numbering is inconsistent ('skip to Step 2' with no labeled Step 2, '1b' with no 1a), fitting 'clear sequence with most checkpoints; minor validation gaps'; not a 5 because of the numbering inconsistency.	4 / 5
Progressive Disclosure	With no bundle files present, all content is inline but well-organized into clear headed sections (Working with Outgrow, Authentication, Connecting, Searching, Popular actions, Proxy requests, Best practices), fitting 'good structure; most content appropriately placed; minor organization gaps'; not a 5 because a 157-line single file with no one-level-deep references could split the proxy flags table and connection-state detail into reference files.	4 / 5
	Total	17 / 20 Passed

Description

62%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 cleanly answers both what and when and is anchored to a distinctive product name, but its capability phrasing is generic. Tightening the action list with concrete Outgrow-specific operations would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Outgrow operations, e.g. 'Fetch leads, quiz responses, and calculator submissions, and automate Outgrow workflows.'

Add a few natural trigger variants to broaden keyword coverage, e.g. 'Use when the user mentions Outgrow, Outgrow calculators, quizzes, or lead-capture data.'

Tie the 'when' clause to specific Outgrow artifacts (calculators, quizzes, surveys) so the trigger is more clearly Outgrow-specific and less likely to overlap with generic data skills.

Dimension	Reasoning	Score
Specificity	The description names the Outgrow domain and lists action areas ('Manage data, records, and automate workflows'), but these verbs are generic rather than concrete operations, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; not a 4 because no specific concrete operations (e.g. 'fetch leads', 'pull quiz responses') are named.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Outgrow data') are explicitly present, matching the 'has both what and when; when could be more explicit' anchor; not a 5 because the 'what' actions are generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	It includes the natural product term 'Outgrow' and the phrase 'interact with Outgrow data', but coverage is limited to the single product name with no synonyms or variant phrasings, fitting the 'some relevant keywords but missing common variations' anchor; not a 4 because only one trigger phrase is effectively present.	3 / 5
Distinctiveness Conflict Risk	The distinctive product name 'Outgrow' gives it a clear niche with low conflict risk, but the generic 'manage data, records, and automate workflows' phrasing could overlap with other integration skills, fitting 'mostly distinct; minor overlap risk'; not a 5 because the action wording is not uniquely Outgrow-specific.	4 / 5
	Total	14 / 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/outgrow/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.