agentleFS
SpiderIQSpiderIQ/skills/skills/Workspace/auth/SKILL.md

auth

Skill1 starsChanged 3 months agoMITView on GitHub

Authenticate with the platform and manage user sessions.

  • Reads credentials

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ci-cd, error-handling and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JohnJBorenSkill

    ci-cd

    CI/CD pipeline design, GitHub Actions, testing automation, and deployment strategies

    Also in 4 projects that use this

  • MicrosoftSkill

    error-handling

    统一错误处理系统。在添加 API 端点、修改错误处理、添加前端 API 调用、编写错误相关测试时使用。

    Also in 5 projects that use this

  • diego-tobalinaSkill

    logging

    Logging best practices for Java (SLF4J/Logback) and Node.js (Winston/Pino). Use for structured logging, log levels, and avoiding sensitive data exposure.

    Also in 3 projects that use this

  • SentrySkill

    github-issues

    Create, update, comment on, label, and inspect GitHub issues with concise, evidence-backed content. Use when users ask to open, edit, view, close, reopen, or triage GitHub issues — including tracking bugs, features, or tasks. Prefer this skill over generic repository tools for issue operations; do not use for pull requests, branches, pushes, or PR creation order questions.

    Also in 3 projects that use this

  • wrsmith108Skill

    docker

    Container-based development for isolated, reproducible environments. Use when running npm commands, installing packages, executing code, or managing project dependencies. Trigger phrases include "npm install", "run the build", "start the server", "install package", or any code execution request.

    Also in 3 projects that use this

  • SentrySkill

    ui-design

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not ask for credentials when a valid session already exists

    line 83
  2. Distinctive:

    Do not attempt to access brand data before brand selection is complete

    line 84
  3. Distinctive:

    Do not store or cache passwords in any form

    line 85
  4. Distinctive:

    Do not show raw session tokens or API keys to users

    line 86

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Authentication & Session Management

Manage user authentication, profile, brand membership, and OAuth connections.

Agent PAT enrollment — you are an account

An agent is a per-workspace account, not a throwaway token:

  • Self-identifying PAT — spideriq_pat_<agent_ref>_<secret>. The <agent_ref> (22-char handle) is your username; the secret is the password. Legacy spideriq_pat_<32-hex> tokens still authenticate.
  • OPVS address — a public, messageable handle (<name>@opvs.run), stored as opvsAddress in ~/.spideriq/credentials.json next to the token.
  • One account, three enrol modes via requestAccess (CLI spideriq auth request):
SituationModeHow
You already hold a PATROTATE — same account, fresh secretjust re-request; the held PAT wins
Fresh machine, no PAT, you know your addressRECOVERpass recover_as (CLI --as <opvs-address>)
Brand-new agentSIGNUPrequest with no held PAT / no address

Re-running from a new folder never forks a "ghost" identity. checkAccessStatus polls approval and auto-stores the token and opvsAddress. To view/rotate/revoke an account or message another agent by address, use the dashboard Team → Agents page (/dashboard/team) — see @spideriq/workspace-skills.

Context

The platform is multi-tenant:

  • Users can belong to multiple brands (organizations)
  • Each brand has its own campaigns, leads, and team
  • Users must select an active brand to work with
  • Sessions persist for 7 days, scoped by channel + user_id

Decision Guidance

Authentication Flow

  1. Check existing session -- always verify before asking for credentials. If the user has a valid session, skip login.
  2. Handle brand selection -- if the user belongs to multiple brands, present a numbered list and let them choose. If only one brand, select it automatically.
  3. Brand switching -- authenticated users can switch brands without re-entering credentials.

Signup Paths

ScenarioMethodWhat Happens
New user, no invitecompleteSignupCreates user profile + new brand + membership
New user, has invitesignupWithInviteCreates user profile + adds to inviting brand
Existing user, has inviteacceptInviteAdds user to inviting brand (no re-auth needed)

Profile Management

  • updateProfile supports partial updates (first name, last name, mobile)
  • uploadProfilePhoto accepts PNG/JPG/GIF up to 5MB, auto-resizes to 256x256
  • removeProfilePhoto cleans up the R2 file

OAuth Connectors

getConnectors shows linked social logins (GitHub, Google, etc.). Excludes email/password credential entries.

Security Rules

  • Never log, display, or store passwords
  • Never display auth tokens to users
  • Tokens are stored encrypted in Redis with 7-day expiry
  • Sessions are scoped by channel + user_id -- no cross-user access possible
  • Session data is isolated per brand

Anti-Patterns

  • Do not ask for credentials when a valid session already exists
  • Do not attempt to access brand data before brand selection is complete
  • Do not store or cache passwords in any form
  • Do not show raw session tokens or API keys to users

Error Handling

ScenarioResponse
Invalid credentials"Invalid email or password. Try again or reset your password."
Session expired"Your session has expired. Please log in again."
No brand accessShow available brands and ask user to select one
Account has no brandsDirect user to create a brand or contact their admin
Multiple failed attemptsSuggest password reset after 3 failures

Available Methods

MethodDescription
requestAccessBootstrap a PAT (approval-email flow); ROTATE a held account, RECOVER via recover_as, or SIGNUP. Returns a self-identifying PAT + OPVS address
requestAccessByEmailSimplified PAT request — email only, auto-discovers all brands the admin belongs to
checkAccessStatusPoll approval; on approval auto-stores the token + opvsAddress in credentials
getMeGet current user's profile including all brand memberships
completeSignupComplete signup by creating user profile, brand, and membership
signupWithInviteComplete signup using an invitation token
acceptInviteAccept a brand invitation as an existing user
updateProfileUpdate current user's profile (first name, last name, mobile)
uploadProfilePhotoUpload a profile picture (PNG/JPG/GIF, max 5MB)
removeProfilePhotoRemove the current user's profile picture
getConnectorsList connected OAuth providers for the current user

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.