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

Blog Docs Log in Get started

amocrm

AmoCRM integration. Manage data, records, and automate workflows. Use when the user wants to interact with AmoCRM 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/amocrm/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, mostly actionable guide to driving AmoCRM through the Membrane CLI, with a strong state-machine-based connection flow. Its main weaknesses are a padded introductory paragraph explaining concepts Claude already knows and some inconsistent step numbering that slightly muddies the workflow.

Suggestions

Remove or trim the opening 'AmoCRM is a customer relationship management platform...' paragraph; assume Claude knows what a CRM is and lead directly with the integration purpose.

Fix the step numbering: label the action-search/run section as 'Step 2' so the 'skip to Step 2' reference resolves, and add a '1a' or relabel '1b' to a non-numbered heading.

Add a brief validation note in the 'Running actions' section for error responses (e.g., check the JSON output for error fields and re-query the action's inputSchema) to close the loop on failed action calls.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands, but the opening paragraph ('AmoCRM is a customer relationship management platform geared towards sales teams...') explains what AmoCRM is — context Claude does not need — and a few sentences carry light padding.	3 / 5
Actionability	Provides concrete, copy-paste-ready membrane commands (login, connection ensure, action list/run, request) with real flags and JSON examples; a few placeholders like /path/to/endpoint keep it just short of fully executable for all cases.	4 / 5
Workflow Clarity	The connection flow is sequenced with a state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling feedback loops, but numbering is inconsistent ('Step 2' is referenced but unlabeled, '1b' appears without a '1a').	4 / 5
Progressive Disclosure	No bundle files are present, but the single SKILL.md is well-organized into clear sections (Install, Authentication, Connecting, Searching actions, Proxy, Best practices) with content appropriately placed in one file.	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 cleanly states the domain and includes an explicit 'Use when...' trigger, but the capability list is generic ('manage data, records, automate workflows') rather than naming the concrete AmoCRM entities and operations. It is distinct because of the named product, but it undersells the specific actions available.

Suggestions

Replace generic verbs with concrete AmoCRM operations, e.g. 'Manage leads, contacts, companies, tasks, and notes, and automate sales workflows.'

Expand the trigger clause with the entity terms users actually say: 'Use when the user wants to manage AmoCRM leads, contacts, companies, tasks, or notes.'

Drop the redundant 'Manage data, records' phrasing in favor of the named entities already listed in the body's Overview section.

Dimension	Reasoning	Score
Specificity	Names the AmoCRM domain and a few action categories ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete entity-level operations like leads, contacts, or deals.	3 / 5
Completeness	Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with AmoCRM data'); the 'what' could be more concrete, keeping it just below a 5.	4 / 5
Trigger Term Quality	Includes the relevant product term 'AmoCRM' and 'data', but misses the natural entity variations and synonyms (leads, contacts, tasks, deals) a user would actually say.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product AmoCRM gives it a clear niche with low conflict risk, but the generic 'manage data, records' phrasing retains minor overlap with other CRM skills.	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/amocrm/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.