Name: lawmatics
Rating: 62.4 (1 reviews)
Author: membranedev

lawmatics

Lawmatics integration. Manage Matters, Contacts, Automations, Forms, Reports, Users. Use when the user wants to interact with Lawmatics data.

Quality

74%

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

Quality

Content

82%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 skill body is highly actionable with executable CLI commands and a clear connection workflow, supported by good section structure; its main weaknesses are some padded prose and the absence of explicit validation feedback loops for action execution.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and tables, but it includes some padded prose (e.g. the introductory "Lawmatics is a CRM..." paragraph and lengthy clientAction explanations) that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready membrane CLI commands with flags, a popular-actions table, and concrete parameter-passing examples covering the common cases.	5 / 5
Workflow Clarity	The connection flow is well-sequenced with explicit polling states and a clear READY/CLIENT_ACTION_REQUIRED branch, but there are no validation/retry checkpoints for destructive or batch action runs, leaving a minor gap.	4 / 5
Progressive Disclosure	Content is organized into clear sections (Overview, Install, Authentication, Connecting, Actions, Best practices) with no bundle files to reference, though the popular-actions table is somewhat large and could be split if a references directory existed.	4 / 5
	Total	17 / 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 is clear and well-structured with explicit what/when guidance and strong distinctiveness, but the repeated "Manage" verb limits specificity and trigger-term coverage is thin on natural synonyms.

Suggestions

Replace the generic "Manage ..." with a few distinct concrete verbs (e.g. "List, create, and update Matters and Contacts; send Forms; run Automations and Reports") to raise specificity.

Add natural trigger phrases users would say, such as "Use when the user wants to manage law firm leads, clients, cases, or automate intake in Lawmatics."

Include a synonym or file/extension hint (e.g. "law firm CRM", "intake") so the trigger matches how users actually phrase the request.

Dimension	Reasoning	Score
Specificity	It names the Lawmatics domain and several concrete entities ("Manage Matters, Contacts, Automations, Forms, Reports, Users") but the actions are all the same generic verb "Manage", leaving minor gaps in distinct concrete actions.	4 / 5
Completeness	It states both what ("Manage Matters, Contacts...") and when ("Use when the user wants to interact with Lawmatics data"); the "when" clause is explicit but somewhat generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	"interact with Lawmatics data" gives one relevant phrase and the entity names help, but it lacks natural variations or synonyms a user would actually say (e.g. "law firm CRM", "leads", "cases").	3 / 5
Distinctiveness Conflict Risk	"Lawmatics integration" targeting a specific named platform creates 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/lawmatics/SKILL.md
Commit: f484c82

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