CtrlK
BlogDocsLog inGet started
Tessl Logo

growsurf

Growsurf integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Growsurf data.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/growsurf/SKILL.md
SKILL.md
Quality
Evals
Security

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 CLI integration guide with strong connection-workflow feedback loops, held back by a lack of validation guidance for the destructive actions it exposes and minor conceptual padding.

Suggestions

Add a verify-before-act checkpoint for destructive actions (e.g., run list-participants / get-participant-by-id to confirm the target before delete-participant, and confirm reward state before fulfill/approve).

Trim padding such as the Growsurf marketing intro, the term-definition bullets, and 'Use action names and parameters as needed.' to tighten conciseness.

Consider moving the Popular actions table into a references file and linking it from the body to improve progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly lean with copy-paste CLI commands, but includes minor padding such as the Growsurf intro sentence, the term-definition bullet list, and the filler line "Use action names and parameters as needed."

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands for install, login, connection setup, action search/run, and proxy requests, plus a concrete actions table and flag reference covering the common cases.

5 / 5

Workflow Clarity

The connection setup is well sequenced with state-based polling and error-recovery feedback loops, but the skill covers destructive operations (Delete Reward, Delete Participant, Fulfill/Approve Reward) whose 'Running actions' guidance lacks any verify-before-act checkpoint, capping the score at 3.

3 / 5

Progressive Disclosure

Content is well organized into clearly headed sections (install, auth, connecting, searching, running, proxy, best practices) and is appropriately self-contained, though no bundle files exist and the sizable actions table is inlined.

4 / 5

Total

16

/

20

Passed

Description

73%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 clear, third-person description that names a distinct product niche and includes an explicit 'Use when' trigger, but it leans on the generic verb 'Manage' and a broad 'when' clause rather than enumerating concrete actions and trigger phrases.

Suggestions

Replace the generic 'Manage' with a few concrete verbs (e.g., 'Create, update, and list participants, referrals, and rewards') to lift specificity.

Expand the 'Use when' clause with concrete trigger phrases (e.g., 'Use when the user wants to send referral invites, track campaign analytics, or manage participants and rewards in Growsurf').

DimensionReasoningScore

Specificity

Names the Growsurf domain and many concrete resources ("Persons, Organizations, Deals, Leads, Projects, Activities") but the only verb is the generic "Manage", so concrete action coverage is not comprehensive.

3 / 5

Completeness

It states what ("Growsurf integration. Manage …") and when ("Use when the user wants to interact with Growsurf data"), but the 'when' clause is generic rather than a list of concrete trigger phrases.

4 / 5

Trigger Term Quality

"Growsurf", "Growsurf data", and the entity names are natural trigger terms with good coverage, though common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The named product "Growsurf" plus its specific resource list carves a clear niche with minimal risk of triggering for unrelated skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.