CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

castingwords-automation

Automate Castingwords tasks via Rube MCP (Composio). Always search tools first for current schemas.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/castingwords-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 compact, well-structured operational guide with concrete tool-call patterns and a sensible discover-then-execute workflow. Its main gaps are repeated instructions, no error-recovery guidance for failed executions, and placeholder-only examples.

Suggestions

Add an error-recovery step for RUBE_MULTI_EXECUTE_TOOL failures (e.g., re-run RUBE_SEARCH_TOOLS, re-check connection, retry with corrected arguments).

Consolidate the "always search tools first" instruction into a single location instead of repeating it in Prerequisites, Tool Discovery, and Known Pitfalls.

Include one fully worked example with realistic values for a common Castingwords operation to make the execution pattern concrete.

DimensionReasoningScore

Conciseness

The body is lean and imperative with concrete tool-call blocks, but "always search tools first" is repeated across Prerequisites, Tool Discovery, and Known Pitfalls — minor repetition that could be consolidated. Not a 5 because of that duplicated instruction and the decorative "Powered by Composio" footer.

4 / 5

Actionability

Concrete tool invocation blocks with parameter structures are provided for each step; the placeholder slugs (e.g., "TOOL_SLUG_FROM_SEARCH") are justified by the changing schemas but keep the blocks from being copy-paste executable. Not a 5 because no fully worked example with real values is shown.

4 / 5

Workflow Clarity

The setup and execution sequences are clearly ordered with a status checkpoint ("Confirm connection status shows ACTIVE") and an auth-retry loop ("If connection is not ACTIVE, follow the returned auth link"). Not a 5 because there is no guidance for handling tool-execution failures from RUBE_MULTI_EXECUTE_TOOL.

4 / 5

Progressive Disclosure

No bundle files exist and the content is well-sectioned, self-contained, and easy to navigate; the body (~84 lines) exceeds the under-50-line simple-skill exception, so it scores 4 rather than 5. Not a 3 because all sections are appropriately organized with nothing that clearly belongs in a separate file.

4 / 5

Total

16

/

20

Passed

Description

52%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 short, third-person, and names a distinct niche, but it lacks a "when to use" trigger clause and concrete capability verbs. Its reliance on technical jargon (Rube MCP, Composio) limits natural trigger-term coverage.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks to automate Castingwords transcription tasks or mentions Castingwords, transcription jobs, or audio timestamps."

Replace the generic "Automate Castingwords tasks" with 2-3 concrete operations (e.g., submit audio for transcription, check job status, fetch completed transcripts).

Include natural user vocabulary such as "transcription", "captions", and "audio files" alongside the service name.

DimensionReasoningScore

Specificity

"Automate Castingwords tasks" names the domain but the action is generic — no concrete operations (e.g., transcribe audio, manage jobs, fetch transcripts) are listed. It is not a 3 because no specific concrete action is named beyond "automate tasks".

2 / 5

Completeness

The "what" is present (automate Castingwords via Rube MCP) but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric. Not a 2 because the "what" is clearly stated, not vague.

3 / 5

Trigger Term Quality

"Castingwords" is a natural term a user would say, but "Rube MCP", "Composio", and "search tools" are technical jargon, and common variations like "transcription", "captions", or "audio files" are missing. Not a 4 because keyword coverage is limited to the service name itself.

3 / 5

Distinctiveness Conflict Risk

"Castingwords" plus "Rube MCP (Composio)" carves out a clear niche with distinct triggers and minimal conflict risk with other skills. Clearly matches the anchor for a clear niche with distinct triggers.

5 / 5

Total

13

/

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

ComposioHQ/awesome-claude-skills

Path

composio-skills/castingwords-automation/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.