Name: getaccept
Rating: 56.8 (1 reviews)
Author: membranedev

getaccept

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

Quality

65%

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

Quality

Content

67%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 a well-structured, actionable integration guide with executable commands and clear connection-state checkpoints, held back slightly by some introductory padding and a couple of unclear step cross-references.

Suggestions

Trim the sales-enablement intro paragraph and the bare 'Use action names and parameters as needed.' line to improve token efficiency.

Clarify the 'skip to Step 2' references by labeling the searching/running-actions section as 'Step 2', and add a brief note on handling action-run errors.

Consider moving the detailed clientAction field breakdown or the Popular actions table into a reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes some unnecessary prose such as the sales-enablement intro paragraph and a thin 'GetAccept Overview' list ending in 'Use action names and parameters as needed.' that could be tightened.	3 / 5
Actionability	It provides copy-paste ready bash commands for every phase (login, connection ensure, action list/run, request proxy) plus a Popular actions table with concrete keys, with only minor gaps such as placeholder values for parameters.	4 / 5
Workflow Clarity	The install → authenticate → connect → poll-for-ready → search → run sequence is clear with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) as a feedback loop, though 'skip to Step 2' references an unlabeled step and action-run error recovery is not addressed.	4 / 5
Progressive Disclosure	Content is well organized into clear sections (Overview, Working with GetAccept, Popular actions, Best practices) with no nested references, though all material is inline with no bundle files for the longer reference-style tables.	4 / 5
	Total	15 / 20 Passed

Description

62%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 successfully answers both what and when with a distinctive brand trigger, but relies on a single generic action verb and lacks task-level keyword variations that would help users naturally invoke it.

Suggestions

Replace the generic 'Manage' with a few concrete verbs (e.g. 'Create, update, and query Deals, Persons, Organizations...') to raise specificity.

Expand the 'when' clause with concrete task triggers users would say, e.g. 'Use when the user wants to send documents for e-signature, manage deals, or look up contacts in GetAccept.'

Dimension	Reasoning	Score
Specificity	The description lists six concrete domain objects ('Deals, Persons, Organizations, Leads, Projects, Pipelines') but the only action verb is the generic 'Manage', so it names the domain and objects without comprehensive concrete actions.	3 / 5
Completeness	Both a clear 'what' ('Manage Deals, Persons...') and a 'when' ('Use when the user wants to interact with GetAccept data') are present, though the 'when' could be more specific about particular tasks.	4 / 5
Trigger Term Quality	The natural keyword 'GetAccept' is present in the trigger clause, but there are no task-level synonyms or variations (e.g. e-signatures, documents, proposals) that users would naturally say.	3 / 5
Distinctiveness Conflict Risk	The brand name 'GetAccept' makes the skill mostly distinct with minimal overlap risk, though the single trigger phrase is narrow rather than a rich set of distinct triggers.	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/getaccept/SKILL.md
Commit: f484c82

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