CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

castmagic

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

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/castmagic/SKILL.md
SKILL.md
Quality
Evals
Security

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 CLI guidance with a sensible connection-to-action workflow and good state-based error handling. Main weaknesses are mild marketing padding, a dangling "Step 2" reference, and the absence of a worked end-to-end action example.

Suggestions

Remove the marketing sentence "This helps users save time and effort in content creation and distribution" and the empty "Castmagic Overview" bullet list, or replace the latter with the two or three concrete entities agents will actually address (projects, files, workspaces) with their meaning.

Fix the dangling "skip to **Step 2**" references by labeling the subsequent sections as numbered steps (e.g. "Step 2: Search for actions", "Step 3: Run actions") or rephrasing to "continue to Searching for actions".

Add one worked example that runs a real action end-to-end, e.g. `membrane action run get-transcript --connectionId=... --input '{"id": "..."}' --json`, so agents see a complete input/output round trip.

DimensionReasoningScore

Conciseness

The body is mostly command-driven, but contains padded spots: "This helps users save time and effort in content creation and distribution" (marketing fluff), a near-empty "Castmagic Overview" bullet section, and commentary like "This is the fastest way to get a connection". This matches anchor 3 (mostly efficient but includes some unnecessary explanation) rather than 4 because there are several such spots.

3 / 5

Actionability

Concrete copy-paste commands throughout ("npm install -g @membranehq/cli@latest", "membrane connection ensure \"https://www.castmagic.io/\" --json", "membrane action run <actionId> --input '{...}' --json") plus a proxy flags table. This matches anchor 4 (mostly executable with minor gaps) rather than 5 because there is no end-to-end example running a real action (e.g. get-transcript) with actual input values.

4 / 5

Workflow Clarity

A clear install → authenticate → connect → poll-state → search/run → proxy-fallback sequence exists with feedback via state polling and clientAction handling. However, "skip to **Step 2**" references a step label that does not exist anywhere in the document. This matches anchor 4 (clear sequence, minor validation gaps) rather than 5 due to the dangling step reference and absence of output validation beyond connection state.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the single-file structure is well organized with clear sections and tables; nothing that belongs in a separate file is inlined. This matches anchor 4 (good structure, minor organization gaps) rather than 5 because the empty "Castmagic Overview" section and inconsistent step numbering slightly hurt navigation.

4 / 5

Total

15

/

20

Passed

Description

48%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 names a distinct product niche and includes an explicit "Use when" trigger, but the capability statement is generic. Users searching for concrete Castmagic tasks (transcripts, show notes, summaries) would not reliably match it.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete capabilities, e.g. "Fetch and create transcripts, generate show notes and summaries, and manage Castmagic files and workspaces".

Expand the "Use when" clause with natural trigger phrases users would actually say: "Use when the user mentions Castmagic, podcasts, transcripts, show notes, or repurposing audio/video content".

Drop the filler words "Manage data, records" which overlap with generic data skills and add no distinctiveness.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Castmagic domain but the actions are entirely generic; no concrete capabilities (transcripts, show notes, summaries) are stated. It matches anchor 2 (domain named, actions minimal/generic) rather than 3 because not even one concrete action is listed.

2 / 5

Completeness

The "when" is explicit ("Use when the user wants to interact with Castmagic data") but the "what" ("Manage data, records, and automate workflows") is vague. It falls between anchor 2 (vague what, no when) and anchor 4 (both present and solid), so the weak "what" pulls it to 3.

3 / 5

Trigger Term Quality

"Castmagic" is a natural term users would say, but the remaining keywords ("data", "records", "workflows") are generic and natural variations like "transcripts", "show notes", or "podcast" are missing. This is anchor 3 (some relevant keywords, missing common variations) rather than 4 due to thin keyword coverage beyond the product name.

3 / 5

Distinctiveness Conflict Risk

"Castmagic integration" carves a clear niche with minimal conflict risk, but the generic capability phrasing ("Manage data, records, and automate workflows") overlaps with many data-oriented skills. This matches anchor 4 (mostly distinct, minor overlap risk) rather than 5 because of that generic phrasing.

4 / 5

Total

12

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.