Name: warp
Rating: 53.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

warp

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

Quality

60%

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

Quality

Content

57%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 well-structured, command-heavy integration guide with strong actionability and a clear connection state machine. Its weaknesses are a padded intro, missing validation steps for action execution, and a monolithic single-file structure with no progressive disclosure.

Suggestions

Trim the introductory paragraph describing what Warp the product is; assume Claude's competence and lead directly with the integration workflow.

Add an explicit validation/verification step after running actions (e.g., inspect the `output` field and confirm success before proceeding), since this skill performs operations against external records.

Move the inline entity overview list and proxy-flags table into separate reference files and link to them, so the main SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-driven content, but the opening paragraph explaining what Warp the product is and 'focus on the integration logic rather than auth plumbing' are unnecessary background Claude does not need.	3 / 5
Actionability	Provides many concrete, copy-paste-ready CLI commands (install, login, connection ensure, action run with --input, proxy flags) covering common cases, with only minor placeholder-substitution gaps.	4 / 5
Workflow Clarity	The connection sub-workflow is well-sequenced with state-based checkpoints and repolling, but the core action-execution workflow (running actions against records) lacks validation/verification steps, capping clarity at 3 per the destructive/batch feedback-loop rule.	3 / 5
Progressive Disclosure	Has clear section headers and good internal organization, but all content is inlined in a single ~160-line file with zero references to separate files; the entity list and proxy-flag table are bulk content that could be split out.	3 / 5
	Total	13 / 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 correctly pairs a 'what' and a 'when' clause and anchors on a specific product (Warp), giving it solid completeness and distinctiveness. Weaknesses are generic action verbs and thin trigger-term coverage with few natural synonyms.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Warp capabilities (e.g., search/run Warp actions, send messages, manage records via the Membrane CLI).

Expand the 'Use when' clause with multiple natural trigger phrases and synonyms (e.g., 'Use when the user wants to query Warp records, send Warp messages, or automate Warp workflows').

Add concrete trigger terms users would actually say (Warp records, Warp messaging, Warpcast) to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	Names the Warp domain plus a couple of actions ('Manage data, records, and automate workflows') but the actions are generic and not comprehensive, matching the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	States both what ('Warp integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Warp data.'), but the 'when' is a single generic trigger rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	Provides the relevant keyword 'Warp' via 'interact with Warp data' but lacks common variations, synonyms, or file extensions, matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific Warp product gives a mostly-distinct niche with minimal overlap risk, though the trigger 'interact with Warp data' is generic enough to keep it below a clean 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/warp/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.