Name: squarespace
Rating: 62.4 (1 reviews)
Author: membranedev

squarespace

Squarespace integration. Manage Websites, Forms, Products, Orders, Customers, Campaigns. Use when the user wants to interact with Squarespace data.

Quality

73%

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/squarespace/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 skill body built on concrete, executable Membrane commands with a clear connection workflow. It loses points on conciseness (concept re-explanation) and on workflow clarity because destructive proxy/action operations lack verification steps.

Suggestions

Trim the introductory "Squarespace is a website builder..." paragraph and other auth-plumbing commentary that Claude already knows.

Add a verification checkpoint for destructive proxy/action runs (e.g., re-fetch or dry-run before POST/PUT/DELETE, confirm the returned id/state).

Consider moving the clientAction state spec and the proxy flag table into a short reference file linked from SKILL.md to tighten the overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands, but it opens by explaining what Squarespace is ("Squarespace is a website builder and hosting provider...") and includes prose like "so you can focus on the integration logic rather than auth plumbing" that Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready, fully flagged commands for every phase (login, connection ensure/get with --wait, action list/run with --input, request with a full flag table), covering the common cases concretely.	5 / 5
Workflow Clarity	The connection flow is well-sequenced with state checks and a poll-after-action feedback loop, but the destructive proxy/action operations (POST/PUT/DELETE) have no validation or verification checkpoint, which caps this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	Content is well-sectioned (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references and no bundle files, though some inlined detail (the clientAction state spec and proxy flag table) could live in reference files.	4 / 5
	Total	15 / 20 Passed

Description

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

A solid description that names the domain, lists managed entities, and includes an explicit "Use when" trigger clause. It is held back from the top band by a single generic verb and a one-phrase trigger that could enumerate more concrete user situations.

Suggestions

Replace the single verb "Manage" with a few distinct concrete actions (e.g., "Create and update Products, fulfill Orders, sync Customers, launch Campaigns") to raise specificity.

Expand the "Use when" clause to list concrete trigger situations (e.g., "Use when the user wants to manage Squarespace orders, products, customers, or email campaigns").

Add common synonyms/variants users might say (e.g., "Squarespace store", "Squarespace ecommerce") to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	"Manage Websites, Forms, Products, Orders, Customers, Campaigns" lists several concrete managed objects, though they all hang off a single generic verb ("Manage") rather than multiple distinct actions, which keeps it just below the comprehensive-coverage anchor.	4 / 5
Completeness	It states a clear "what" ("Squarespace integration. Manage Websites, Forms, Products, Orders, Customers, Campaigns.") and an explicit "when" ("Use when the user wants to interact with Squarespace data."), but the trigger clause is a single generic phrase rather than several concrete trigger situations.	4 / 5
Trigger Term Quality	It surfaces the brand term "Squarespace" plus natural entity keywords (Websites, Forms, Products, Orders, Customers, Campaigns), giving good keyword coverage, but lacks synonyms or extension variants that would mark it comprehensive.	4 / 5
Distinctiveness Conflict Risk	The Squarespace brand plus its named entity set carves a clear niche with distinct, brand-specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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/squarespace/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.