Name: agent-authentication
Rating: 63.2 (1 reviews)
Author: ruvnet

Blog Docs Log in Get started

agent-authentication

Agent skill for authentication - invoke with $agent-authentication

2.23x

Quality

45%

Does it follow best practices?

Impact

96%

2.23x

Average score across 3 eval scenarios

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-authentication/SKILL.md

The canonical home for this skill is agent-authentication in ruvnet/claude-flow

Quality

Content

61%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 with concrete MCP tool examples and a clear five-step workflow, but it is padded with persona fluff and its validation step is too vague for sensitive auth operations like password resets and account changes. Tightening the intro and making validation concrete would lift the weakest dimensions.

Suggestions

Replace the persona intro ('You are a Flow Nexus Authentication Agent, specializing in...') with a one-line scope statement to remove buzzword padding.

Make the validation step concrete, e.g. 'Check the returned session token/user_id; on error, surface the MCP error message and retry with corrected credentials before proceeding.'

Add a validate->fix->retry feedback loop for password reset and account-update flows, which are sensitive and failure-prone.

Dimension	Reasoning	Score
Conciseness	The toolkit code block is efficient, but the persona intro ('You are a Flow Nexus Authentication Agent, specializing in seamless user onboarding, secure authentication flows...') and the closing 'always prioritize security, user experience...' line are padded fluff Claude does not need, matching 'Mostly efficient but includes some unnecessary explanation'; not 4 because the buzzwordy framing is more than minor.	3 / 5
Actionability	Concrete MCP tool calls with named parameters (user_register, user_login, user_reset_password, etc.) give mostly executable guidance, matching 'Mostly executable guidance; concrete code or commands with minor gaps'; not 5 because parameter values are placeholders and there is no coverage of return shapes or the common cases end-to-end.	4 / 5
Workflow Clarity	A 5-step workflow is sequenced, but step 3 'Validate Results: Confirm authentication success and handle any error states' is an implicit, vague checkpoint with no concrete validation (e.g. check returned token/session) and no validate->fix->retry feedback loop, matching 'Steps listed but validation gaps; checkpoints implicit'; not 4 because the validation step lacks any concrete check.	3 / 5
Progressive Disclosure	The single-file skill is well organized into clear sections (responsibilities, toolkit, workflow, scenarios, standards) with no external bundle files needed, matching 'Good structure; most content is appropriately placed'; not 5 because the persona/intro prose is inlined where a leaner overview would help.	4 / 5
	Total	14 / 20 Passed

Description

28%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 is a near-placeholder: it names the authentication domain and an invocation hint but provides no concrete capabilities, natural trigger phrases, or explicit use-when guidance. It is too generic to reliably route users to this skill.

Suggestions

Replace the description with concrete actions, e.g. 'Handles user login, registration, password reset, and session management via Flow Nexus MCP tools.'

Add an explicit trigger clause: 'Use when the user needs to log in, register, reset a password, or manage a Flow Nexus account.'

Drop the meta 'invoke with $agent-authentication' phrasing in favor of third-person capability and trigger language.

Dimension	Reasoning	Score
Specificity	The phrase 'Agent skill for authentication' names the domain but lists no concrete actions, matching the anchor 'Names the domain but actions are minimal or generic'; it is below 3 because no specific capabilities (login, registration, session management) are stated.	2 / 5
Completeness	It offers only a vague 'what' ('Agent skill for authentication') and no 'when'/trigger guidance, matching 'Has a vague what and no when'; the missing 'Use when...' clause also caps completeness at 3, and this sits below that cap.	2 / 5
Trigger Term Quality	'authentication' is a single generic keyword and 'invoke with $agent-authentication' is a usage hint rather than a natural user phrase, matching 'One or two generic keywords; missing the natural phrases users say'; not 3 because no common variations or synonyms are present.	2 / 5
Distinctiveness Conflict Risk	'authentication' is somewhat specific to a niche but is broad enough to overlap with other auth-related skills, matching 'Somewhat specific but could still overlap with similar skills'; not 4 because no distinct triggers narrow the niche.	3 / 5
	Total	9 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/ruflo
Path: .agents/skills/agent-authentication/SKILL.md
Commit: fa13ee4

Reviewed: about 8 hours 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.