Tessl • The management layer for AI agent skills

SkillPublic

chatwork

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

Quality

71%

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

68%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.

A highly actionable, command-first skill body with excellent executable coverage of the Membrane CLI workflow. Its weaknesses are mild intro padding, incoherent step cross-references ('Step 2' is never defined), and missing validation guidance for destructive actions like delete-room and delete-message.

Suggestions

Fix the workflow numbering: label the post-connection steps explicitly (e.g., 'Step 2: Search for actions') so the two 'skip to Step 2' references resolve, and renumber or drop the orphaned '#### 1b' heading.

Add a brief verification step before destructive actions (delete-room, delete-message), e.g., confirm the target room/message ID with a get-room/get-message call and confirm with the user before running the delete.

Trim the overview paragraph ('Chatwork is a team collaboration and communication tool...') and the filler line 'Use action names and parameters as needed' to cut tokens without losing guidance.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and tables, but the intro ('Chatwork is a team collaboration and communication tool... used by businesses of all sizes to streamline internal communication') explains a concept Claude already knows, and filler like 'Use action names and parameters as needed' adds tokens without guidance.	3 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases: install ('npm install -g @membranehq/cli@latest'), login including headless completion ('membrane login complete <code>'), 'membrane connection ensure "https://go.chatwork.com/en/" --json', action list/run with '--input' JSON, and the proxy request flag table. Not below 5: no pseudocode or missing key details found.	5 / 5
Workflow Clarity	A rough install → authenticate → connect → search → run sequence exists with state-polling checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but two 'skip to Step 2' references point to a step that is never labeled, and destructive actions (delete-room, delete-message) include no verification guidance, capping this at 3.	3 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is well-sectioned with headers, an actions table, and no nested references. Fits anchor 4 rather than 5 due to minor organization gaps such as the dangling 'Step 2' cross-references and the orphaned '#### 1b' heading numbering.	4 / 5
	Total	15 / 20 Passed

Description

61%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 has an explicit 'Use when...' trigger and a clearly distinct niche (Chatwork), but its capability statement is generic — 'manage data, records, and automate workflows' could describe almost any integration skill, and the concrete actions the body actually supports (rooms, messages, tasks, contacts, files) never appear.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete Chatwork actions, e.g., 'Send messages, create rooms and tasks, and list contacts, files, and room members in Chatwork'.

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

State what the skill does operationally (interacts with Chatwork via the Membrane CLI) so the 'what' is concrete rather than implied by 'integration'.

Dimension	Reasoning	Score
Specificity	'Manage data, records, and automate workflows' is generic; the description names the Chatwork domain but lists no concrete actions (e.g., send messages, create tasks, list rooms). Fits anchor 2 ('Names the domain but actions are minimal or generic'), not 3, since no Chatwork-specific action is stated.	2 / 5
Completeness	Both parts are present: what ('Chatwork integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Chatwork data'). Not 5 because the 'what' is vague and the trigger clause lacks concrete phrases; clearly above 3 since an explicit 'Use when...' clause exists.	4 / 5
Trigger Term Quality	'Chatwork' is the key natural trigger term and 'data'/'records' add a little, but common phrases users would say — messages, rooms, tasks, contacts, files — are missing. Matches anchor 3 ('Some relevant keywords but missing common variations or synonyms') rather than 4, where those natural terms would be present.	3 / 5
Distinctiveness Conflict Risk	'Chatwork integration' names one specific app, giving a clear niche with a distinct trigger term and minimal risk of firing for the wrong skill. No generic phrasing ('helps with data') that would overlap other skills.	5 / 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/chatwork/SKILL.md
Revision: f484c82

Reviewed: 16 days ago

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.

chatwork

Table of Contents

Is this your skill?