mirror of
https://github.com/MadsLorentzen/ai-job-search.git
synced 2026-09-17 00:26:26 +00:00
docs: sync onboarding with linkedin-search + freehire-search reality (#150)
/setup still told non-DK users that built-in CLIs are Denmark-specific. Align setup, /add-portal, and search-queries.md with shipped country-agnostic CLIs and /scrape auto-discovery (post #85 / #95 / #102). Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
co-authored by
Cursor
parent
b20467df4a
commit
0a8fc194e5
@@ -1,6 +1,6 @@
|
||||
# /add-portal - Generate a Job-Portal Search Skill for Your Local Market
|
||||
|
||||
You are helping the user build a job-portal search skill for a job board in their market. The repo ships worked examples of the pattern (four Danish portals plus the country-agnostic `linkedin-search`), and the README invites users elsewhere to build equivalents — this command turns that invitation into a guided workflow: investigate the portal, scaffold the skill from the canonical structure, and test-run a live query before registering anything.
|
||||
You are helping the user build a job-portal search skill for a job board in their market. The repo ships worked examples of the pattern (four Danish portals plus the country-agnostic `linkedin-search` and `freehire-search`), and the README invites users elsewhere to build equivalents — this command turns that invitation into a guided workflow: investigate the portal, scaffold the skill from the canonical structure, and test-run a live query before registering anything.
|
||||
|
||||
The generator is **country-agnostic**: it works for any portal in any market and language. The skills it produces are typically market-specific and live in the user's fork (per repo policy, country-specific portal skills are not merged upstream — the generator is the upstream feature, its output is yours).
|
||||
|
||||
@@ -118,7 +118,9 @@ Do not proceed to Step 5 until search, detail, and tests all pass.
|
||||
|
||||
## Step 5: Register
|
||||
|
||||
1. Ask whether the user wants the new portal added to their `/scrape` search strategy. If yes, add the portal's site to the relevant query categories in `.claude/skills/job-scraper/search-queries.md` (site-specific queries, like the existing `jobindex.dk` entries) so `/scrape` includes it.
|
||||
1. Ask whether the user wants the new portal added to their `/scrape` search strategy. If yes:
|
||||
- The portal CLI itself is already picked up automatically by `/scrape` (it discovers `.agents/skills/*/SKILL.md`) — no further wiring is needed for CLI search/detail.
|
||||
- Optionally add WebSearch/`site:` placeholder queries for that board in `.claude/skills/job-scraper/search-queries.md` (use the `[YOUR_JOB_BOARD]` style placeholders already there) so the fallback path still covers the board if the CLI is unavailable.
|
||||
2. Remind the user to add the install line for their own records if they maintain a fork README:
|
||||
```bash
|
||||
cd .agents/skills/<name>/cli && bun install && cd ../../../..
|
||||
|
||||
Reference in New Issue
Block a user