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

platformly

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

Quality

74%

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

Quality

Content

82%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, highly actionable guide built around concrete Membrane CLI commands, with a strong validation-rich connection workflow. Its weaknesses are minor: a small amount of background fluff, slightly inconsistent step numbering, and no verification guidance after destructive action/proxy calls.

Suggestions

Trim the opening 'Platform.ly is an all-in-one...' paragraph and consolidate the duplicated `action list` command so the discovery guidance appears once.

Fix the step numbering: add a labeled 'Step 1'/'Step 2' (or remove the 'skip to Step 2' / '1b' references) so the connection-to-action flow is unambiguous.

Add a brief verification/error-handling note after `action run` and destructive proxy requests (e.g. check the `output`/`error` field and retry on non-2xx) to close the validation gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with executable commands throughout and little concept explanation, though the opening 'all-in-one business management' paragraph and the duplicated action-list command in 'Popular actions' are minor over-explanation that could be trimmed; fits 'efficient; minor instances of over-explanation' rather than the fully lean 5.	4 / 5
Actionability	Provides copy-paste-ready commands for the full flow (install, login, connection ensure/get --wait, action list/run, request with a complete flags table), with appropriate placeholders, matching 'fully executable; copy-paste ready commands covering common cases'.	5 / 5
Workflow Clarity	The connection workflow has a clear sequence with explicit validation checkpoints (state checks, --wait polling, CLIENT_ACTION_REQUIRED feedback loops), matching 'clear sequence with most checkpoints present'; not a 5 because step references are slightly inconsistent ('skip to Step 2' with no labeled Step 2, a '1b' with no '1a') and destructive proxy/action operations lack an explicit post-run verification step.	4 / 5
Progressive Disclosure	Content is well-organized into clear headed sections (Overview, Authentication, Connecting, Searching, Popular actions, Proxy requests, Best practices) with no nested or buried references, fitting 'good structure; most content appropriately placed'; not a 5 because the skill exceeds the simple-skill threshold and inline detail like the full clientAction state handling and proxy flags table could be split into reference files.	4 / 5
	Total	17 / 20 Passed

Description

66%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 third-person, concise, and explicitly pairs a 'what' with a 'Use when' trigger, naming the specific Platform.ly niche clearly. Its main weakness is generic action verbs ('manage data, records') and limited trigger-term variety, which keep specificity and trigger quality at the midpoint.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Create and query records, trigger automation workflows, and retrieve campaign/email analytics from Platform.ly'.

Broaden trigger terms to natural user phrases such as 'Platform.ly contacts, campaigns, emails, or automation workflows'.

Make the 'when' clause more specific by listing concrete trigger objects (records, campaigns, emails, workspaces) rather than the generic 'interact with Platform.ly data'.

Dimension	Reasoning	Score
Specificity	Names the Platform.ly domain with a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concretely specified, matching the '1-2 concrete actions but not comprehensive' anchor; not a 4 because 'manage data/records' lacks the specificity of 'extracts text, fills forms'.	3 / 5
Completeness	Explicitly answers both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with Platform.ly data'), matching the 'has both what and when; when could be more explicit' anchor; not a 5 because the trigger ('interact with Platform.ly data') is generic rather than a concrete trigger phrase list.	4 / 5
Trigger Term Quality	Includes 'Platform.ly', 'data', 'records', and 'workflows' plus an explicit trigger phrase, but misses common synonyms or variations a user might naturally say, fitting the 'some relevant keywords but missing common variations' anchor rather than the broader coverage of a 4.	3 / 5
Distinctiveness Conflict Risk	Names the specific product Platform.ly, giving it a clear niche with distinct triggers and minimal conflict risk with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	15 / 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/platformly/SKILL.md
Commit: f484c82

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