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

beanstalk

Beanstalk integration. Manage Persons, Organizations, Deals, Leads, Activities, Notes and more. Use when the user wants to interact with Beanstalk 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/beanstalk/SKILL.md

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.

The body is highly actionable with executable commands and a solid connection-state feedback loop, and it is well-structured with no nested references. Its main weaknesses are missing validation/confirmation before destructive actions (delete, production deploy) and a dangling "Step 2" reference under a section labeled "1b" with no "1a".

Suggestions

Add a validation/confirmation checkpoint before destructive or deployment actions, e.g. "Before running delete-* or create-release, confirm the target with the user."

Fix the broken step numbering: the "1b. Wait for the connection" heading and the "skip to Step 2" reference have no matching "1a" or labeled "Step 2".

Trim marketing-style padding such as "so you can focus on the integration logic rather than auth plumbing."

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable commands, tables, and state-handling lists with only minor prose padding (e.g. "so you can focus on the integration logic rather than auth plumbing") that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready bash commands for install, login, connection, action search, action run (with JSON input), and proxy requests, plus a flag-options table covering the common cases.	5 / 5
Workflow Clarity	The connection flow has a clear polling feedback loop (BUILDING → CLIENT_ACTION_REQUIRED → re-poll), but destructive operations (delete-repository, delete-user, create-release to production) appear in the popular-actions table with no validation/confirmation checkpoint before running them, capping this dimension at 3.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections (Overview, Authentication, Connecting, Searching, Popular actions, Running actions, Proxy, Best practices) with no nested references; the large inline actions table is reasonable but keeps the file over 50 lines, so it is not a perfect 5.	4 / 5
	Total	16 / 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 provides both a capability statement and an explicit trigger clause, but its enumerated entities (Persons, Organizations, Deals, Leads) misrepresent the skill, which actually manages Git repositories, branches, changesets, and code reviews. This inaccuracy drags down specificity and creates mild conflict risk with CRM skills.

Suggestions

Replace the entity list with the skill's actual capabilities, e.g. "Manage repositories, branches, changesets, code reviews, releases, and users."

Expand the trigger clause with concrete natural phrases, e.g. "Use when the user wants to manage Beanstalk repositories, review code, or trigger deployments."

Drop the vague "and more" padding to tighten the description.

Dimension	Reasoning	Score
Specificity	The single verb "Manage" is applied to a list of entities ("Persons, Organizations, Deals, Leads, Activities, Notes and more"), but "and more" is vague padding and the listed entities do not match the skill's actual Git-SCM capabilities, which is an over-claim.	3 / 5
Completeness	Both a "what" ("Beanstalk integration. Manage …") and a "when" ("Use when the user wants to interact with Beanstalk data") are present; the "when" is explicit but generic rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	It surfaces the natural term "Beanstalk" (and "Beanstalk data") in an explicit trigger clause, but offers no synonyms, related phrases, or file/extension variations users might say.	3 / 5
Distinctiveness Conflict Risk	The named app "Beanstalk" gives it a clear niche with minimal conflict risk, but the CRM-style entity list could cause it to surface for CRM/person-management requests instead of the intended Git-SCM skill.	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/beanstalk/SKILL.md
Commit: f484c82

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