claudegoodies
Skill

career-ops-plugin-apify

From santifer

How to scan a job source through an Apify actor as a keyed provider.

Runs an Apify actor for one portals.yml entry and maps its dataset fields into the job scanner pipeline.

Use it when

  • A job source has no built-in scanner but has an Apify actor scraping it
  • You want to track an Indeed/company search via Apify's dataset output
  • You need custom field mapping (title/url/company/location) from raw actor output
  • You want scraped job descriptions cached locally under jds/

Skip it if

  • Requires an Apify account and APIFY_TOKEN in .env
  • Only activates via explicit provider: apify entry, no auto-detection
  • Depends on the specific Apify actor's output schema matching your field_map

Facts

Repository
santifer/career-ops
Status
Actively maintained
Last commit
Source file
plugins/apify/skill.md

Source preview

The instructions Claude Code reads when this skill runs.

# apify plugin

A keyed provider: runs an Apify actor and maps its dataset items into the
scanner. It fires ONLY on a `portals.yml` entry that sets `provider: apify` —
never via auto-detection. Put `APIFY_TOKEN` in `.env`.

## portals.yml entry

```yaml
tracked_companies:
  - name: "Indeed — VP Engineering (Chicago)"
    provider: apify
    actor: misceres/indeed-scraper
    input: { position: "VP of Engineering", location: "Chicago, IL", maxItems: 25 }
    field_map:
      title:    [positionName, title]    # array = first non-empty wins
      url:      url
      company:  [company, companyName]
      location: [location, formattedLocation]
```

## Then

`node scan.mjs` runs the provider for that entry and writes the results to the
pipeline like any other source. An optional `field_map.description` caches the
JD locally under `jds/`.
View full source on GitHub →

Other skills