agentleFS
Sign inStart free
ahmetenesdurahmetenesdur/starkfi/skills/authenticate-wallet/SKILL.md

authenticate-wallet

Skill2 starsChanged 8 months agoMITView on GitHub

Authenticate, manage sessions, and deploy Starknet wallets with StarkFi. Handles email OTP login (two-step), session checks, address display, account deployment, and logout. Use this skill whenever the user wants to sign in, log in, check their session, see their wallet address, deploy their account, or log out — even if they don't say "authenticate" explicitly.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. nirholas/three.ws★ 271same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository13 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    ALWAYS run npx starkfi@latest status first to check if the user already has an active session.

    line 39
  2. Very specific:

    After auth login, you MUST wait for the user to provide their OTP code.

    line 40
  3. Very specific:

    After auth verify, you MUST run npx starkfi@latest status to confirm the session is active.

    line 41
  4. Very specific:

    If any other skill reports Not authenticated, direct the user to this skill.

    line 43
  5. Very specific:

    All other skills depend on this skill — if any reports Not authenticated, use this.

    line 118
  6. Very specific:

    Use config to enable gasfree mode if the user can't afford deployment gas.

    line 119

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Authenticate Wallet

Manage authentication sessions for the StarkFi CLI. StarkFi uses a remote Auth Server with Privy TEE for email-based one-time password (OTP) authentication. A valid session is required before any transactional skill can operate.

Prerequisites

  • The StarkFi Auth Server (starkfi-server) must be running and accessible.
  • An email address the user has access to (for receiving OTP codes).

Authentication Flow

The login process is a two-step OTP flow:

  1. Initiate — auth login <email> sends an OTP code to the email.
  2. Verify — auth verify <email> <code> completes authentication.

The agent CANNOT guess or auto-fill the OTP code — it must wait for the user to provide it after checking their email.

Rules

  1. ALWAYS run npx starkfi@latest status first to check if the user already has an active session. If they do, skip the login flow — just inform them.
  2. After auth login, you MUST wait for the user to provide their OTP code. Do NOT ask more than once; just say you're waiting.
  3. After auth verify, you MUST run npx starkfi@latest status to confirm the session is active.
  4. deploy is idempotent — it's safe to run multiple times. It deploys the smart account contract on-chain if not already deployed.
  5. If any other skill reports Not authenticated, direct the user to this skill.

Commands

# Step 1: Send OTP to email
npx starkfi@latest auth login <email>

# Step 2: Verify OTP code
npx starkfi@latest auth verify <email> <code>

# Check session status
npx starkfi@latest status

# Display wallet address
npx starkfi@latest address

# Deploy smart account on-chain
npx starkfi@latest deploy

# End session
npx starkfi@latest auth logout

Parameters

ParameterTypeDescriptionRequired
emailstringUser's email addressYes
codestringOne-time password from emailYes

Examples

User: "Log me in with user@example.com"

npx starkfi@latest status
# If not authenticated:
npx starkfi@latest auth login user@example.com
# Wait for user to provide OTP code (e.g. "123456")
npx starkfi@latest auth verify user@example.com 123456
npx starkfi@latest status

User: "What's my wallet address?"

npx starkfi@latest address

User: "Deploy my account"

npx starkfi@latest deploy

User: "Log me out"

npx starkfi@latest auth logout

Error Handling

ErrorAction
Invalid OTP codeAsk the user to check their email and retry auth verify.
Session expiredRestart from auth login.
Server unreachableEnsure starkfi-server is running at the configured URL.
Rate limitWait 60 seconds before retrying.
Deployment failedCheck balance — send ETH/STRK to the address, or enable gasfree mode first.
Insufficient balanceFor deploy: npx starkfi@latest config set-gasfree on to bypass gas costs.

Related Skills

  • All other skills depend on this skill — if any reports Not authenticated, use this.
  • Use config to enable gasfree mode if the user can't afford deployment gas.

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.

Check your setup, free