CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

async-interview-automation

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

50

Quality

63%

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/async-interview-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 is a lean, actionable workflow with concrete tool calls and clear sequencing. Its main weakness is the absence of explicit post-execution validation/feedback for the batch execute operation, which caps workflow clarity.

Suggestions

Add a post-execution validation step in the Core Workflow Pattern (e.g. inspect RUBE_MULTI_EXECUTE_TOOL results, verify HTTP/status codes, and retry failed tools) to establish a feedback loop.

Consolidate the overlapping connection instructions across Prerequisites, Setup, and the Quick Reference table to reduce redundancy.

Show one concrete example of checking for and following pagination tokens in an actual tool call block rather than only listing it as a pitfall.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, though there is minor redundancy between the Prerequisites, Setup, and Quick Reference sections that could be trimmed, fitting level 4 over the fully lean level 5.

4 / 5

Actionability

Provides concrete, mostly executable tool calls (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL) with example argument shapes, with only minor gaps (placeholder session IDs / tool slugs), matching level 4 rather than fully copy-paste-ready level 5.

4 / 5

Workflow Clarity

Steps are clearly sequenced (discover -> check connection -> execute) with a connection checkpoint, but RUBE_MULTI_EXECUTE_TOOL is a batch operation with no post-execution validation/feedback loop, which per guidelines caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Well-organized into clearly headed sections (Prerequisites, Setup, Tool Discovery, Core Workflow Pattern, Known Pitfalls, Quick Reference) with no bundle files present to reference; good structure with minor organization gaps, fitting level 4 rather than the one-level-deep reference model of level 5.

4 / 5

Total

15

/

20

Passed

Description

41%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 clearly identifies the domain and integration mechanism but is generic in its action verb and lacks an explicit 'Use when...' trigger clause. It is distinctive but light on natural trigger terms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to automate Async Interview tasks or manage Async Interview data'.

Replace the generic 'Automate ... tasks' with concrete actions (e.g. 'schedule, review, and export Async Interview responses').

Include natural user-facing terms (e.g. 'async interviews', 'interview responses') alongside the technical 'Rube MCP'/'Composio' jargon.

DimensionReasoningScore

Specificity

Names the domain ("Async Interview tasks") and mechanism ("Rube MCP (Composio)") but the action "Automate ... tasks" is generic, matching the 'names the domain but actions are minimal or generic' anchor rather than the multiple concrete actions of level 3.

2 / 5

Completeness

Has a clear 'what' ("Automate Async Interview tasks via Rube MCP") but no 'Use when...' or equivalent trigger clause, which per guidelines caps completeness at 3 and matches the 'clear what, when missing' anchor.

3 / 5

Trigger Term Quality

Mostly technical jargon ("Rube MCP", "Composio", "schemas", "search tools") with only one natural product term ("Async Interview"); missing common natural phrases a user would say, fitting level 2 over level 3's broader coverage.

2 / 5

Distinctiveness Conflict Risk

Targets a specific named toolkit ("async_interview" via Rube MCP/Composio) giving a clear niche with minor overlap risk against other Composio skills, fitting level 4; not a 5 because the description lacks explicit distinct trigger phrases.

4 / 5

Total

11

/

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/async-interview-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.