Name: simplecast
Rating: 55.2 (1 reviews)
Author: membranedev

simplecast

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

Quality

62%

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/simplecast/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 delivers a clear, actionable Membrane-CLI workflow for Simplecast with strong command coverage and a well-handled connection state machine, but it carries some unnecessary explanatory filler and lacks a fully worked end-to-end example.

Suggestions

Trim the product-intro paragraph and remove filler such as "Use action names and parameters as needed." to tighten token efficiency.

Add one worked end-to-end example with realistic values (e.g. a concrete action list intent and a sample `action run` with a real input JSON) so the running-actions section is copy-paste ready.

Clarify the step numbering (the body references "Step 2" without a matching header) and add a brief output-validation note for destructive proxy methods (DELETE/PUT).

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, command-focused content, but it includes unnecessary explanation such as the product-intro paragraph ("Podcasters and media companies use it to manage and grow their audience"), the filler line "Use action names and parameters as needed.", and marketing-tinged phrasing ("so you can focus on the integration logic rather than auth plumbing"), matching the score-3 anchor (mostly efficient with some unnecessary explanation).	3 / 5
Actionability	Concrete, executable commands are provided throughout (install, login, connection ensure/get, action list/run, request) plus a comprehensive proxy flag table, but placeholders like <actionId> and --intent "QUERY" lack a worked end-to-end example with real values, fitting score 4 (mostly executable with minor gaps) rather than the copy-paste-ready score 5.	4 / 5
Workflow Clarity	The connect-to-poll-to-handle-state sequence is clear with explicit state checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a feedback loop (re-poll after the user acts), but the referenced "Step 2" is not clearly demarcated and action-run output has no validation step, placing it at score 4 rather than the score-5 anchor requiring fully explicit validation.	4 / 5
Progressive Disclosure	The single-file body is well-organized into clear sections (Overview, Working with Simplecast, Install, Authentication, Connecting, Searching, Popular actions, Best practices) with no nested references, but at ~145 lines with minor redundancy between "Searching for actions" and "Popular actions" it has minor organization gaps, fitting score 4 rather than the cleanly-split score 5.	4 / 5
	Total	15 / 20 Passed

Description

57%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 correctly names the Simplecast niche and includes an explicit "Use when" trigger, satisfying basic completeness, but its action language is generic and it omits the natural podcast-domain terms a user would actually say.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete Simplecast actions, e.g. "Publish and distribute podcast episodes, view listener analytics, and manage subscriptions and ad campaigns."

Add natural trigger terms users would say, e.g. "Use when the user wants to manage a podcast, publish episodes, check Simplecast analytics, or work with their Simplecast feed."

Keep the third-person voice (already correct) but make the "what" specific enough that it is distinguishable from generic data-integration skills.

Dimension	Reasoning	Score
Specificity	Names the domain ("Simplecast integration") but the actions "Manage data, records, and automate workflows" are generic abstractions rather than concrete Simplecast actions like publishing episodes or viewing analytics, fitting the score-2 anchor (minimal/generic actions) below the score-3 anchor which requires 1-2 concrete actions.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Simplecast data") are present, but the "what" is vague and the trigger could be more specific, fitting the score-4 anchor rather than the score-5 anchor which requires concrete trigger phrases.	4 / 5
Trigger Term Quality	The brand keyword "Simplecast" is present and is the strongest natural trigger, but the supporting terms ("data", "records", "workflows") are generic and common podcast-domain variations (podcast, episodes, analytics, hosting) are missing, matching the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	The "Simplecast" brand name creates a clear niche with low conflict risk, but the generic action framing ("manage data, records") leaves minor overlap risk with other data-integration skills, so it sits at score 4 rather than the fully-distinct score 5.	4 / 5
	Total	13 / 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/simplecast/SKILL.md
Commit: f484c82

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