Name: chatlayer
Rating: 59.2 (1 reviews)
Author: membranedev

chatlayer

Chatlayer integration. Manage data, records, and automate workflows. Use when the user wants to interact with Chatlayer 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/chatlayer/SKILL.md

Quality

Content

76%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 content is highly actionable with ready-to-run commands and a clear connection state-machine, and it is well-structured despite having no bundle files. Its main weakness is the lack of validation/verification steps for the destructive table-record operations it documents.

Suggestions

Add a validation/verification step before and after destructive batch actions (e.g., select-table-records to preview, then confirm with the user, then re-query to verify the delete/update took effect), which would lift workflow_clarity above the destructive-ops cap.

Trim the opening paragraph describing what Chatlayer is and the chatty framing around Membrane auth, since Claude does not need that background.

Consider moving the 'Popular actions' table and the proxy flag reference into a separate reference file so SKILL.md stays a lean overview, improving progressive_disclosure toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, copy-paste CLI commands, but the opening platform-description paragraph and a few chatty asides ('so you can focus on the integration logic rather than auth plumbing') are removable padding, fitting anchor 4 rather than 5.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for connection, polling, action search, action run, and proxying, with real flags and a parameter-syntax example, covering the common cases at anchor 5.	5 / 5
Workflow Clarity	The install→login→connect→poll→search→run sequence is clear with an explicit state-machine feedback loop, but the skill exposes destructive/batch actions (delete-table-records, update-table-record) with no validation or verification step, triggering the rubric's workflow_clarity cap at 3.	3 / 5
Progressive Disclosure	There are no bundle files; everything is inline in a single well-organized SKILL.md with clear headers and compact tables, giving good structure and easy navigation, but it remains a monolithic file with no offloading of detail, fitting anchor 4.	4 / 5
	Total	16 / 20 Passed

Description

62%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 functional and clearly tied to a named product with an explicit 'Use when' clause, but its capability verbs are generic and its trigger coverage is thin. Tightening the action list and adding concrete trigger phrases would lift specificity and completeness.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete actions tied to the popular actions table (e.g., 'List, query, insert, update, and delete table records; automate chatbot workflows').

Expand the 'Use when' clause with concrete trigger phrases a user would naturally say (e.g., 'Use when the user mentions Chatlayer bots, customer records, table data, or wants to automate chatbot workflows').

Add natural synonyms and the product's file/URL markers to broaden trigger-term coverage beyond the bare product name.

Dimension	Reasoning	Score
Specificity	It names the Chatlayer domain and a couple of actions ('Manage data, records, and automate workflows'), but the verbs are generic ('manage', 'automate') rather than concrete, so it sits at the anchor-3 level and not above.	3 / 5
Completeness	It answers both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with Chatlayer data'), but the 'when' clause is generic rather than listing concrete trigger phrases, so it does not reach a 5.	4 / 5
Trigger Term Quality	It includes the distinctive product name 'Chatlayer' plus 'data', 'records', and 'workflows', but offers no synonyms or natural variations, matching the anchor-3 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The 'Chatlayer' product name gives it a clear niche with low conflict risk, but the generic 'what' wording ('manage data, records') keeps minor overlap risk, fitting anchor 4 rather than 5.	4 / 5
	Total	14 / 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/chatlayer/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.