battlenet-automation

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

Quality

53%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./composio-skills/battlenet-automation/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too vague to effectively guide skill selection. It fails to specify what Battlenet tasks can be automated and lacks explicit trigger guidance. The operational instruction about searching tools first belongs in the skill body, not the description.

Suggestions

Replace 'Automate Battlenet tasks' with specific capabilities like 'Manage Battlenet friends lists, check game status, launch games, view account details'

Add a 'Use when...' clause with natural trigger terms like 'Use when the user mentions Battlenet, Blizzard games, WoW, Overwatch, or Battle.net account management'

Move the 'Always search tools first' instruction to the skill body since it's operational guidance, not a description of capabilities

Dimension	Reasoning	Score
Specificity	The description says 'Automate Battlenet tasks' which is extremely vague - it doesn't specify what tasks can be automated (account management, game launching, friend lists, etc.). 'Search tools first' is a meta-instruction, not a capability description.	1 / 3
Completeness	The 'what' is vague ('automate tasks') and there is no 'Use when...' clause or explicit trigger guidance. The instruction to 'search tools first' is operational guidance, not a description of when to use the skill.	1 / 3
Trigger Term Quality	Contains 'Battlenet' and 'Rube MCP' and 'Composio' as keywords, but lacks natural user terms like 'Blizzard', 'games', 'WoW', 'Overwatch', or specific actions users might request.	2 / 3
Distinctiveness Conflict Risk	'Battlenet' provides some distinctiveness, but 'automate tasks' is generic. Could potentially conflict with other gaming or automation skills. The Rube MCP/Composio reference helps narrow scope but isn't user-facing terminology.	2 / 3
	Total	6 / 12 Passed

Implementation

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured skill that efficiently guides Claude through Battlenet automation via Rube MCP. The workflow is clear with proper validation checkpoints, and the content respects token budget. The main weakness is that tool call examples use placeholder syntax rather than concrete, copy-paste-ready examples with realistic values.

Suggestions

Replace pseudocode-style tool calls with concrete examples showing realistic Battlenet use cases (e.g., actual game data queries, character lookups) with real parameter values

Add an example showing a complete end-to-end workflow with actual tool slugs and arguments that might be returned from RUBE_SEARCH_TOOLS

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding explanations of what Battlenet or MCP are. Every section serves a purpose with no padding or unnecessary context.	3 / 3
Actionability	Provides concrete tool call patterns with parameter examples, but uses pseudocode-style blocks rather than fully executable code. The arguments are placeholders rather than real examples with actual values.	2 / 3
Workflow Clarity	Clear 3-step workflow with explicit sequence (discover → check connection → execute). Includes validation checkpoint (verify ACTIVE status before proceeding) and known pitfalls section addresses error prevention.	3 / 3
Progressive Disclosure	Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to toolkit docs is one level deep and clearly signaled. Quick reference table aids navigation.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: ComposioHQ/awesome-claude-skills
Commit: 2790447

Reviewed: 2 months 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.