Name: dealersocket
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

dealersocket

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

Quality

63%

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/dealersocket/SKILL.md

Quality

Content

61%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 tightly actionable CLI integration guide with concrete commands and a solid connection-state workflow. Its main weaknesses are a padded marketing intro, missing verification for destructive action/proxy operations, and minor section redundancy.

Suggestions

Trim the opening CRM/marketing paragraph and remove filler ('Use action names and parameters as needed.') to assume Claude's competence.

Add a verification checkpoint after running actions and proxy write/DELETE requests, e.g. 'Check the output field for success; for writes, re-query to confirm the record changed.'

Fix the step numbering (label 'Step 1'/'Step 2' or drop the stray '1b' and 'Step 2' references) and consolidate 'Popular actions' with the search/run sections to remove redundancy.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph explaining what a CRM/dealership platform is ('improve customer engagement and drive revenue') and filler like 'Use action names and parameters as needed.' are unnecessary explanation that could be trimmed.	3 / 5
Actionability	Provides concrete, copy-pasteable bash commands for install, auth, connection, search, run, and proxy plus a full options table; minor gaps are unfilled placeholders (<actionId>, CONNECTION_ID, QUERY) with no fully worked end-to-end example.	4 / 5
Workflow Clarity	The connection flow has good feedback loops (poll until READY, re-poll after CLIENT_ACTION_REQUIRED), but running actions and proxy requests (which enable destructive writes/DELETE) have no verification steps, triggering the destructive-operation cap at 3; the '1b'/'Step 2' labeling is also inconsistent.	3 / 5
Progressive Disclosure	No bundle files exist and none are needed (action schemas are discovered dynamically); the single file is well-sectioned with clear headers, with only minor redundancy between 'Popular actions' and the search/run sections.	4 / 5
	Total	14 / 20 Passed

Description

66%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 what the skill does and when to use it with a specific product name, giving it strong distinctiveness and decent completeness. It is held back by generic action verbs and a single trigger phrase with no synonyms.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Search customers, create deals, and manage tasks/appointments in DealerSocket.'

Broaden the trigger with natural variations: 'Use when the user wants to query, create, or update DealerSocket customers, deals, tasks, or appointments.'

Dimension	Reasoning	Score
Specificity	Names the DealerSocket domain and lists 2-3 actions ('Manage data, records, and automate workflows'), but the verbs are generic ('manage') rather than concrete like 'extract' or 'fill', matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor.	3 / 5
Completeness	Explicitly answers both what ('DealerSocket integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with DealerSocket data.'), but the trigger is a single phrase that could be more specific, matching the 'both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	'DealerSocket' is a strong natural keyword a user would say, but supporting terms ('data', 'records', 'workflows') are generic and no synonyms or variations are offered, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	DealerSocket is a single named automotive CRM product with a distinct trigger ('interact with DealerSocket data'), giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	15 / 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/dealersocket/SKILL.md
Commit: f484c82

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