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

dealmachine

DealMachine integration. Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more. Use when the user wants to interact with DealMachine 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/dealmachine/SKILL.md

Quality

Content

72%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 complete executable commands and a well-validated connection workflow, but it is weakened by the absence of verification steps for destructive/batch actions and by inlining large reference tables rather than splitting them into a referenced file.

Suggestions

Add a validation/confirmation checkpoint before destructive or batch actions (e.g., confirm lead IDs and show a dry-run before running delete-lead or add-lead-to-lists).

Move the Popular actions table and the DealMachine entity overview into a separate REFERENCE.md (or similar) and link to it from the body to improve progressive disclosure.

Trim the introductory paragraph explaining what DealMachine is and the Membrane auth rationale, keeping only what Claude needs to operate the CLI.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands and tables with only minor over-explanation (e.g., the introductory "DealMachine is a mobile app for real estate investors..." and "so you can focus on the integration logic rather than auth plumbing") that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready executable commands for every stage (login, connection ensure, connection get --wait, action list, action run, request) with --json flags and a parameterized input example, covering the common cases.	5 / 5
Workflow Clarity	The connection workflow is well sequenced with polling checkpoints and state handling, but the skill exposes destructive (delete-lead) and batch (add-lead-to-lists, remove-lead-from-lists) actions without any validation or verification guidance, capping workflow clarity at 3.	3 / 5
Progressive Disclosure	Sections are organized, but the ~175-line body inlines substantial reference content (a 20-row Popular actions table and an entity overview list) that, for a skill over 50 lines, would be better placed in a separate reference file with clear navigation.	3 / 5
	Total	15 / 20 Passed

Description

78%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 clearly identifies a specific named integration and provides both a capability list and an explicit use-when clause. It is strong on distinctiveness and completeness, slightly less so on action-verb specificity and trigger-term variety.

Dimension	Reasoning	Score
Specificity	"Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more" lists several specific entities, but the only action verb is the generic "Manage", leaving minor gaps in concrete action coverage.	4 / 5
Completeness	States both what ("DealMachine integration. Manage Deals, Persons, Organizations, Leads, Projects, Pipelines") and when ("Use when the user wants to interact with DealMachine data"), but the trigger clause is single and could be more explicit with varied phrases.	4 / 5
Trigger Term Quality	Includes the natural product name "DealMachine" plus domain nouns (Deals, Leads, Persons, Pipelines) and the phrase "interact with DealMachine data", giving good keyword coverage, though synonyms and file extensions are absent.	4 / 5
Distinctiveness Conflict Risk	"DealMachine" is a named niche real-estate product with a distinct trigger ("Use when the user wants to interact with DealMachine data"), giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	17 / 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/dealmachine/SKILL.md
Commit: f484c82

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