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

Blog Docs Log in Get started

attio

Attio integration. Manage crm data, records, and workflows. Use when the user wants to interact with Attio 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/attio/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 well-validated connection workflow, and it is reasonably concise and well-sectioned. Its main gap is the absence of validation/verification guidance around the destructive and batch actions it exposes.

Suggestions

Add explicit validation or confirmation steps before destructive actions (e.g., 'Confirm the record ID before running delete-record; verify the result with get-record afterwards') to lift workflow clarity above the cap.

Move the bulk popular-actions reference table into a separate references file and link to it from the body to improve progressive disclosure.

Trim the introductory paragraph about who uses Attio and other restated Membrane descriptions to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste command blocks and tables, but includes minor over-explanation such as the opening paragraph about who uses Attio and prose restating what Membrane handles, which could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action list/run, request) with concrete flags and JSON examples covering the common cases.	5 / 5
Workflow Clarity	The connection setup flow has a clear sequence with explicit polling/state checkpoints and a retry feedback loop, but the skill involves destructive and batch operations (delete-record, delete-task, list records) with no validation or verification steps, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Content is well organized into clear sections with no nested references and no bundle files to navigate, but the large 20-row popular-actions table and proxy flag table are inline reference material that could be split into separate files, leaving minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

73%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 clear, third-person, and provides an explicit 'Use when' trigger tied to a distinct product niche. Its main weakness is the generic verb 'Manage', which undersells the concrete capabilities and keeps specificity and completeness below the top anchors.

Suggestions

Replace the generic verb 'Manage' with concrete actions (e.g., 'List, create, update, and delete records, list entries, tasks, and notes') to lift specificity and completeness.

Add natural trigger synonyms users might say, such as 'contacts', 'companies', 'deals', or 'Attio CRM', to broaden trigger-term coverage.

Keep the explicit 'Use when the user wants to interact with Attio data' clause but make the 'what' list match the actual action surface described in the body.

Dimension	Reasoning	Score
Specificity	Names the domain (Attio/CRM) and enumerates entity targets ('crm data, records, and workflows'), but the single verb 'Manage' is generic rather than concrete actions, matching the anchor for domain plus 1-2 actions that are not comprehensive.	3 / 5
Completeness	Explicitly answers both 'what' ('Manage crm data, records, and workflows') and 'when' ('Use when the user wants to interact with Attio data'); the 'when' is present and reasonably explicit but the 'what' is generic, so it sits below the fully concrete trigger-phrase anchor.	4 / 5
Trigger Term Quality	Includes natural user-facing terms ('Attio', 'crm data', 'records', 'interact with Attio data') with good coverage; a few common synonyms or phrasings are missing, so it does not reach comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	'Attio integration' targets a specific named product with a distinct trigger ('interact with Attio data'), giving it a clear niche with minimal overlap risk against other skills.	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/attio/SKILL.md
Commit: f484c82

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