CtrlK
BlogDocsLog inGet started
Tessl Logo

anthropic-administrator-automation

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

56

Quality

64%

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/anthropic-administrator-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 well-structured, actionable, and concise with a clear workflow and validation checkpoint for connection status. Its main gaps are repeated directives, template placeholders instead of fully runnable examples, and the absence of an execution-stage error-recovery feedback loop.

Suggestions

Consolidate the 'always search tools first' guidance into one authoritative section to remove repetition across Prerequisites, Tool Discovery, and Pitfalls.

Add an execution-stage feedback loop, e.g. if RUBE_MULTI_EXECUTE_TOOL returns an error or pagination token, inspect and retry/continue before proceeding.

Provide at least one fully concrete example with a real tool slug and populated arguments so a common case is copy-paste runnable.

DimensionReasoningScore

Conciseness

The body is mostly efficient with code blocks and no concept over-explanation, but the 'search tools first' directive is repeated across Prerequisites, Tool Discovery, and Known Pitfalls, which is minor trimmable redundancy keeping it just below level 5.

4 / 5

Actionability

Concrete RUBE_SEARCH_TOOLS / RUBE_MANAGE_CONNECTIONS / RUBE_MULTI_EXECUTE_TOOL call templates are provided with real field names, but placeholders like 'your_session_id' and 'TOOL_SLUG_FROM_SEARCH' keep them from being fully copy-paste ready, fitting level 4.

4 / 5

Workflow Clarity

The Core Workflow Pattern gives a clear Discover -> Check Connection -> Execute sequence with an explicit validation checkpoint (confirm ACTIVE status before executing) and a setup feedback loop (follow auth link if not ACTIVE), but lacks an execution-stage error-recovery loop, so it sits at level 4 rather than 5.

4 / 5

Progressive Disclosure

Content is well-organized into clearly labeled sections (Prerequisites, Setup, Tool Discovery, Core Workflow, Pitfalls, Quick Reference) with no nested or buried references, but at ~85 lines with all content inline it exceeds the under-50-line simple-skill exception, so level 4 rather than 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 clearly identifies a distinct niche and a concrete behavioral directive, but it lacks an explicit 'Use when...' trigger clause and relies on generic capability verbs plus technical jargon. It is solid but not exemplary on completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when automating Anthropic Admin operations like managing users, workspaces, billing, or API keys.'

Replace generic 'Automate... tasks' with 2-3 concrete operations users would name (e.g. manage users, view billing, rotate API keys).

Move 'Rube MCP (Composio)' out of the lead phrasing or relegate it so natural user terms dominate the trigger surface.

DimensionReasoningScore

Specificity

Names the domain ('Anthropic Admin tasks') and a concrete behavioral directive ('Always search tools first for current schemas'), but the capability verb 'Automate... tasks' is generic and coverage is not comprehensive, matching the level-3 anchor rather than the more action-rich level 4.

3 / 5

Completeness

The 'what' is clear ('Automate Anthropic Admin tasks via Rube MCP'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric cap completeness stays at 3.

3 / 5

Trigger Term Quality

'Anthropic Admin tasks' is a relevant natural phrase, but 'Rube MCP (Composio)' is technical jargon and common user variations/synonyms for the admin domain are missing, fitting the level-3 anchor.

3 / 5

Distinctiveness Conflict Risk

The 'Anthropic Admin' toolkit niche is fairly distinct with specific tool slugs, carrying only minor overlap risk with other Anthropic-related automation skills, matching the level-4 anchor.

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.

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