Skip to content

galiprandi/job-seeker / .agents/skills/browser-automation

browser-automation

Verified

Control a dedicated browser via agent-browser (Vercel). Use when automating web apps, scraping authenticated sites, filling forms, or navigating SPAs. Do NOT use for desktop apps or API-only integrations.

FileKindSize
SETUP.mdmarkdown3.0 KB
SKILL.mdskill md39.4 KB
references/agent-browser.mdmarkdown4.6 KB
references/api-capture.mdmarkdown1.8 KB
references/ats-patterns.mdmarkdown4.5 KB
references/audio-transcription.mdmarkdown2.4 KB
references/custom-combobox.mdmarkdown5.0 KB
references/efficiency-patterns.mdmarkdown2.6 KB
references/golden-rules.mdmarkdown5.7 KB
references/key-patterns.mdmarkdown4.4 KB
references/network-console.mdmarkdown1.2 KB
references/parallel-agents.mdmarkdown6.2 KB
references/profile-management.mdmarkdown6.3 KB
references/token-extraction.mdmarkdown2.8 KB
scripts/README.mdmarkdown6.0 KB
scripts/agent-browser.template.jsonconfig333 B
scripts/browser-share.jsscript20.0 KB
scripts/browser.jsexecutablescript17.1 KB
scripts/teams.jsscript7.1 KB
scripts/test-find-guide.jsscript6.3 KB
scripts/transcribe-audio.jsscript3.6 KB
scripts/viewer.htmlother8.6 KB
sites/CONTRIBUTING.mdmarkdown11.0 KB
sites/LEARN.mdmarkdown5.4 KB
sites/afip_gob_ar/guide.mdmarkdown9.0 KB
sites/app_web3forms_com/guide.mdmarkdown7.1 KB
sites/buk_co/guide.mdmarkdown1.5 KB
sites/calendar_google_com/calendar-deeplink.mdmarkdown1.9 KB
sites/calendly_com/guide.mdmarkdown1001 B
sites/careers_epam_com/guide.mdmarkdown4.4 KB
sites/dash_cloudflare_com/guide.mdmarkdown7.7 KB
sites/discord_com/guide.mdmarkdown9.9 KB
sites/discord_com/login-flow.mdmarkdown3.2 KB
sites/docs_google_com/guide.mdmarkdown7.3 KB
sites/facebook_com/guide.mdmarkdown9.8 KB
sites/gmail_com/guide.mdmarkdown35.6 KB
sites/google_com/guide.mdmarkdown1.1 KB
sites/google_com/login-flow.mdmarkdown3.3 KB
sites/google_home_com/guide.mdmarkdown2.1 KB
sites/google_maps_com/guide.mdmarkdown8.4 KB
sites/groq_com/signup-apikey.mdmarkdown6.6 KB
sites/humand_co/guide.mdmarkdown6.9 KB
sites/jira_com/guide.mdmarkdown10.8 KB
sites/linkedin_com/guide.mdmarkdown27.4 KB
sites/linkedin_com/outreach-strategy.mdmarkdown1.2 KB
sites/linkedin_com/posting.mdmarkdown14.0 KB
sites/linkedin_com/voyager-api.mdmarkdown8.1 KB
sites/mercadolibre_com/guide.mdmarkdown4.5 KB
sites/onstrider_com/draftjs-editor-fill.mdmarkdown2.3 KB
sites/onstrider_com/guide.mdmarkdown11.3 KB
sites/onstrider_com/react-autocomplete-inputs.mdmarkdown4.0 KB
sites/outlook_office_com/calendar-deeplink.mdmarkdown2.2 KB
sites/outlook_office_com/guide.mdmarkdown14.0 KB
sites/property_directory/guide.mdmarkdown3.7 KB
sites/reddit_com/guide.mdmarkdown16.2 KB
sites/teams_com/guide.mdmarkdown10.3 KB
sites/teamtailor_com/guide.mdmarkdown6.5 KB
sites/vea_com_ar/guide.mdmarkdown8.8 KB
sites/whatsapp_com/guide.mdmarkdown21.3 KB
sites/whatsapp_com/login-flow.mdmarkdown3.0 KB
sites/whatsapp_com/message-extraction.mdmarkdown5.7 KB
sites/whatsapp_com/voice-notes.mdmarkdown7.1 KB
sites/workatastartup_com/guide.mdmarkdown1.5 KB

sites/humand_co/guide.md

View on GitHub
---
name: humand
description: Automate job applications on Humand.co-based career sites via guest session API.
verified: 2026-09-02
domains:
  - humand.co
  - app.humand.co
---

# Humand.co Automation

Automate job applications on Humand.co-based career sites. Humand is an ATS used by some companies. Applications are submitted via their internal API with a guest session (no login required).

## Setup

```bash
# Open the company's career site
# NOTE: real URL pattern is jobs.humand.co/<company-slug>, NOT <company>.humand.co
node .agents/skills/browser-automation/scripts/browser.js open "https://jobs.humand.co/<company-slug>" --headed
```

A proprietary cookie banner may appear on first load. Accept/dismiss it before proceeding:

```bash
node .agents/skills/browser-automation/scripts/browser.js exec snapshot -i   # find the accept/reject button @eN
node .agents/skills/browser-automation/scripts/browser.js exec click @eN
```

## Apply via API (guest session)

Humand uses a guest session flow: create a guest session token, upload the CV file asset, POST the application. All calls run in-page via `exec eval` so they inherit the site's origin and cookies.

### 1. Open the job apply page

```bash
node .agents/skills/browser-automation/scripts/browser.js goto "https://jobs.humand.co/<company-slug>/jobs/<job-id>/apply"
node .agents/skills/browser-automation/scripts/browser.js exec wait --fn "!!(document.querySelector('form') || document.querySelector('input'))"
```

