Name: chatrace
Rating: 67.2 (1 reviews)
Author: membranedev

chatrace

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

Quality

81%

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

Quality

Content

88%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 written, fully actionable integration guide with concrete CLI commands, a well-sequenced connection workflow with validation and feedback loops, and clean section organization. The only gaps are minor verbosity and inline reference tables that could be split into separate files.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and minimal conceptual padding, but contains a few trimmable bits ('Use action names and parameters as needed', 'This is the fastest way to get a connection', and light marketing framing of Membrane), placing it just below the lean anchor-5.	4 / 5
Actionability	It provides copy-paste-ready commands throughout — install, login, connection ensure/get with --wait, action list/run with --input JSON, and proxy requests with a full flag table — covering the common cases with executable specifics, matching the anchor-5 example.	5 / 5
Workflow Clarity	The connection flow is a clear sequence with explicit validation checkpoints (state READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and feedback loops (poll with --wait, then re-poll after the user acts), matching the anchor-5 'explicit validation steps; feedback loops for error recovery' example.	5 / 5
Progressive Disclosure	No bundle files exist, so the skill is a single well-organized file with clear section headers and good navigation; it stays at 4 rather than 5 because longer inline reference material (the Popular actions table and proxy flag table) could appropriately live in separate reference files.	4 / 5
	Total	18 / 20 Passed

Description

73%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 concise, third-person, and includes an explicit 'Use when' trigger tied to a distinctive named platform. Its main weakness is that the capability verbs ('manage data, records, automate workflows') are generic rather than concrete actions.

Suggestions

Replace generic verbs with concrete Chatrace capabilities, e.g. 'Send flows and text messages to contacts, manage tags and custom fields, and query contacts and pages.'

Tighten the trigger clause to list natural user phrases such as 'when the user wants to send a Chatrace flow, message a contact, or query Chatrace records'.

Dimension	Reasoning	Score
Specificity	Names the domain (Chatrace) and a couple of actions ('Manage data, records, and automate workflows'), but those actions are generic verbs rather than concrete capabilities, so it sits at the anchor-3 'names domain and 1-2 concrete actions, but not comprehensive' level and not above.	3 / 5
Completeness	It explicitly answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Chatrace data'), matching the anchor-4 example where both are present but the 'when' could be more specific; it is not 5 because neither side is fully concrete.	4 / 5
Trigger Term Quality	Includes the natural platform keyword 'Chatrace' plus 'data', 'records', and 'workflows' in the trigger clause, giving good keyword coverage; it falls short of 5 only because it lacks synonyms or file extensions, which a niche SaaS platform mostly cannot have anyway.	4 / 5
Distinctiveness Conflict Risk	'Chatrace' is a specific named platform, giving it a clear niche with distinct triggers and minimal conflict risk with other skills, matching the anchor-5 example.	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/chatrace/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.