| name | auto-create-connector |
| description | Autonomously create, test, and validate a data connector for any web platform — end to end. Use when asked to "auto-create a connector", "automatically build a connector", or when a connector needs to be created from scratch and tested without manual guidance. Triggers on: "auto-create", "auto connector", "create and test connector", "build connector end to end", "generate connector".
|
Autonomous Data Connector Creator
Fully autonomous, zero human-in-the-loop connector creation. The agent writes a Playwright
connector script, tests it against the live site using credentials from .env, validates
the output, iterates until quality, and caches the result for deterministic reuse.
Input
- Platform name (required): e.g., "Twitter", "Reddit", "Notion"
- Data description (optional): what data to extract. If not specified, extract all
commonly useful personal data (profile, content, settings).
Credentials Convention
Credentials are stored in .env at the repo root:
USER_LOGIN_TWITTER=user@example.com
USER_PASSWORD_TWITTER=secretpassword
Pattern: USER_LOGIN_<PLATFORM_UPPER> and USER_PASSWORD_<PLATFORM_UPPER>.
The platform name is uppercased (e.g., LINKEDIN, REDDIT, TWITTER).
The connector script reads these via process.env and performs automated login —
filling the form fields programmatically and submitting. No manual browser interaction.
Workflow
Execute steps IN ORDER. Do not skip validation. Do not skip testing.
Step 1 — Research the Platform
Goal: Understand the platform's data landscape, login flow, and extraction strategy.
Actions (do all of these):
