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

paperspace

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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/paperspace/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.

The body is highly actionable with concrete, executable Membrane CLI commands and a solid connection-state feedback loop, but it is held back by a verbose intro, a redundant actions section, and missing validation around the destructive action/proxy operations.

Suggestions

Trim the opening Paperspace overview paragraph and the "focus on integration logic rather than auth plumbing" fluff to respect token budget.

Add a validation/verification checkpoint before destructive proxy or action calls, e.g. confirm the action's outputSchema or dry-run before running DELETE/mutating actions, to lift workflow clarity.

Resolve the dangling "Step 2" reference by labeling the install/auth/connect steps as Step 1 and Step 2, and merge the redundant "Popular actions" section into "Searching for actions".

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but it opens by explaining what Paperspace is ("cloud computing platform geared towards machine learning..."), includes fluff like "so you can focus on the integration logic rather than auth plumbing", and the "Popular actions" section redundantly repeats the "Searching for actions" command, matching the anchor for mostly efficient content with some unnecessary explanation.	3 / 5
Actionability	It provides copy-paste-ready commands throughout — install, login, connection ensure/get --wait, action list/run with --input, and a proxy flags table — covering the common cases (auth, connecting, searching, running, proxying), matching the fully executable anchor.	5 / 5
Workflow Clarity	The connection flow has an explicit state feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with re-polling), but the core action-run and proxy steps (which support DELETE) lack validation/verification checkpoints; per the destructive-operation cap this cannot exceed 3, and the dangling "Step 2" reference with no Step 1/2 headers adds a sequence gap.	3 / 5
Progressive Disclosure	The single file is well-sectioned (Overview, Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with clear headers and no bundle files to reference; at ~145 lines it exceeds the 50-line simple-skill exception, and minor gaps (the redundant Popular actions section, undefined Step 2 reference) keep it just below a 5.	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 is a functional two-part statement covering what and when, anchored to a named product for distinctiveness. Its weakness is generic action language and thin trigger-term coverage that lacks synonyms or concrete Paperspace-specific capabilities.

Suggestions

Replace generic verbs with Paperspace-specific capabilities, e.g. "Launch GPU/CPU machines, manage notebooks, snapshots, and projects" to lift specificity.

Broaden trigger terms with natural synonyms such as "Paperspace machines, Gradient notebooks, GPU VMs, snapshots" so users phrasing it differently still match.

Tighten the when clause to concrete triggers, e.g. "Use when the user wants to launch or manage Paperspace machines, notebooks, or storage."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Paperspace domain and a few actions, but the verbs (manage, automate) and nouns (data, records) are generic rather than Paperspace-specific, matching the anchor that lists 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It states the what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Paperspace data"), but the when could be more specific with concrete trigger phrases, matching the anchor where both are present yet when is not maximally explicit.	4 / 5
Trigger Term Quality	The only natural keyword is "Paperspace" repeated in "interact with Paperspace data"; this matches the anchor with some relevant keywords but missing common variations or synonyms.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product Paperspace with a Paperspace-scoped trigger gives a clear niche with minimal conflict risk, though the generic "manage data/records" actions leave minor overlap with other data-management skills.	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/paperspace/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.