Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

amocrm

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

Quality

69%

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 body delivers copy-paste-ready Membrane CLI commands with a mostly clear connection-to-action workflow and useful state-based validation guidance. Its weaknesses are padded explanatory content (the CRM intro paragraph, an empty 'Popular actions' section) and a dangling 'Step 2' reference that breaks the otherwise good step sequencing.

Suggestions

Cut the introductory paragraph explaining what AmoCRM/CRM is and delete the 'Popular actions' section (or populate it with actual action names) — it currently just repeats the action-discovery command.

Replace the dangling 'skip to Step 2' and '1b' references with an explicit numbered sequence (Step 1: connect, Step 2: discover actions, Step 3: run actions) so the workflow reads as one coherent process.

Add one complete proxy request example with a real AmoCRM endpoint (e.g. /api/v4/leads) alongside the flag table.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what AmoCRM is ('customer relationship management platform geared towards sales teams... helps businesses track leads') — knowledge Claude already has — and 'Use action names and parameters as needed.' is a filler line. The 'Popular actions' section duplicates the earlier action-discovery command without listing any actions. Mostly efficient with some unnecessary explanation matches anchor 3 rather than anchor 4's 'minor instances'.	3 / 5
Actionability	Concrete, executable commands throughout: 'npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://www.amocrm.com/" --json', 'membrane action run <actionId> --input ... --json', plus a complete proxy flag table. Minor gaps keep it below anchor 5: the proxy section shows flags but no full example with a real endpoint, and the 'Popular actions' heading promises actions but delivers only a discovery command.	4 / 5
Workflow Clarity	The sequence is followable (install CLI, login including headless variant, connection ensure, poll with --wait, handle clientAction states, search and run actions) with validation via state polling and an explicit error branch for CONFIGURATION_ERROR. However 'skip to Step 2' dangles — no Step 1/Step 2 headings exist, only an unnumbered '1b' — a minor gap that fits anchor 4 rather than anchor 5.	4 / 5
Progressive Disclosure	A single SKILL.md with well-organized, clearly headed sections and no nested references, so navigation is easy. At roughly 140 lines it exceeds the under-50-line simple-skill exception, and content like the proxy flag table and clientAction schema detail could arguably live in a reference file, which fits anchor 4's 'minor organization gaps' rather than anchor 5.	4 / 5
	Total	15 / 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 'Use when' clause and a clearly named niche platform, but the capability statement is generic buzzword-level phrasing rather than concrete actions. Trigger coverage relies almost entirely on the product name, missing the natural vocabulary (leads, deals, contacts) users would use.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete actions drawn from the skill's own entity model, e.g. 'Create and update leads, contacts, companies, and tasks, log notes, and automate sales workflows in AmoCRM.'

Add natural trigger terms users would actually say: leads, deals, contacts, CRM records, pipeline, e.g. 'Use when the user mentions AmoCRM, leads, deals, or their CRM contacts and tasks.'

Dimension	Reasoning	Score
Specificity	The domain (AmoCRM) is named, but the stated actions 'Manage data, records, and automate workflows' are generic with no concrete operations (e.g. create/update leads, contacts, tasks). This matches the anchor 'Names the domain but actions are minimal or generic' and falls short of anchor 3, which requires concrete actions.	2 / 5
Completeness	Both parts are present: 'AmoCRM integration. Manage data, records, and automate workflows' answers what (though vaguely) and 'Use when the user wants to interact with AmoCRM data' explicitly answers when. The 'when' could be more specific and the 'what' lacks concrete trigger phrases, so it fits anchor 4 rather than anchor 5.	4 / 5
Trigger Term Quality	'AmoCRM' and 'interact with AmoCRM data' give one strong natural keyword, but common variations users would say (leads, deals, contacts, CRM records, pipeline) are missing. Some relevant keywords without synonyms matches anchor 3 rather than anchor 4's 'good keyword coverage'.	3 / 5
Distinctiveness Conflict Risk	The AmoCRM-specific naming and trigger clause create a clear niche, but the generic middle sentence 'Manage data, records, and automate workflows' introduces minor overlap risk with generic data-management skills. Mostly distinct with minor overlap risk matches anchor 4 rather than anchor 5.	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/amocrm/SKILL.md
Revision: f484c82

Reviewed: 16 days 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.

amocrm

Table of Contents

Is this your skill?