Agent skill

Auto Login

by woocommerce in woocommerce/woocommerce-ios

Launch the WooCommerce app on a simulator already authenticated into a given store (site credentials, application password, or WPCom), skipping the manual login UI.

GPL-2.0Auto-check: notesMobile

Install Auto Login

skills CLI
$ npx skills add woocommerce/woocommerce-ios --skill auto-login -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install woocommerce/woocommerce-ios auto-login --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/woocommerce/woocommerce-ios.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/auto-login .claude/skills/auto-login && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
auto-login
GitHub stars
358
Token cost
~1.3k tokens
SKILL.md length
575 words
Files
2 (incl. scripts)
Skills in repo
13
Repo updated
First seen
Licence
GPL-2.0

At a glance

Launch the WooCommerce app on a simulator already authenticated into a given store (site credentials, application password, or WPCom), skipping the manual login UI.

  • Mobile work in your project
  • SKILL.md covers Prerequisites, Usage, Never commit secrets and Known limitations
  • Runs Shell scripts from its folder; calls bash and xcrun; reaches example-jn-site.com

What it does

Auto Login is an agent skill from woocommerce/woocommerce-ios. Launch the WooCommerce app on a simulator already authenticated into a given store (site credentials, application password, or WPCom), skipping the manual login UI. Meant to be referenced by other skills/workflows that need a logged-in session fast, but also directly runnable.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `Scripts/launch.sh`).

It sits in Mobile. It works with WooCommerce and WordPress. The licence is GPL-2.0.

When your agent uses it

  • Mobile work in your project

Example prompts

  • “/auto-login”

Requirements

  • A Bash shell
  • Pre-approved tools (allowed-tools): Bash

What it can do on your machine

Read from SKILL.md and the folder at commit 630d986. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • bash
    • xcrun

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • example-jn-site.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Auto Login loads about 1.3k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 575 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~72
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from woocommerce/woocommerce-ios at commit 630d986, republished under its GPL-2.0 licence (© woocommerce). 575 words, ~1,319 tokens.

Download SKILL.mdSave it as .claude/skills/auto-login/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
auto-login
description
Launch the WooCommerce app on a simulator already authenticated into a given store (site credentials, application password, or WPCom), skipping the manual login UI. Meant to be referenced by other skills/workflows that need a logged-in session fast, but also directly runnable.
allowed-tools
Bash
user-invocable
true
argument-hint
<UDID> <site-address> <username> <secret> [auth-type: wporg|applicationPassword|wpcom] [store-id]

Auto-Login

Launch the app already authenticated into a store, skipping the manual login UI. Backed by a DEBUG-only shortcut in ProcessConfiguration.swift that seeds SessionManager credentials + store ID at launch, before AppCoordinator decides whether to show the login screen or the tab bar.

Scope: this skill only launches. It does not build the app, install it, or provision a site — those are the caller's responsibility (see /build, /simulator, and JN site provisioning tools/skills).