### 2. Create the guest session

The `communityId` is a numeric ID embedded in the page HTML (e.g. `"communityId":8554`). Extract it, then request the guest session token.

```bash
# Extract communityId from the page HTML
node .agents/skills/browser-automation/scripts/browser.js exec eval "(function(){
  const m = document.documentElement.innerHTML.match(/\"communityId\"\\s*:\\s*(\\d+)/);
  return m ? m[1] : 'not_found';
})()"

# Create the guest session
node .agents/skills/browser-automation/scripts/browser.js exec eval "(async function(){
  const r = await fetch('/api/file-assets/guest-session', {
    method: 'POST',
    headers: { 'content-type': 'application/json' },
    body: JSON.stringify({ instanceId: <communityId> })
  });
  const data = await r.json();
  return JSON.stringify(data);   // -> { guestSessionToken }
})()"
```

### 3. Upload the CV file asset

```bash
# Register the file asset -> { fileAsset, uploadUrl }
node .agents/skills/browser-automation/scripts/browser.js exec eval "(async function(){
  const r = await fetch('/api/file-assets/public', {
    method: 'POST',
    headers: { 'content-type': 'application/json' },
    body: JSON.stringify({
      guestSessionToken: '<token from step 2>',
      name: 'cv.pdf',
      type: 'FILE',
      contentType: 'application/pdf',
      public: true,
      size: <bytes>,
      sizeInBytes: <bytes>
    })
  });
  return JSON.stringify(await r.json());   // -> { fileAsset, uploadUrl }
})()"

# PUT the file bytes to uploadUrl (presigned). Do it from Node-side tooling
# (not fetch) if the file lives on disk: read the file and PUT its body to
# the returned uploadUrl with the same contentType.
```

### 4. Submit the application

```bash
node .agents/skills/browser-automation/scripts/browser.js exec eval "(async function(){
  const r = await fetch('/api/jobs/apply', {
    method: 'POST',
    headers: { 'content-type': 'application/json' },
    body: JSON.stringify({
      jobId: <job-id>,
      formVersionId: <formVersionId>,        // tenant-specific; capture from the real form
      fieldAnswers: { /* tenant-specific fields; capture from a real submission */ },
      communityId: <communityId>,
      submitterId: '<submitterId>',          // from file-assets flow / tenant config
      submissionDate: '<YYYY-MM-DD>'         // today
    })
  });
  return r.status + ' ' + r.statusText;
})()"
```

### 5. Verify

```bash
# Check for thank you page or success message
node .agents/skills/browser-automation/scripts/browser.js exec wait --text "gracias"
# or:
node .agents/skills/browser-automation/scripts/browser.js exec eval "(function(){
  const t = document.body.innerText.toLowerCase();
  if (t.includes('thank you') || t.includes('gracias')) return 'success';
  return 'no_confirmation';
})()"
```

## Required fields

Fields vary per tenant. The guaranteed shape:

| Field | Description | Source |
|---|---|---|
| `jobId` | Numeric job ID | Job URL / `GET /api/jobs?...&boardId=<n>` |
| `formVersionId` | Form version | Capture from the real apply form/request |
| `fieldAnswers` | Answers to the tenant's fields (name, email, phone, birth date, resume fileAsset, LinkedIn URL, consent...) | User profile + captured schema |
| `communityId` | Numeric tenant ID embedded in page HTML | Step 2 |
| `submitterId` | Submitter identifier | Guest session / tenant flow |
| `submissionDate` | YYYY-MM-DD, today | Generated |

**Never invent values.** If a field is missing from the data source, stop and ask the user.

## Gotchas

- **Guest session** - Humand doesn't require login. Each application uses a guest session token.
- **S3 upload first** - the CV must be uploaded (file asset + presigned `uploadUrl` PUT) before submitting the application. The apply POST references the fileAsset, not the file directly.
- **API structure varies per tenant** - capture the actual requests from a real browser application to get the exact endpoints, `formVersionId`, and `fieldAnswers` keys for each company.
- **Thank you page** - after a successful application, a thank you page appears. Verify by checking page content.
- **Jobs listing** - `GET /api/jobs?...&boardId=<n>`; job IDs are pure numerics.

## Anti-patterns

- **Don't** submit the application without first uploading the CV file asset.
- **Don't** hardcode personal data - read from the consuming repo's data source.
- **Don't** assume the API structure is the same across all Humand.co sites - capture and verify.
- **Don't** skip the consent field - it's required.

## Corrections + agent-browser notes (verified 2026-10-24)
- Real URL: `jobs.humand.co/<company-slug>` - NOT `<company>.humand.co`. Beware: `careers.humand.co` is Humand's own careers site (Teamtailor), NOT the ATS.
- Real apply flow:
  1. `POST /api/file-assets/guest-session` `{instanceId:<communityId numeric>}` -> `{guestSessionToken}` (communityId embedded in HTML, e.g. `"communityId":8554`)
  2. `POST /api/file-assets/public` `{guestSessionToken,name,type:"FILE",contentType,public,size,sizeInBytes}` -> `{fileAsset,uploadUrl}` -> `PUT uploadUrl` with the file
  3. `POST /api/jobs/apply` `{jobId,formVersionId,fieldAnswers,communityId,submitterId,submissionDate(YYYY-MM-DD today)}`
- `/api/uploads/sign` does NOT exist (404) - any older documented apply payload using it is wrong; fields vary per tenant.
- Jobs: `GET /api/jobs?...&boardId=<n>`; pure numeric IDs.
- Proprietary cookie banner on first load.
- All in-page calls via `exec eval` (fetch inherits origin + cookies). `find`/`snapshot -i` for UI interactions like the cookie banner.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall