Name: lagrowthmachine
Rating: 60.8 (1 reviews)
Author: membranedev

lagrowthmachine

LaGrowthMachine integration. Manage Leads, Persons, Organizations, Users, Roles, Activities and more. Use when the user wants to interact with LaGrowthMachine data.

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/lagrowthmachine/SKILL.md

Quality

Content

63%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 Membrane CLI commands and a clear connection workflow including validation checkpoints. Its main weaknesses are mild verbosity in the intro, inlined reference material that belongs in a separate file, and placeholder values in examples.

Suggestions

Trim the opening descriptive paragraph and the bare Overview bullet list to assume Claude's knowledge of the product category.

Move the 16-row Popular actions table into a references/ file (e.g., ACTIONS.md) and keep only a few key examples inline, with a clear pointer.

Tighten the "Step 2" cross-reference so the connection → action-search → action-run sequence reads as one numbered workflow.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the opening marketing paragraph ("LaGrowthMachine is a sales automation tool that helps businesses generate leads...") and the thin Overview list are background Claude does not strictly need, so it could be tightened.	3 / 5
Actionability	Provides concrete, copy-pasteable commands throughout (membrane login, connection ensure, action list/run, request) with flag tables; minor gaps remain in the form of placeholders like CONNECTION_ID and a generic --input example.	4 / 5
Workflow Clarity	Clear sequence from install → authenticate → connect → poll for READY → search actions → run, with explicit state-based checkpoints and a polling feedback loop for CLIENT_ACTION_REQUIRED; only minor gaps (the "Step 2" reference is loosely labeled).	4 / 5
Progressive Disclosure	Well-sectioned single file, but with no bundle files the 16-row Popular actions reference table and the proxy flag table are inlined bulk reference content that would be better placed in a separate reference file, so it is not fully appropriately split.	3 / 5
	Total	14 / 20 Passed

Description

78%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 specific and clearly scoped to LaGrowthMachine with both a "what" and an explicit "when" clause. It is held back from the top band only by the vague "and more" and a slightly generic trigger phrase.

Suggestions

Replace "and more" with a finite, concrete list of the primary manageable entities to lift specificity.

Sharpen the trigger clause to name the concrete user requests (e.g., "Use when the user wants to search, create, or update leads and campaigns in LaGrowthMachine").

Add natural synonyms users might say (e.g., "LGM", "lead outreach", "campaign stats") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete actions ("Manage Leads, Persons, Organizations, Users, Roles, Activities"), but the trailing "and more" leaves minor coverage gaps, so it stops short of a 5.	4 / 5
Completeness	Answers both "what" (manage Leads, Persons, Organizations, etc.) and "when" ("Use when the user wants to interact with LaGrowthMachine data"), but the "when" trigger is somewhat generic and could be more specific, keeping it below 5.	4 / 5
Trigger Term Quality	Includes natural terms a user would say ("Leads", "Campaigns"-adjacent entities, "LaGrowthMachine data") and an explicit "Use when" clause, though it lacks common synonyms or alternate phrasings users might emit.	4 / 5
Distinctiveness Conflict Risk	Targets a named, specific application (LaGrowthMachine) with entity-specific triggers, giving it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	17 / 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/lagrowthmachine/SKILL.md
Commit: f484c82

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