Prerequisites

  • A booted simulator (use the /simulator skill approach if none is booted)
  • The app already built and installed for that simulator, from a DEBUG configuration (the default for simulator builds). If not installed yet, build first and xcrun simctl install <UDID> <path-to-.app>.
  • Credentials for the target store:
    • wporg (default) — the wp-admin username + real password (e.g. a fresh Jurassic Ninja site's admin credentials). Works with no extra setup: the app's networking layer automatically does the cookie/nonce handshake and generates+stores a proper application password on the first REST call.
    • applicationPassword — a wp-admin username + an application password created on that site (e.g. via wp user application-password create <user> <name> --porcelain over SSH). Use this if wporg doesn't work for some reason (e.g. a security plugin blocking the wp-login.php handshake).
    • wpcom — a WordPress.com username + auth token, plus the store's real numeric site ID (store-id).

Usage

bash
bash .claude/skills/auto-login/Scripts/launch.sh <UDID> <site-address> <username> <secret> [auth-type] [store-id]

Examples:

bash
# Self-hosted / JN site via its real admin username+password (auth-type defaults to wporg)
bash .claude/skills/auto-login/Scripts/launch.sh "$UDID" https://example-jn-site.com admin "real-admin-password"

# Self-hosted site via an application password instead
bash .claude/skills/auto-login/Scripts/launch.sh "$UDID" https://example-jn-site.com admin "abcd 1234 efgh 5678" applicationPassword

# WPCom-connected site (needs the real site ID)
bash .claude/skills/auto-login/Scripts/launch.sh "$UDID" https://example.com someuser somewpcomtoken wpcom 123456789

The script launches twice: a seeding launch that reads the credentials and persists them to Keychain/UserDefaults, then a second plain relaunch (no debug env vars) that boots already-authenticated from the start — this is what makes launch-time steps gated on already-being-authenticated (push notification registration, analytics identity refresh) run normally, since the seeding launch alone starts out deauthenticated and misses that window. See the comments in launch.sh for details.

After it returns, wait ~3 seconds, then verify: screenshot the simulator or use list_ui_elements (if mobile-mcp is available) and confirm the tab bar is visible (not the login screen), and that the store name matches the target site.

Never commit secrets

Credentials only ever exist as arguments to this one shell invocation and the resulting SIMCTL_CHILD_* environment variables passed to simctl launch — never write them to a file in this repo, a scheme, or any other persisted location.

Show full SKILL.md (215 more words)Show less

Known limitations

These stem from the app-side DEBUG shortcut itself and are accepted tradeoffs, not bugs in this script:

  • Don't persist these env vars on a personal Xcode scheme. If set that way instead of via this script, every subsequent debug launch — not just the one you intended — silently re-authenticates and re-syncs. Always prefer invoking launch.sh fresh (it only sets them for that one simctl launch call).
  • wpcom requires a real store-id. This script validates that, but if you ever set the env vars directly (bypassing this script), a missing/invalid store ID for wpcom credentials silently falls back to the self-hosted placeholder site ID, producing a broken/inconsistent session.
  • No error is surfaced on bad credentials. Unlike the real login UI, this shortcut doesn't validate role eligibility, WooCommerce installation, or application-password validity. Bad credentials just produce a blank/broken dashboard — check the simulator's console log (DDLogError) if the store doesn't load.
  • wporg needs the wp-login.php cookie/nonce handshake to succeed on first REST call. If a security plugin (e.g. Jetpack's account-protection module) blocks that handshake, wporg will silently fail the same way as any other bad credentials — fall back to applicationPassword in that case.
  • If you also pass logout-at-launch in the same launch, auto-login will silently re-authenticate right after it deauthenticates — the two aren't designed to be combined.

© woocommerce, GPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (scripts) in .claude/skills/auto-login of woocommerce/woocommerce-ios.

  • SKILL.md
  • Scripts/launch.sh

Open the folder on GitHubat commit 630d986

Compare with similar skills

Auto Login next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Auto Login compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Auto Login this skillwoocommerce/woocommerce-ios358—~1.3kAutomated safety check: NotesGPL-2.0
Setup Test Storeswoocommerce/woocommerce-android319—~1.4kAutomated safety check: NotesGPL-2.0
Woo AI Smokewoocommerce/woocommerce-android319—~2.5kAutomated safety check: PassGPL-2.0
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence
WooCommerce Email Editor Developmentwoocommerce/woocommerce11k—~893Automated safety check: PassCustom licence
WooCommerce Dev Cyclewoocommerce/woocommerce11k3 repos~431Automated safety check: PassCustom licence

Similar skills

  • Setup Test Stores

    woocommerce/woocommerce-android

    Provision a disposable Jurassic Ninja store for the Maestro smoke suite, connect Jetpack to the developer's own WordPress.com test account, create WooCommerce API keys, and write .maestro/.env.local.

    319 GitHub stars~1.4k tokensUpdated today
    MobileAuto-check: notes
  • Woo AI Smoke

    woocommerce/woocommerce-android

    Run the Android AI Assistant headless smoke regression harness without launching UI.

    319 GitHub stars~2.5k tokensUpdated today
    MobileAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Sets up a local environment for the WooCommerce block email editor, with a watcher, Mailpit email capture and build and test commands for its PHP and JS packages.

    11k GitHub stars~893 tokensUpdated today
    Backend & APIsAuto-check passed
  • WooCommerce Dev Cycle

    woocommerce/woocommerce

    Workflow for WooCommerce development: run PHP and JavaScript tests, lint and fix code style on the current branch, and follow guides for i18n and markdown.

    11k GitHub starsUsed in 3 repos~431 tokens
    DevelopmentAuto-check passed
  • WooCommerce Code Guard

    amElnagdy/guard-skills

    Reviews generated or changed WooCommerce code for HPOS safety, CRUD use, checkout validation and money handling before it ships.

    1.3k GitHub stars~2.2k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

More from woocommerce/woocommerce-ios

All 13 skills in this repo
  • Woo iOS Swift 6 Migration

    woocommerce/woocommerce-ios

    Diagnose and fix Swift strict-concurrency warnings in WooCommerce iOS.

    358 GitHub stars~3.2k tokensUpdated today
    Auto-check: notes
  • Setup Context A8c

    woocommerce/woocommerce-ios

    Set up the ContextA8C MCP server for accessing Automattic internal resources (Slack, Linear, P2s, GitHub Enterprise, etc.)

    358 GitHub stars~627 tokensUpdated today
    Auto-check: notes
  • Snapshot

    woocommerce/woocommerce-ios

    Use swift-snapshot-testing to visually verify SwiftUI views during implementation.

    358 GitHub stars~1.8k tokensUpdated today
    Auto-check: notes
  • Verify

    woocommerce/woocommerce-ios

    Build the app, launch on simulator, and verify feature behavior via mobile-mcp interaction.

    358 GitHub stars~1.2k tokensUpdated today
    Auto-check: notes
  • Debug

    woocommerce/woocommerce-ios

    Debug a failing test or build error in WooCommerce iOS. An agent skill from woocommerce/woocommerce-ios.

    358 GitHub stars~539 tokensUpdated today
    Auto-check: notes
  • Mocks

    woocommerce/woocommerce-ios

    Start or stop the WireMock API mock server for UI testing and E2E verification.

    358 GitHub stars~291 tokensUpdated today
    Auto-check: notes

Categories

Questions about Auto Login

What does Auto Login do?

Launch the WooCommerce app on a simulator already authenticated into a given store (site credentials, application password, or WPCom), skipping the manual login UI. Auto Login is an agent skill from woocommerce/woocommerce-ios. Launch the WooCommerce app on a simulator already authenticated into a given store (site credentials, application password, or WPCom), skipping the manual login UI.

When should I use Auto Login?

Auto Login fits situations like: mobile work in your project.

How do I install Auto Login in Claude Code?

Run `npx skills add woocommerce/woocommerce-ios --skill auto-login -a claude-code`. Or copy the skill folder (.claude/skills/auto-login in woocommerce/woocommerce-ios) into .claude/skills/auto-login in your project. Claude Code loads it when a task matches its description.

How do I install Auto Login in Codex?

Run `npx skills add woocommerce/woocommerce-ios --skill auto-login -a codex`. Or copy the skill folder (.claude/skills/auto-login in woocommerce/woocommerce-ios) into .agents/skills/auto-login in your project. Codex loads it when a task matches its description.

Can I use Auto Login in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add woocommerce/woocommerce-ios --skill auto-login -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/auto-login, .gemini/skills/auto-login, .github/skills/auto-login and .opencode/skills/auto-login in your project.

What does Auto Login need to run?

Going by SKILL.md and its folder, Auto Login needs a shell for the scripts in its folder and the command-line tools its instructions call (bash and xcrun). Our summary lists: A Bash shell. Its frontmatter pre-approves these tools: Bash.

Does Auto Login access the network?

SKILL.md names 1 domain. In commands or code: example-jn-site.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Auto Login safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Auto Login use?

Auto Login is published under the GPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Auto Login use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Auto Login?

Skills that share tags, products or a category with Auto Login: Setup Test Stores (woocommerce/woocommerce-android, 319 stars), Woo AI Smoke (woocommerce/woocommerce-android, 319 stars), WooCommerce Code Review (woocommerce/woocommerce, 11k stars) and WooCommerce Email Editor Development (woocommerce/woocommerce, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Auto Login?

woocommerce (a GitHub organization) maintains it in woocommerce/woocommerce-ios, which has 358 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 9, 2026.

Source: woocommerce/woocommerce-ios on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.