メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Sweep all (or a filtered subset of) email addresses in the workspace CRM and re-verify them via Hunter Email-Verifier. Use periodically — people change jobs, addresses go stale, accept-all status changes. Updates the `verified` and `last-verified` columns in `crm/contacts.md` and prints a summary of what flipped.
Scan the user's existing Claude Code plugins and MCP servers to detect capabilities the career plugin needs (email send, transcription, calendar/tasks, semantic store, CRM). For each capability, decide whether to reuse an already-installed plugin/MCP, install a recommended companion plugin, or add an MCP server. Writes the resolution map to ${CAREER_DATA_DIR}/config.json under a `capabilities` block. Invoked from /career:onboard before install-companion-plugins so we don't double up on capabilities the user already has.
Enrich an existing CRM contact with Hunter Combined-Enrichment — pulls role, seniority, department, social handles, and the contact's company facts in one call. Use to flesh out a thinly-populated CRM row before drafting outreach or prepping for a meeting. Operates on an email address from the CRM; updates the row in place.
Given a person's name and their company (name or domain), return Hunter's best guess at their email address with a confidence score. Use when the user already knows who they want to reach and just needs the address. Differs from find-contact (which lists candidates at a company) — this is targeted at a single named person.
Validate a single email address via Hunter Email-Verifier. Use when the user has an address (handed to them, scraped, guessed) and wants a deliverability + confidence read before sending outreach. Returns Hunter's verdict (deliverable / risky / undeliverable / unknown), score, and the disposable / role / accept-all flags. Does not write to the CRM unless asked.
For CONTEXT_STORE=pinecone — verify the index against the local workspace. Flags vectors whose source file was deleted, renamed, or content-changed (hash mismatch), and surfaces vectors whose content contradicts current ground-truth (stale claims, closed engagements, outdated targets). Proposes deletes/re-embeds; never silently mutates the index.
| name | discover-remote-friendly |
| description | 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. |
| disable-model-invocation | false |
| allowed-tools | Read, Write, WebSearch, WebFetch, Bash(mkdir *), Bash(test *) |
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.