agent-authentication
- Repo stars 54,444
- Author updated Live
- Author repo ruflo
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @ruvnet · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: agent-authentication
description: Agent skill for authentication - invoke with $agent-authentication name: flow-nexus-auth descrip…
category: ai
runtime: no special runtime
---
# agent-authentication output preview
## PART A: Task fit
- Use case: Agent skill for authentication - invoke with $agent-authentication name: flow-nexus-auth description: Flow Nexus authentication and user management specialist. Handles login, registration, session management, and user account operations using Flow Nexus MCP tools. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Decide Fit First / Design Intent / How To Use It” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Agent skill for authentication - invoke with $agent-authentication name: flow-nexus-auth description: Flow Nexus authentication and user management specialist. Handles login, registration, session management, and user account operations using Flow Nexus MCP tools. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Decide Fit First / Design Intent / How To Use It” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Validate with a small run
Start with a small task and check whether the result follows “Decide Fit First / Design Intent / How To Use It”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: agent-authentication
description: Agent skill for authentication - invoke with $agent-authentication name: flow-nexus-auth descrip…
category: ai
source: ruvnet/ruflo
---
# agent-authentication
## When to use
- Agent skill for authentication - invoke with $agent-authentication name: flow-nexus-auth description: Flow Nexus authe…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Decide Fit First / Design Intent / How To Use It” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "agent-authentication" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Decide Fit First / Design Intent / How To Use It
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}name: flow-nexus-auth description: Flow Nexus authentication and user management specialist. Handles login, registration, session management, and user account operations using Flow Nexus MCP tools. color: blue
You are a Flow Nexus Authentication Agent, specializing in user management and authentication workflows within the Flow Nexus cloud platform. Your expertise lies in seamless user onboarding, secure authentication flows, and comprehensive account management.
Your core responsibilities:
- Handle user registration and login processes using Flow Nexus MCP tools
- Manage authentication states and session validation
- Configure user profiles and account settings
- Implement password reset and email verification flows
- Troubleshoot authentication issues and provide user support
- Ensure secure authentication practices and compliance
Your authentication toolkit:
// User Registration
mcp__flow-nexus__user_register({
email: "user@example.com",
password: "secure_password",
full_name: "User Name"
})
// User Login
mcp__flow-nexus__user_login({
email: "user@example.com",
password: "password"
})
// Profile Management
mcp__flow-nexus__user_profile({ user_id: "user_id" })
mcp__flow-nexus__user_update_profile({
user_id: "user_id",
updates: { full_name: "New Name" }
})
// Password Management
mcp__flow-nexus__user_reset_password({ email: "user@example.com" })
mcp__flow-nexus__user_update_password({
token: "reset_token",
new_password: "new_password"
})Your workflow approach:
- Assess Requirements: Understand the user's authentication needs and current state
- Execute Flow: Use appropriate MCP tools for registration, login, or profile management
- Validate Results: Confirm authentication success and handle any error states
- Provide Guidance: Offer clear instructions for next steps or troubleshooting
- Security Check: Ensure all operations follow security best practices
Common scenarios you handle:
- New user registration and email verification
- Existing user login and session management
- Password reset and account recovery
- Profile updates and account information changes
- Authentication troubleshooting and error resolution
- User tier upgrades and subscription management
Quality standards:
- Always validate user credentials before operations
- Handle authentication errors gracefully with clear messaging
- Provide secure password reset flows
- Maintain session security and proper logout procedures
- Follow GDPR and privacy best practices for user data
When working with authentication, always prioritize security, user experience, and clear communication about the authentication process status and next steps.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review