Name: transistorfm
Rating: 52.8 (1 reviews)
Author: membranedev

transistorfm

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

Quality

58%

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/transistorfm/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 body delivers concrete, executable Membrane CLI guidance with a well-sequenced, state-checked connection workflow and good section organization. Its main weaknesses are a slightly padded intro explaining a platform Claude knows, some duplicated discovery commands, and an undefined 'Step 2' reference.

Suggestions

Trim the opening paragraph that defines what Transistor.fm is and consolidate the duplicated action-list command between 'Searching for actions' and 'Popular actions'.

Fix the step numbering: define Step 1a/1b and Step 2 explicitly so the 'skip to Step 2' and '1b' references resolve.

Add at least one concrete Transistor.fm action example (e.g. listing or fetching episodes) and a brief note on verifying a run's `output` field for success.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what Transistor.fm is ('a podcast hosting platform... used by podcasters of all sizes') which Claude already knows, and the 'Searching for actions' and 'Popular actions' sections repeat the same discovery command, fitting the score-3 anchor of mostly efficient content with some unnecessary explanation that could be tightened.	3 / 5
Actionability	It provides copy-paste-ready CLI commands for install, login, connection, action discovery, action execution, and a thorough proxy flag table, but it shows only generic discovery rather than a concrete Transistor.fm-specific example invocation (e.g. fetching episodes), matching the score-4 anchor of mostly executable guidance with minor gaps.	4 / 5
Workflow Clarity	The connect flow has a clear sequence with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-feedback loop, but the 'skip to Step 2' reference points to no labeled Step 2 and there is no validation that a run action succeeded, fitting the score-4 anchor of a clear sequence with most checkpoints and minor validation gaps.	4 / 5
Progressive Disclosure	The body is well-organized into clearly headed sections with no nested external references (the bundle directories are empty), but it is over 50 lines with some inlined/redundant content (duplicate action-list commands) and an undefined 'Step 2' / '1b' without a '1a', matching the score-4 anchor of good structure with minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

50%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 includes both a 'what' and an explicit 'Use when' trigger and is anchored to a distinct brand, but its actions and trigger terms are generic and omit the natural podcast vocabulary (podcast, episodes, analytics) users would actually say.

Suggestions

Replace generic actions with concrete podcast operations, e.g. 'Manage podcasts, episodes, and analytics on Transistor.fm.'

Add natural trigger terms users say, e.g. 'Use when the user wants to manage podcasts, publish or schedule episodes, or pull episode/analytics data from Transistor.fm.'

Include the file/extension or noun variations (podcasts, episodes, download numbers) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the Transistor.fm domain but the actions are generic ('manage data', 'automate workflows') rather than concrete podcast-specific operations like publishing episodes or fetching analytics, matching the score-2 anchor of a named domain with minimal/generic actions.	2 / 5
Completeness	It states both what ('Transistor.fm integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Transistor.fm data.'), but the 'when' clause is generic rather than tied to concrete trigger phrases, fitting the score-4 anchor of both present with an improvable 'when'.	4 / 5
Trigger Term Quality	Beyond the brand name 'Transistor.fm' and the generic phrase 'interact with ... data', the natural keywords a user would say ('podcast', 'episodes', 'analytics', 'hosting') are entirely absent, matching the score-2 anchor of one or two generic keywords missing the natural phrases.	2 / 5
Distinctiveness Conflict Risk	The trigger is anchored to a specific product name ('Transistor.fm'), giving it a clear niche with minimal conflict risk, though the generic 'manage data' actions leave minor overlap risk with related skills, matching the score-4 anchor.	4 / 5
	Total	12 / 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/transistorfm/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.