Name: chatwork
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

chatwork

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

Quality

66%

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

Quality

Content

75%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 concrete Membrane CLI commands and a clear connection workflow including state-driven validation. Its main weaknesses are mild introductory padding and a dangling 'Step 2' reference that slightly muddies the sequence.

Suggestions

Trim the opening 'Chatwork is a team collaboration...' paragraph and the 'so you can focus on the integration logic' phrasing to reduce padding Claude does not need.

Resolve the 'skip to Step 2' reference by explicitly labeling the searching/running-actions sections as Step 2, or reword to 'skip to Searching for actions'.

Consider moving the 20-row popular-actions table into a references/ file referenced from the body to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but the opening paragraph explaining what Chatwork is ('a team collaboration and communication tool, similar to Slack...') and phrasing like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary padding Claude does not need.	3 / 5
Actionability	It provides fully executable, copy-paste ready commands throughout (npm install, membrane login, connection ensure, action list/run, request) plus a concrete popular-actions table and proxy flag table covering the common cases.	5 / 5
Workflow Clarity	The install → login → connect → poll-for-ready → search → run sequence is clear with state checkpoints and a feedback loop (poll again after user action), but the 'skip to Step 2' reference points to no labeled Step 2, a minor sequencing gap.	4 / 5
Progressive Disclosure	Content is well organized into clearly headed sections with no nested references and easy navigation; the only gap is the large inline popular-actions table that could live in a separate reference file, but no bundle files exist to split into.	4 / 5
	Total	16 / 20 Passed

Description

57%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 correctly identifies the product and includes an explicit 'Use when' clause, satisfying basic completeness. It is held back by generic action verbs and the absence of natural Chatwork task terms (messages, rooms, tasks).

Suggestions

Replace generic verbs with concrete Chatwork actions, e.g. 'Send messages, manage chat rooms and tasks, and list contacts in Chatwork'.

Expand the trigger clause with natural terms users say, e.g. 'Use when the user wants to send Chatwork messages, manage rooms or tasks, or work with Chatwork contacts and files'.

Add file-format or entity synonyms (rooms, tasks, messages, contacts) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain (Chatwork) but the actions 'Manage data, records, and automate workflows' are minimal and generic rather than concrete Chatwork operations like sending messages or managing rooms/tasks.	2 / 5
Completeness	Both a 'what' (Chatwork integration; manage data, records, automate workflows) and a 'when' ('Use when the user wants to interact with Chatwork data') are present, though the trigger is generic rather than concrete.	4 / 5
Trigger Term Quality	The main keyword 'Chatwork' appears, but natural task terms users would actually say (messages, rooms, tasks, team chat) are missing, leaving only generic variations.	3 / 5
Distinctiveness Conflict Risk	Targeting a specific named product (Chatwork) gives it a clear niche with low conflict risk, but the generic 'interact with Chatwork data' phrasing leaves minor overlap with general integration skills.	4 / 5
	Total	13 / 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/chatwork/SKILL.md
Commit: f484c82

Reviewed: 4 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.