Swissdevjobs

swissdevjobs skill

Drives the swissdevjobs-cli tool to search, inspect, and apply across three platforms: the all-IT devitjobs family (swissdevjobs.ch, germantechjobs.de, devitjobs.uk/.com/.nl/.fr — salary always published), JobCloud (jobs.ch, jobup.ch — every Swiss industry, ~50k postings, no salary data), and MyCareersFuture (Singapore's government job portal — IT only, ~9k postings, salary published in SGD).

jobs.ch/jobup.ch are search-driven: without a query they only return their newest postings, so always pass the user's actual search terms (sdj list "<terms>"), and add --category it to keep those two boards in tech. Board selectors take a board id (--board jobsch) or a country code (--board ch = all three Swiss boards). Their postings have no native apply — direct-apply answers no_native_apply with the real ATS URL; follow browser mode.

MyCareersFuture is search-driven too (--board sg or --board mycareersfuture), for the same reason: ~9k IT postings, 100 rows per page. It does publish salary (annualized from the monthly SGD figure) and skills, so --min-salary, --tech, and --remote work there; --visa, --level, and --workload don't exist on its wire and exclude it visibly. It has no native apply either — applying happens on the posting page through the portal's own flow, so direct-apply refuses with that page's URL and you continue in browser mode.

Prefer the MCP server when it is connected. swissdevjobs-cli also ships an MCP server exposing search_jobs, list_boards, get_job, apply_to_job, list_applications, mark_applied and top_technologies. If those tools are available, use them — they return structured data directly and apply_to_job carries its own confirmation gate. Fall back to the CLI below when they are not. Board facts (scope, currency, salary availability, categories, apply capability) come from list_boards / sdj boards — ask the tool, don't guess.

The easiest way to get them is the plugin, which bundles its own skill:

/plugin marketplace add Stupidoodle/swissdevjobs-cli
/plugin install swissdevjobs@swissdevjobs

Setup

Install the CLI (pipx install git+https://github.com/Stupidoodle/swissdevjobs-cli, or pip install -e . from a checkout), then store the applicant identity once:

sdj config --init      # writes ~/.config/swissdevjobs-cli/.env
sdj config             # verify what resolved, and from which file

SDJ_NAME="Your Name"
SDJ_EMAIL="you@example.com"
SDJ_CV="/absolute/path/to/cv.pdf"

.env is read from $SDJ_ENV_FILE, then ./.env (walking up), then the config directory. Real environment variables and explicit --name / --email / --cv flags both win over the file. Without an identity from some source, sdj direct-apply refuses to run — run sdj config to see what it found.

Tooling

CLI binary: sdj (alias swissdevjobs). Every command accepts --json for machine-readable output — prefer --json whenever you're going to act on the results. Since 0.6, list --json returns compact summary rows in an envelope (with boards_searched and a coverage note), capped at 50 unless you pass --limit (0 = uncapped). --raw restores the full wire rows (~470 tokens each — always cap those with --limit). Filters a board's platform cannot serve (salary, remote, visa, level on jobs.ch/jobup.ch; visa, level, workload on MyCareersFuture; --workload on the devitjobs boards) exclude that board visibly: the envelope carries boards_excluded and the note explains it — drop the filter to search those boards. --tech still reaches jobs.ch/jobup.ch (the terms travel server-side as the full-text query), and --contract works on every board via shared aliases (permanent, freelance, …).

sdj boards                                    # every board, as data
sdj list --tech Python --remote --min-salary 130000 --json --limit 25
sdj show <id|slug> --json
sdj apply <id|slug> --json                    # surface the apply mechanism
sdj apply <id|slug> --json --complete email   # mark as applied via email
sdj direct-apply <id|slug> --motivation "text or /path/to/letter.txt"
sdj direct-apply <id|slug> --cv /path/to/cv_de.pdf --motivation ...  # override CV
sdj applications --json                       # list tracked applications
sdj stats                                     # cache + application counts
sdj config                                    # resolved identity + paths
sdj auth                                      # clear a Cloudflare challenge

Agent-friendly behaviour:

• sdj list hides jobs already applied to (--include-applied to override).
• sdj apply --json returns an applied field — null when not yet applied.
• sdj direct-apply --json returns {"already_applied": true, ...} for a duplicate rather than failing.
• Applications are tracked automatically in SQLite at ~/.cache/swissdevjobs-cli/swissdevjobs.db.

Workflow: search → shortlist → apply

1. Search. sdj list … --json --limit 25. Already-applied jobs are filtered out.
2. Check the apply route. sdj apply <id> --json returns a mode and a fallback_mode.
3. Inspect. sdj show <id> --json for any candidate you're unsure about.
4. Apply via the mode below. On success the application is recorded in the local database.

mode == "direct"

sdj direct-apply <id> --motivation /path/to/letter.txt

--cv defaults to $SDJ_CV. Pass it explicitly when the posting's language calls for a different CV than the default.

Submits through the site's own apply form (POST /api/jobApply, multipart). --motivation takes either inline text or a path to a .txt file. The motivation letter must not contain < or > — the site rejects them.

direct-apply refuses with exit code 2 when the posting is syndicated from an aggregator, when it merely links out to the company's own ATS, or always on jobs.ch/jobup.ch and MyCareersFuture (no_native_apply — the platform has no native apply endpoint). In every case the command routes you to the ATS URL instead. Follow the browser mode.

mode == "email"

apply_email is populated. Draft a motivation letter in the posting's language, attach a CV matching that language, and send it through the user's mail client.

1. Save the draft to a file first so the user can review it.
2. Send via the user's configured mail client, or open a mailto: link.
3. Afterwards: sdj apply <id> --json --complete email.