From career
Enumerate companies in a domain that are genuinely remote-friendly to USER_LOCATION (not just "remote-OK" with US-only fine print). Writes to <WORKING_FOLDER>/domain-notes/remote-<domain-slug>.md. Honest negatives over hopeful positives.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin careerThis skill is limited to using the following tools:
Domain ∩ remote-friendly to `USER_LOCATION`. The bar: would *this user, in their actual timezone* clear the company's hiring filter today.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Domain ∩ remote-friendly to USER_LOCATION. The bar: would this user, in their actual timezone clear the company's hiring filter today.
$ARGUMENTS:
<domain> — the niche (free text).--location=<override> — defaults to USER_LOCATION from ${CAREER_DATA_DIR}/config.json.--n=<count> (default 20).--lens=<employer|client> — defaults employer. client mode looks for companies that buy remote services rather than employ remotely.--strict — only "global remote" / "anywhere"; exclude "remote within EMEA" unless EMEA covers the user.--refresh./career:discover remote-friendly "developer tools"
/career:discover remote-friendly "ai eval startups" --strict
/career:discover remote-friendly "policy research orgs" --lens=client
Read USER_LOCATION and WORKING_FOLDER from config. Output: ${WORKING_FOLDER}/domain-notes/remote-${domain-slug}.md.
Same enumeration approach as discover-by-domain. Cap at ~2× target so the remote filter has headroom.
For each candidate, fetch:
Classify each as:
friendly — explicit acceptance of the user's timezone/region in current postings.friendly-with-overlap — accepts globally but requires N hours overlap with US/EU. Note the overlap.region-locked — limited to a region that excludes the user.us-only — explicit US-only / US-payroll-only.unclear — no public signal.--strict keeps only friendly.
Mark contact-status as in discover-by-domain.
# Remote-friendly companies in {{domain}} (for {{location}})
> Domain: {{domain}}
> Location filter: {{location}}
> Strict: {{true|false}}
> Surveyed: {{date}}
## Companies — friendly
| name | website | evidence (live posting / page) | overlap req | contact-status | notes |
| --- | --- | --- | --- | --- | --- |
## Companies — friendly with overlap
(same columns)
## Region-locked / US-only — for the record
| name | reason |
## Honest unknowns
| name | what would resolve this |
## Sources
1. ...
note: domain-notes/remote-<domain-slug>.md
friendly: <n>
friendly-with-overlap: <n>
unclear: <n>
ruled-out: <n>
next: /career:suggest companies --from=remote-<domain-slug>
us-only, not friendly.unclear.unclear, do not classify as friendly.