auth0-automation

Automate Auth0 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/auth0-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. While it identifies the target platform (Auth0) and tooling (Rube MCP/Composio), it fails to specify concrete capabilities or provide trigger guidance. The procedural note about searching tools first is implementation detail rather than selection criteria.

Suggestions

Add specific Auth0 actions like 'manage users, configure rules, create applications, handle tenant settings' to clarify capabilities

Add a 'Use when...' clause with trigger terms like 'Auth0', 'authentication', 'identity management', 'SSO configuration', 'user provisioning'

Remove or relocate the procedural guidance ('Always search tools first') to the skill body, keeping the description focused on what and when

Dimension	Reasoning	Score
Specificity	The description says 'Automate Auth0 tasks' which is vague - it doesn't specify what tasks (user management, rule creation, tenant configuration, etc.). 'Always search tools first' is procedural guidance, not a capability description.	1 / 3
Completeness	The 'what' is extremely vague ('automate tasks'), and there is no 'Use when...' clause or equivalent trigger guidance. The description fails to answer when Claude should select this skill over others.	1 / 3
Trigger Term Quality	Includes 'Auth0' which is a specific product name users would mention, and 'Rube MCP' and 'Composio' for technical context. However, it lacks natural task-related terms users might say like 'authentication', 'users', 'login', 'SSO', 'identity'.	2 / 3
Distinctiveness Conflict Risk	'Auth0' provides some distinctiveness as a specific product, but 'automate tasks' is generic enough that it could conflict with other automation or identity-related skills. The Composio/Rube MCP reference adds some specificity to the implementation.	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 Auth0 automation via Rube MCP. It excels at workflow clarity with explicit validation steps and progressive disclosure with good organization. The main weakness is that tool call examples use placeholder syntax rather than fully executable examples, though this may be intentional given the dynamic nature of tool schemas.

Suggestions

Provide at least one complete, executable example with real Auth0 operation arguments (e.g., listing users or creating a client) to demonstrate the full workflow end-to-end

Show a concrete example of what RUBE_SEARCH_TOOLS returns and how to extract the tool_slug and arguments from that response

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding explanations of what Auth0 or MCP are. Every section provides actionable information without padding or unnecessary context.	3 / 3
Actionability	Provides concrete tool call patterns with parameter examples, but uses pseudo-code style rather than fully executable code. The argument placeholders like '/* schema-compliant args from search results */' require inference rather than being copy-paste ready.	2 / 3
Workflow Clarity	Clear 3-step workflow pattern with explicit sequencing (discover → check connection → execute). Includes validation checkpoint for connection status ('Confirm connection status shows ACTIVE before running any workflows') and error recovery guidance in pitfalls section.	3 / 3
Progressive Disclosure	Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to Composio docs is one level deep and clearly signaled. Quick reference table provides efficient navigation for common operations.	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.