CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

benzinga-automation

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

52

Quality

65%

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/benzinga-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 lean and actionable with concrete tool-call examples and a clear connection-validation step, but it lacks post-execution error-recovery feedback loops expected for batch/external-API operations. Structure is good for a self-contained single-purpose skill.

Suggestions

Add an explicit error-recovery step after RUBE_MULTI_EXECUTE_TOOL (e.g., inspect error responses, adjust arguments, and retry) to lift workflow clarity above 3.

Remove the repeated 'search first' guidance (it appears in Prerequisites, Tool Discovery, Step 1, and Pitfalls) into a single canonical statement to tighten conciseness.

Provide at least one fully concrete example with a real tool slug and schema-compliant arguments instead of placeholder session IDs to push actionability to 5.

DimensionReasoningScore

Conciseness

The body is lean — mostly tool-call blocks and bullet pitfalls with no padding or explanation of concepts Claude already knows; minor repetition of 'search first' across sections keeps it just below a 5.

4 / 5

Actionability

Concrete tool-call blocks with real parameters (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL) and a quick-reference table map operations to tools; placeholder session IDs and argument stubs are the minor gap from fully copy-paste ready.

4 / 5

Workflow Clarity

There is a clear Discover -> Check connection -> Execute sequence with an ACTIVE-status validation checkpoint and an auth-link feedback loop, but as a batch/execute operation it lacks post-execution error-recovery checkpoints (e.g., what to do when a tool call fails), capping it at 3.

3 / 5

Progressive Disclosure

No bundle files exist, so the skill is correctly self-contained; sections (Prerequisites, Setup, Tool Discovery, Core Workflow, Pitfalls, Quick Reference) are well organized with no nested references, fitting the simple-skill exception just short of a 5 only because of minor inline redundancy.

4 / 5

Total

15

/

20

Passed

Description

46%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 names the domain and primary action but lacks explicit 'when to use' trigger guidance and relies on product jargon rather than natural user phrases. It is distinctive but not comprehensive in specifying capabilities.

Suggestions

Add a 'Use when ...' clause with natural trigger phrases (e.g., 'Use when automating Benzinga news, calendars, or data tasks').

Replace generic 'Benzinga tasks' with 1-2 concrete operations (e.g., 'fetch news, pull analyst ratings, manage calendars').

Include common synonyms or Benzinga feature names users would actually say to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Benzinga tasks') and a concrete action ('Automate ... via Rube MCP') plus a concrete procedural instruction ('search tools first for current schemas'), but coverage is not comprehensive — 'Benzinga tasks' itself is generic about which operations.

3 / 5

Completeness

There is a clear 'what' (automate Benzinga tasks via Rube MCP) but no 'Use when...' or equivalent explicit trigger guidance; the second sentence is a how, not a when, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Keywords are product/technical names ('Rube MCP', 'Composio', 'Benzinga') rather than natural user phrases; common natural variations and an explicit 'Use when' trigger are missing, so it sits below the midpoint.

2 / 5

Distinctiveness Conflict Risk

It targets a distinct niche (Benzinga automation via Composio's Rube MCP) with minimal conflict risk; only minor overlap with other Composio-toolkit skills keeps it from a 5.

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

ComposioHQ/awesome-claude-skills

Path

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