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

goodbits

Goodbits integration. Manage Organizations, Leads, Projects, Users. Use when the user wants to interact with Goodbits data.

Quality

73%

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

Quality

Content

75%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 content is highly actionable with executable commands and a well-validated connection workflow, but it carries some marketing fluff that hurts token efficiency and inlines reference-style material that could be split out for better progressive disclosure.

Suggestions

Remove the introductory marketing paragraph about who uses Goodbits; Claude does not need audience context to run CLI commands.

Move the popular-actions table and proxy flag reference into separate reference files linked from the body to improve progressive disclosure.

Add an explicit validation/verification step after running actions (e.g. check the output field for errors) to close the workflow loop.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient executable command reference, but the opening marketing paragraph ("Goodbits is a newsletter platform that helps content creators and marketers grow their audience...") and some auth-plumbing narration are unnecessary context Claude does not need.	3 / 5
Actionability	The body is packed with copy-paste-ready commands (npm install, membrane login, connection ensure, action list/run, request) plus flag tables and a popular-actions table, covering the common cases fully.	5 / 5
Workflow Clarity	A clear install → authenticate → connect → poll-for-ready → search → run sequence exists with explicit state-based validation and a polling feedback loop, but the "skip to Step 2" references are not backed by cleanly numbered step headers, and no validation is prescribed after running actions.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers and no bundle files exist to reference, but at ~150 lines everything is inlined monolithically (popular-actions and proxy-flag tables could live in separate reference files) rather than split across one-level-deep references.	4 / 5
	Total	16 / 20 Passed

Description

71%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 answers both what and when and is clearly distinct thanks to the Goodbits brand name, but its trigger coverage is thin (only the brand name) and the managed-entity list reads as generic template content rather than Goodbits-specific capabilities.

Suggestions

Replace the generic "Manage Organizations, Leads, Projects, Users" with Goodbits-specific entities (newsletters, subscribers, snippets, content items) to match the actual skill scope.

Expand the "Use when..." clause with concrete natural triggers, e.g. "Use when the user wants to manage Goodbits newsletters, subscribers, or email content."

Dimension	Reasoning	Score
Specificity	Names the domain ("Goodbits integration") and lists several concrete managed entities ("Manage Organizations, Leads, Projects, Users"), though only a single action verb covers them, leaving minor coverage gaps versus a fully comprehensive list.	4 / 5
Completeness	Both "what" (Goodbits integration; manage Organizations/Leads/Projects/Users) and "when" ("Use when the user wants to interact with Goodbits data") are present, but the "when" clause is generic and could name concrete newsletter/subscriber use cases to be fully explicit.	4 / 5
Trigger Term Quality	The only natural trigger keyword is the brand name "Goodbits" in "Use when the user wants to interact with Goodbits data"; common variations or synonyms a user might say (newsletter, subscribers) are absent.	3 / 5
Distinctiveness Conflict Risk	"Goodbits" is a specific named application with a clear niche, so the description is unlikely to trigger for an unrelated skill.	5 / 5
	Total	16 / 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/goodbits/SKILL.md
Commit: f484c82

Reviewed: 1 day 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.