Autoreg

Build and run automated service registrations end to end: recon a signup flow, generate an adapter, drive real Chromium/Gecko with a persistent identity, read email OTP codes, solve or inject CAPTCHA tokens, route through proxies, and verify accounts. Use this skill whenever the user asks to auto-register or mass register on a service, create accounts, automate signup/registration, bypass browser fingerprint checks, wire temporary mail or SMS, or turn a manual signup flow into a repeatable script — even if they do not say "autoreg". Also use it for QA/test-account provisioning and for debuggin

7 stars 1 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Ikhdev1/autoreg-agent-skill --skill autoreg
Manual install
git clone --depth 1 https://github.com/Ikhdev1/autoreg-agent-skill.git /tmp/autoreg-agent-skill
mkdir -p ~/.claude/skills
cp -r /tmp/autoreg-agent-skill/. ~/.claude/skills/autoreg

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# autoreg

A self-contained registration pack. The engine lives next to this file; project
state (profiles, encrypted accounts, ledgers, artifacts) lives in a per-project
`.autoreg/` directory.

```text
autoreg/
├── SKILL.md
├── scripts/autoreg.py          # CLI entry point
├── scripts/autoreg_pkg/        # engine (flow, browser, mail, captcha, recon)
├── scripts/mock_site.py        # local end-to-end target
├── assets/adapters/            # templates (mock, generic, protocol)
├── references/                 # load only the file you need:
│   ├── playbook.md             # first-try method, end to end
│   ├── preflight.md            # questions and checks before code
│   ├── adapters.md             # full YAML schema + browser_fetch
│   ├── recon.md                # report → adapter
│   ├── fingerprints.md         # engines, profiles, fpcheck
│   ├── mail.md                 # providers, aliases, code extraction
│   ├── providers.md            # mail/SMS/proxy/engine selection
│   ├── sms.md                  # SMS catalog + hook/API patterns
│   ├── captcha.md              # solvers, injection, proxy binding
│   ├── cases.md                # distilled October 2026 examples
│   ├── anti-fraud.md           # one-IP rule, pacing, error classes
│   ├── two-phase.md            # signup/confirm split
│   ├── gateway.md              # bank, keys, OpenAI-compatible shim
│   └── troubleshooting.md
└── tests/                      # unit + e2e
```

## Command prefix
Read the full skill on GitHub

Details

Skill name
autoreg
Repo updated
27 October 2026

FAQ

What does the Autoreg skill do?

Build and run automated service registrations end to end: recon a signup flow, generate an adapter, drive real Chromium/Gecko with a persistent identity, read email OTP codes, solve or inject CAPTCHA tokens, route through proxies, and verify accounts. Use this skill whenever the user asks to auto-register or mass register on a service, create accounts, automate signup/registration, bypass browser fingerprint checks, wire temporary mail or SMS, or turn a manual signup flow into a repeatable script — even if they do not say "autoreg". Also use it for QA/test-account provisioning and for debuggin

How do I install the Autoreg skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add Ikhdev1/autoreg-agent-skill --skill autoreg. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Autoreg popular?

It lives in Ikhdev1/autoreg-agent-skill, which has 7 GitHub stars and 1 forks.

Related skills

Supertest

8

renanmpimentel/supertest

Use when creating, changing, running, or auditing unit and integration tests, investigating tests that pass without observing outcomes, or analyzing application mutations and Necessist findings.

Testing & QA

Dpia Generator

9

wnallen/dpia-generator

Use whenever the user wants to run, draft, or stress-test a Data Protection Impact Assessment or any jurisdiction's equivalent for a new or modified processing. Triggers: "run a DPIA on", "assess privacy risk for", "is this Article 35 / high risk?", "need a Colorado data protection assessment / LGPD RIPD / PIPL PIPIA / Law 25 PIA?", any new-processing description (tool, vendor, AI feature, monitoring) with a privacy-risk question, or a pasted vendor page with a GDPR/ICO/CNIL/EDPB/CPPA/ANPD question. Also "index our privacy notice" — a portable notice profile later runs check for policy drift.

Testing & QA

Autogrind

7

ttttonyhe/autogrind

Engage in 24x7 auto-work mode. Continuously grind through improvements, fixes, tests, and polish without stopping until you say so. For long-running sessions across code, ML/data, research, design, or writing. Not for single bounded tasks. Trigger phrases: /autogrind, /自己动, 'autogrind this', 'grind on this', 'keep working don't stop', 'work until I say stop', 'keep improving', 'keep going'.

Testing & QA

Universal Checkout

7

zincio/skills

Discover, buy, track, and return real products from Amazon, Walmart, Target and almost any other US online retailer through the Zinc API (zinc.com). Needs no account to begin — the agent mints its own test key, then earns a live key and a $5 starter credit once its operator approves it. Pay from a pre-funded wallet, per request over MPP or x402, or with a Stripe Link card.

Testing & QAIn 1 list

Playing to Win

7

paultaki/playing-to-win

This skill should be used when the user asks to evaluate, sharpen, red-team, or pressure-test a business idea, offer, market choice, product, or strategic move using Roger Martin and A.G. Lafley's Playing to Win choice cascade. Triggers on phrases including "Playing to Win", "P2W", "where to play", "how to win", "winning aspiration", "build me a strategy", "red-team this idea", "pressure-test this", "Plan to Win", or "build a strategy framework around this project". Produces a structured 12-section output across four phases (Diagnosis, Cascade, Stress Test, Verdict), writes a persistent markdo

Testing & QA

Arduino Firmware Building

8

nguyentoanthang/arduino-firmware-building

Use this skill when the user wants to design, build, upload and test firmware for any Arduino-compatible board end to end with arduino-cli: identifies the board and FQBN via cli search, requires user-provided board/library documentation, validates requirements, writes plan and comprehensive test spec (including edge cases, boundary limits, negative inputs, and fault resilience), stops for user review & approval, implements functional code and test cases via two parallel subagents followed by a third integration & compilation subagent, uploads with user-assisted bootloader/reset steps, captures

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.