CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

auth0-automation

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

56

Quality

70%

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

Quality

Content

75%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 body is lean, actionable, and clearly sequenced with connection-status validation before execution, scoring well across all dimensions. The main gaps are placeholder arguments in the execute step and the lack of an explicit validate-fix-retry loop for batch/destructive Auth0 operations.

DimensionReasoningScore

Conciseness

The body is well-organized and largely free of concept explanations Claude already knows, though the Quick Reference table partly duplicates the Core Workflow steps and the Setup section repeats prerequisites already stated, which could be trimmed.

4 / 5

Actionability

It provides concrete, copy-ready tool invocation blocks (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL) with named fields, but arguments are placeholders (e.g. TOOL_SLUG_FROM_SEARCH, /* schema-compliant args */) rather than fully executable against a concrete task, leaving minor gaps.

4 / 5

Workflow Clarity

The Core Workflow Pattern sequences discovery -> connection check -> execution with explicit 'Confirm connection status shows ACTIVE before running any workflows' and Known Pitfalls checkpoints, but execution against destructive/batch Auth0 operations lacks an explicit validate-fix-retry feedback loop, so it does not reach 5.

4 / 5

Progressive Disclosure

No bundle files exist in references/, scripts/, or assets/, yet the skill stays compact and well-sectioned with the quick-reference table serving as navigation; it earns the simple-skill bump toward 4, but the absence of any reference split (e.g. a dedicated pitfalls or schema guide) keeps it from 5.

4 / 5

Total

16

/

20

Passed

Description

53%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 names its niche clearly and would be distinguishable, but it is missing an explicit 'Use when...' trigger clause and lists no concrete Auth0 operations, which caps completeness and trigger-term coverage at 3. It is third person and free of fluff.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g. 'Use when the user asks to manage Auth0 users, roles, connections, or tenant settings').

Replace the generic 'Automate Auth0 tasks' with 2-3 concrete operations (e.g. 'manage users, roles, and connections') to lift specificity.

Include natural synonyms/extensions users say (e.g. 'identity', 'login', 'API keys') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

It names the domain (Auth0 tasks via Rube MCP/Composio) and one concrete action-adjacent directive ('search tools first'), but the named capability 'Automate Auth0 tasks' is generic and does not list specific concrete operations like user management, role assignment, or connection setup.

3 / 5

Completeness

It gives a clear 'what' (automate Auth0 tasks via Rube MCP) plus an operating instruction (search tools first), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

It surfaces 'Auth0', 'Rube MCP', and 'Composio' which a user needing this integration would name, but it omits common natural variations and synonyms a user might say (e.g. 'Auth0 management', 'identity', 'login', 'users', 'roles').

3 / 5

Distinctiveness Conflict Risk

The Auth0 + Rube MCP + Composio combination carves a clear niche with distinct triggers and low overlap risk with other skills, though the generic 'Automate Auth0 tasks' phrasing leaves minor ambiguity.

4 / 5

Total

13

/

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/auth0-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.