anonyflow-automation

Automate Anonyflow 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/anonyflow-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 and lacks the essential components for effective skill selection. It names specific tools/products but fails to explain what concrete actions are possible or when Claude should select this skill. The operational instruction about searching tools doesn't help with skill selection.

Suggestions

Add specific concrete actions that can be performed (e.g., 'Create workflows, manage approvals, trigger automations, query workflow status').

Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user mentions Anonyflow, workflow automation, or Composio integrations').

Replace the procedural instruction ('Always search tools first') with capability descriptions that help Claude understand what this skill enables.

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'Automate Anonyflow tasks' without specifying what concrete actions can be performed. 'Always search tools first' is procedural guidance, not a capability description.	1 / 3
Completeness	The 'what' is extremely vague ('Automate Anonyflow tasks') and there is no 'when' clause or explicit trigger guidance. The instruction about searching tools is operational, not descriptive of when to use the skill.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('Anonyflow', 'Rube MCP', 'Composio') but these are technical/product names rather than natural terms users would say. Missing common variations or task-oriented language.	2 / 3
Distinctiveness Conflict Risk	The specific product names (Anonyflow, Rube MCP, Composio) provide some distinctiveness, but 'automate tasks' is generic enough to potentially overlap with other automation skills.	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 teaches Anonyflow automation via Rube MCP. It excels at workflow clarity with explicit validation steps and provides good progressive disclosure. The main weakness is that tool call examples use a pseudo-code style rather than showing the actual MCP tool invocation format, which slightly reduces actionability.

Suggestions

Show tool calls in actual MCP invocation format (e.g., JSON-RPC or the specific client syntax) rather than pseudo-code blocks to make examples fully executable

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding explanations of concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context about what Anonyflow or MCP is.	3 / 3
Actionability	Provides concrete tool call patterns with specific parameters, but uses pseudo-code style rather than fully executable examples. The tool calls show structure but aren't copy-paste ready in any specific format.	2 / 3
Workflow Clarity	Clear 3-step workflow with explicit validation checkpoint (Step 2: Check Connection shows ACTIVE status before proceeding). The Known Pitfalls section reinforces validation requirements and error prevention.	3 / 3
Progressive Disclosure	Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. Quick reference table provides at-a-glance navigation. External toolkit docs linked appropriately without deep nesting.	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: 29 days 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.