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

Blog Docs Log in Get started

plasmic

Plasmic integration. Manage Projects. Use when the user wants to interact with Plasmic 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/plasmic/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 content is a strong, actionable CLI integration guide with explicit state-validation checkpoints and a feedback loop for connection readiness. Its main weakness is conciseness, due to an inlined concept taxonomy and a padded overview paragraph.

Suggestions

Cut the "Plasmic Overview" concept taxonomy and the "Plasmic is a visual website builder…" paragraph, or move them to a reference file, to reduce token overhead.

Replace the dangling "Step 2" references with a short numbered sequence (1. Install, 2. Authenticate, 3. Connect, 4. Discover & run actions) so the workflow is unambiguous.

Add one fully-resolved worked example (with a concrete connectionId and a sample action run) so the placeholders can be filled in directly.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but the "Plasmic Overview" concept taxonomy and the opening "Plasmic is a visual website builder…" paragraph are unnecessary explanation that could be tightened.	3 / 5
Actionability	It provides concrete, executable CLI commands across install, login (including headless), connection setup, action search/run, and proxy requests with a full flag table, with only minor gaps from placeholder values (CONNECTION_ID, QUERY, actionId).	4 / 5
Workflow Clarity	There is a clear install→authenticate→connect→search→run sequence with state-validation checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, but "Step 2" is referenced without a clearly numbered Step 1, leaving a minor clarity gap.	4 / 5
Progressive Disclosure	The single-file body is well organized with clear section headers and no unnecessary external references, but at ~158 lines it exceeds the simple-skill threshold and the concept taxonomy is content that could be split out, so it stops short of 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 correctly structured with both a capability statement and an explicit use-when trigger, and the brand name gives it strong distinctiveness. It is held back by thin specificity (one action) and limited natural trigger-term variation.

Suggestions

List 2-3 concrete actions beyond "Manage Projects" (e.g., list/create/update Projects, manage Components and Pages, fetch content via the Loader) to lift specificity.

Broaden trigger terms with natural user phrasing such as "Plasmic projects," "Plasmic components," or "Plasmic CMS content" instead of the generic "interact with Plasmic data."

Tighten the "when" clause to name concrete scenarios (e.g., "Use when the user wants to manage Plasmic projects, pages, or components") for a more explicit trigger.

Dimension	Reasoning	Score
Specificity	"Plasmic integration. Manage Projects." names the domain plus a single concrete action, but offers no further specific capabilities, matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It states a "what" ("Plasmic integration. Manage Projects.") and an explicit "when" ("Use when the user wants to interact with Plasmic data."), but the trigger is somewhat generic rather than concrete, fitting the 4 anchor.	4 / 5
Trigger Term Quality	The term "Plasmic" recurs and "interact with Plasmic data" gives a trigger, but there are few natural synonyms or task-oriented phrases a user would actually say, so common variations are missing.	3 / 5
Distinctiveness Conflict Risk	The proper-noun brand "Plasmic" gives a clear niche with distinct triggers and minimal conflict, though the broad "interact with Plasmic data" phrasing leaves minor overlap with general web/CMS 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/plasmic/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.