Tessl • The management layer for AI agent skills

SkillPublic

acquire

Acquire integration. Manage data, records, and automate workflows. Use when the user wants to interact with Acquire data.

Quality

72%

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/acquire/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 body is a well-organized, command-first integration guide with explicit connection-state handling that makes the core workflow easy to follow. Remaining gaps are small: dangling 'Step 2' references, a placeholder login flag, and a few low-value filler sections.

Suggestions

Fix the step references: label the connection sections ('1. Connect', '2. Run actions') so 'skip to Step 2' resolves, and rename the unanchored '#### 1b' heading.

Fill in the empty Description column of the Popular actions table, or drop it, so action selection doesn't require guessing; document the value --tenant expects in the login command.

Add a brief caution/check step for destructive actions (delete-contact, delete-company) — e.g., confirm the record with a get-action before deleting.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable membrane commands with minimal over-explanation, but a few tokens could be trimmed — the cryptic 'Acquire Overview' bullet tree ('Company / Document / Version / User'), the filler line 'Use action names and parameters as needed.', and the garbled 'Agent Types' sentence ('Those will be used to adjust tooling to be used best with your harness').	4 / 5
Actionability	Nearly every section gives copy-paste-ready commands (npm install, membrane login, connection ensure, action list/run, request with a full flags table). Minor gaps: 'membrane login --tenant' shows the flag without the value it takes, and the Popular actions table's empty Description column gives no hint of when to pick each action.	4 / 5
Workflow Clarity	The connect → poll state → handle clientAction → search actions → run sequence is clear, with explicit state-machine checkpoints (READY / CLIENT_ACTION_REQUIRED with clientAction fields / CONFIGURATION_ERROR). Minor gaps: 'skip to Step 2' references a Step 2 that is never labeled, and there is no guidance on verifying action output or extra care before destructive actions like delete-contact.	4 / 5
Progressive Disclosure	A single-file skill (~155 lines) with no bundle files; sections are well-organized with headers, tables, and code blocks appropriately placed, and nothing needs to be split out. Minor organization gaps: inconsistent step numbering ('#### 1b' with no labeled 1 or 2) and the low-value Acquire Overview section.	4 / 5
	Total	16 / 20 Passed

Description

57%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 has an explicit trigger clause and benefits from naming a distinct product, but it wastes its capability statement on generic language. Concrete verbs that reflect the skill's actual capabilities would sharpen both specificity and trigger quality.

Suggestions

Replace 'Manage data, records, and automate workflows' with 2-3 concrete capabilities drawn from the skill body, e.g., 'Send messages, manage cases, and create/update contacts and companies in Acquire'.

Expand the trigger clause with natural task-level phrases users would say: 'Use when the user mentions Acquire, live chat, customer contacts, support cases, or wants to automate Acquire workflows'.

State the 'when' with concrete trigger objects (contacts, cases, companies) rather than the abstract 'interact with Acquire data'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Acquire integration') but its actions are purely generic — 'Manage data, records, and automate workflows' names no concrete operation (e.g., send messages, create cases, manage contacts), matching the anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	Both parts are present — a 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when...' trigger clause — but both are generic, matching 'Has both what and when; when could be more explicit or specific'. Not 3 because the 'when' is explicit rather than missing or only weakly implied.	4 / 5
Trigger Term Quality	'Acquire' is a relevant, specific keyword in 'Use when the user wants to interact with Acquire data', but all common task-level variations users would naturally say (live chat, contacts, cases, support tickets) are missing, fitting 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	The named product 'Acquire' gives the skill a clear niche with minimal conflict risk when mentioned, but the generic 'Manage data, records, and automate workflows' phrasing could overlap with other data-management skills, fitting 'mostly distinct; minor overlap risk'.	4 / 5
	Total	13 / 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/acquire/SKILL.md
Revision: f484c82

Reviewed: 1 day ago

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.

acquire

Table of Contents

Is this your skill?