Name: goody
Rating: 63.2 (1 reviews)
Author: membranedev

goody

Goody integration. Manage Organizations, Pipelines, Projects, Users, Goals, Filters. Use when the user wants to interact with Goody data.

Quality

75%

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/goody/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 a strong, actionable integration guide: real CLI commands, an action catalog, and explicit connection-state validation with a re-poll feedback loop. The main gaps are a loosely numbered top-level sequence, no verification step for destructive/batch action results, and some API-reference material inlined rather than split into separate files.

Suggestions

Add an explicit numbered top-level workflow (1. Install CLI, 2. Authenticate, 3. Ensure connection, 4. Search actions, 5. Run action) so the implicit "Step 2" reference resolves to a real header.

Add a validation/verification checkpoint for destructive and batch actions (e.g. before cancel-order or create-order-batch, confirm the target ID and inspect the returned output/state).

Move the clientAction field breakdown and the full proxy flags table into a separate reference file (e.g. references/connection-states.md) and link to it one level deep, keeping SKILL.md as an overview.

Dimension	Reasoning	Score
Conciseness	The body is largely lean, using executable commands and tables rather than padded prose, with only minor trimmable asides ("so you can focus on the integration logic rather than auth plumbing" and the one-sentence company background).	4 / 5
Actionability	It provides copy-paste-ready commands for every stage (login, connection ensure/get --wait, action list/run, request) plus a concrete actions table with real keys (create-order-batch, list-orders) and JSON input examples, covering the common cases.	5 / 5
Workflow Clarity	The connection flow has explicit state-based validation and a feedback loop (poll after CLIENT_ACTION_REQUIRED), but the overall sequence is only loosely numbered ("Step 2" referenced without a matching header) and running/cancelling actions lacks result-verification, leaving minor validation gaps.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested references, but with no bundle files present, reference-like material (the clientAction field breakdown, the full flags table, the actions catalog) is inlined in a single ~165-line file rather than split into one-level-deep references.	4 / 5
	Total	17 / 20 Passed

Description

67%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 solid: it states what the skill does, lists concrete managed entities, and includes an explicit "Use when" trigger. Its main weakness is generic trigger phrasing ("interact with Goody data") and reliance on a single verb, which leave trigger-term quality and completeness just short of the top anchors.

Suggestions

Replace the generic "interact with Goody data" trigger with concrete phrases users actually say, e.g. "Use when the user wants to send gifts, manage Goody orders/products, or work with Goody contacts and campaigns."

Vary the single "Manage" verb into specific actions (e.g. "create and track orders, browse products, manage contacts and contact lists") to lift specificity and trigger coverage.

Align the listed entities with the body's actual capabilities (orders, products, campaigns, contacts) to avoid implying unsupported objects like Pipelines or Goals.

Dimension	Reasoning	Score
Specificity	Names the domain and enumerates several concrete capabilities ("Manage Organizations, Pipelines, Projects, Users, Goals, Filters"), though the single generic verb "Manage" applied across entities leaves minor gaps versus the comprehensive multi-verb anchor at 5.	4 / 5
Completeness	Answers both what ("Goody integration. Manage Organizations...") and when ("Use when the user wants to interact with Goody data"), but the when clause is generic rather than listing concrete trigger phrases, fitting the 4 anchor.	4 / 5
Trigger Term Quality	Includes the brand keyword "Goody" and a list of entity names, but omits the natural phrases users would actually say ("send gifts", "gifting", "orders", "gifts to employees/clients"), so common variations are missing.	3 / 5
Distinctiveness Conflict Risk	The "Goody" brand gives it a clear niche with minimal conflict risk, but generic entity names like "Projects" and "Users" create minor overlap risk with unrelated skills, so it is mostly distinct rather than fully clear-niched.	4 / 5
	Total	15 / 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/goody/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.