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

Blog Docs Log in Get started

twist

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

Quality

Content

78%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 actionable and well-structured, leading Claude through install, auth, connection lifecycle, and action execution with executable commands and a state-driven polling loop. Its main gaps are a dangling 'Step 2' reference and a little concept padding Claude does not need.

Suggestions

Label or rename the target section so the 'skip to Step 2' instruction resolves to a real, findable heading.

Trim inferable context such as the Slack comparison and the 'rather than auth plumbing' aside to tighten the token budget.

Replace 'Use action names and parameters as needed' with a concrete one-line example of running an action with parameters.

Dimension	Reasoning	Score
Conciseness	Largely efficient with code blocks and a flag table, but a few sentences pad concepts Claude could infer (the Slack comparison and the 'focus on integration logic rather than auth plumbing' aside).	4 / 5
Actionability	Provides concrete, copy-paste-ready commands for install, auth, connections, action search/run, and proxying, with only minor placeholder-driven gaps and one vague line ('Use action names and parameters as needed').	4.5 / 5
Workflow Clarity	The connection flow is well sequenced with explicit state transitions (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-retry feedback loop, but the referenced 'Step 2' is never clearly labeled, leaving a navigation gap.	4 / 5
Progressive Disclosure	Content is organized into clearly headed sections within a single SKILL.md with no nested or buried references; with no bundle files present and a small inline flag table, structure is good though not maximally split.	4 / 5
	Total	16.5 / 20 Passed

Description

60%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 successfully states both the capability and a use trigger, and the explicit Twist app name keeps conflict risk low. Its main weakness is generic, non-Twist-specific action language and missing natural synonyms a user would actually say.

Suggestions

Replace generic verbs with concrete Twist capabilities, e.g. 'Manage Twist threads, messages, and conversations; automate workflows.'

Add natural user-facing trigger phrases such as 'Use when the user wants to send or read Twist threads, messages, or manage Twist conversations.'

Include synonyms or Twist-specific terms (threads, channels, asynchronous messages) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the Twist domain and a couple actions ('Manage data, records, and automate workflows'), but the actions are generic verbs rather than concrete Twist-specific capabilities like threads or messages.	2.5 / 5
Completeness	Explicitly answers both what ('Twist integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Twist data'), though the trigger could be more specific.	4 / 5
Trigger Term Quality	Includes some relevant keywords ('Twist', 'data', 'records') but misses the natural phrases users actually say, such as threads, messages, channels, or asynchronous communication.	3 / 5
Distinctiveness Conflict Risk	Naming a specific app (Twist) with a targeted trigger makes it mostly distinct with only minor overlap risk, despite the generic 'manage data' phrasing.	4 / 5
	Total	13.5 / 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/twist/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.