Name: resurface
Rating: 56.8 (1 reviews)
Author: membranedev

resurface

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

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/resurface/SKILL.md

Quality

Content

67%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, mostly actionable guide built around concrete Membrane CLI commands and a state-based connection workflow, weakened mainly by minor padding and an unlabeled "Step 2" reference.

Suggestions

Trim the introductory explanation of what Resurface is and remove filler phrases ("so you can focus on the integration logic rather than auth plumbing") to improve token efficiency.

Label the post-connection workflow explicitly as "Step 2: Search and run actions" so the repeated "skip to Step 2" references resolve to a real section.

Add one fully-substituted end-to-end worked example (a concrete connectionId and action run) so the action guidance is copy-paste ready without placeholder inference.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands, but the intro paragraph ("Resurface is an API usage intelligence platform...") and phrases like "so you can focus on the integration logic rather than auth plumbing" are explanatory padding that could be trimmed, fitting the mostly-efficient-but-could-be-tightened anchor rather than the efficient anchor at 4.	3 / 5
Actionability	Provides many concrete, copy-paste-ready commands (install, login, connection ensure, action run, request) plus a flags table, but uses unsubstituted placeholders (CONNECTION_ID, <actionId>, <id>) and offers no full end-to-end worked example, so it is mostly-executable with minor gaps rather than fully copy-paste at 5.	4 / 5
Workflow Clarity	The connection flow is a clear state-machine sequence with explicit checkpoints and a feedback loop (polling after CLIENT_ACTION_REQUIRED until READY), but the text repeatedly says "skip to Step 2" without ever labeling a Step 2, a minor sequencing gap that keeps it below the explicit-checklist anchor at 5.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no bundle files to reference, giving good structure with only minor organization gaps; not a 5 because the detailed clientAction schema and flags table are inlined where a one-level reference could help.	4 / 5
	Total	15 / 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 answers both what and when with an explicit Use-when clause and is tied to a distinct product, but its capability phrasing is generic and the trigger keywords lack synonyms or common variations.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete actions users would perform, e.g. "query usage logs, inspect API events, and configure recording rules".

Add natural trigger synonyms and variations, such as "API traffic", "API logging", or "usage analytics", so the skill matches how users actually phrase the need.

Make the "Use when" clause more specific, e.g. "Use when the user wants to log, monitor, or audit API traffic in Resurface".

Dimension	Reasoning	Score
Specificity	Names the domain (Resurface) and lists a few actions — "Manage data, records, and automate workflows" — but the verbs are generic and coverage is not comprehensive, fitting the 1-2 concrete actions anchor rather than the 4-anchor's several specific actions.	3 / 5
Completeness	Provides a clear "what" ("Resurface integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Resurface data"), matching the both-present-but-when-could-be-more-specific anchor; not a 5 because the trigger phrase is generic rather than concrete.	4 / 5
Trigger Term Quality	Includes relevant keywords ("Resurface", "data", "records", "workflows") and a natural "interact with Resurface data" phrase, but misses common variations or synonyms, landing on the some-relevant-keywords anchor rather than the good-coverage anchor at 4.	3 / 5
Distinctiveness Conflict Risk	Resurface is a specific niche product giving clear distinctiveness and low conflict risk, but the generic "Manage data, records, and automate workflows" phrasing introduces minor overlap risk with other data-integration skills, keeping it just below the clear-niche anchor at 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/resurface/SKILL.md
Commit: f484c82

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