agentleFS
TheQmaksTheQmaks/areclaw/.claude/skills/register/SKILL.md

register

Skill67 starsChanged 9 months agoMITView on GitHub

Automated account registration in an Android app using temp email and UI automation

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. dynos-fit/dynos-work★ 2same 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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Read the snapshot. Determine:

    line 23
  2. Distinctive:

    If not on registration screen:

    line 29
  3. Distinctive:

    If fields don't have good resource-ids, use text or XPath:

    line 87
  4. Distinctive:

    Check if the app shows a success state or redirects to main screen.

    line 133

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

/register — Automated Account Registration

You are automating the registration process for an Android app. This requires UI interaction, email verification, and intelligence about form types.

Input

  • $ARGUMENTS — package name (must be installed and running on device)

Phase 1: UI Reconnaissance

1a. Get current state

python pytools/ui_explorer.py snapshot --output-dir workspace/output

Read the snapshot. Determine:

  • Is the app on a login screen, registration screen, or splash screen?
  • What kind of registration? Email, phone, social login, or combination?
  • What fields are visible?

1b. Navigate to registration

If not on registration screen:

# Look for "Sign Up", "Register", "Create Account" buttons
python pytools/ui_explorer.py tap --text "Sign Up"
# or
python pytools/ui_explorer.py tap --text "Register"
# or
python pytools/ui_explorer.py tap --text "Create Account"
# or try XPath
python pytools/ui_explorer.py tap --xpath '//node[contains(@text,"Sign") or contains(@text,"Register") or contains(@text,"Create")]'

Take another snapshot to verify navigation succeeded.

1c. Map the form

python pytools/ui_explorer.py dump

Identify all input fields by resource-id, text, or content-desc. Common patterns:

  • Email field: resource-id contains email, mail, username
  • Password field: class="android.widget.EditText" with password="true"
  • Name fields: name, first_name, last_name, full_name
  • Phone: phone, mobile, tel

Phase 2: Identity Creation

2a. Email strategy

Try temp mail first:

tema create

Save the email address.

If app blocks temp mail domains, use Gmail alias:

tema gmail-alias your.real@gmail.com

Note: Gmail aliases forward to your real inbox. You'll need to check manually or set up a filter.

2b. Generate credentials

  • Email: from tema
  • Password: Generate strong password (16+ chars, mixed case, digits, symbols)
  • Name: Generate plausible name
  • Username: Derive from email prefix

Phase 3: Form Filling

Fill each field:

# Tap field → input text
python pytools/ui_explorer.py input --id "email_field" "generated@email.com"
python pytools/ui_explorer.py input --id "password_field" "GeneratedP@ss123!"
python pytools/ui_explorer.py input --id "name_field" "Test User"

If fields don't have good resource-ids, use text or XPath:

python pytools/ui_explorer.py input --text "Email" "generated@email.com"
python pytools/ui_explorer.py tap --xpath '//node[@class="android.widget.EditText"][1]'

Handle special cases:

  • Checkbox (terms): tap --id "terms_checkbox" or tap --text "I agree"
  • Date picker: May need multiple taps
  • Dropdown/Spinner: Tap to open, then tap option
  • CAPTCHA: Report to user — cannot automate

Submit

python pytools/ui_explorer.py tap --text "Sign Up"
# or
python pytools/ui_explorer.py tap --text "Register"
# or
python pytools/ui_explorer.py tap --text "Create"

Phase 4: Email Verification

4a. Wait for verification email

tema wait --timeout 120

4b. Extract verification link

tema verify

4c. Open verification link

# If it's a deep link / app link
adb shell am start -a android.intent.action.VIEW -d "VERIFICATION_URL"

# If it's a web link that should open in browser
adb shell am start -a android.intent.action.VIEW -d "VERIFICATION_URL" -p com.android.chrome

4d. Verify success

python pytools/ui_explorer.py snapshot --output-dir workspace/output

Check if the app shows a success state or redirects to main screen.

Phase 5: Save Credentials

mkdir -p workspace/credentials

Save to workspace/credentials/$PKG.json:

{
    "package": "<package_name>",
    "email": "<email>",
    "password": "<password>",
    "username": "<username_if_applicable>",
    "created_at": "<timestamp>",
    "method": "tema|gmail_alias",
    "verified": true|false,
    "notes": "<any relevant notes>"
}

Error Handling

  • CAPTCHA detected: Report to user, provide screenshot, ask for manual intervention
  • Phone verification required: Report to user — cannot automate phone OTP
  • Social login only: Report to user — no email registration available
  • Temp mail blocked: Fall back to Gmail alias
  • Registration fails: Take screenshot, read error message, report to user
  • Email never arrives: Try gmail alias, report timeout

Report to User

  • Registration success/failure
  • Credentials saved location
  • Any issues encountered
  • Screenshot of final state

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.