Community forks & adaptations

[MadsLorentzen]

This template is deliberately kept universal: market-specific portals, language adaptations, and alternative-harness ports live in forks rather than upstream (see the policy discussions in #31, #39, #49, #67). This pinned thread is where those forks get discovered.

Maintaining a fork? Reply below with:

• A link to your fork
• What it adapts (market/country, language, job boards, agent harness)
• How closely it tracks upstream

Known adaptations so far:

• 🇨🇳 ai-job-search-cn by @cypggs - Chinese-language adaptation
• 🇨🇳 youngledo/ai-job-search by @youngledo - China-mainland market overlay (Chinese templates and workflows; from PR Add China market job-search overlay #67)
• 🇻🇳 ai-job-search-vn by @jamesng16 - Vietnam adaptation with an ITviec portal skill

Forks that follow the portal-skill contract (/add-portal generates compliant skills) stay compatible with upstream improvements - /scrape picks up any installed *-search skill automatically.

[jamesng16]

🇻🇳 Vietnam Fork: ai-job-search-vn

https://github.com/jamesng16/ai-job-search-vn

Working:

• ✅ ITviec — LaTeX Error: File `moderncv.cls' not found. #1 IT job board VN, Bun CLI, 5/5 tests
• ✅ LinkedIn VN — built-in

Blocked: TopCV (Cloudflare 403), VietnamWorks (SPA)

Built from HCMC 🇻🇳

[MadsLorentzen]

Excellent - and genuinely glad to see this. Going from yesterday's closed PR straight to a working ITviec skill with passing tests in your own fork is exactly the arc this policy hopes for. Adding you to the list in the opening post. If ITviec's markup ever shifts and you find the /add-portal investigation notes lacking, feedback welcome.

[youngledo]

Thanks for setting up this discussion, related PR link: #67.

I have published a China-mainland focused fork here: https://github.com/youngledo/ai-job-search-cn

This version may be a better fit for Chinese users who want a localized workflow while still staying close to upstream. The main reason is that the country/market-specific behavior is kept isolated under a China market layer instead of rewriting the core upstream workflow.

That gives it a few practical advantages:

• China-specific job search, profile fields, evaluation rules, templates, and manual fallback workflows can evolve independently.
• The fork can continue rebasing onto upstream regularly and pick up general improvements such as CI, interview prep, salary-tool fixes, and workflow refinements.
• Useful ideas from other China-focused forks can still be absorbed without making the core project harder to synchronize.
• The workflow supports public job search for China-market sites, but falls back to manually saved job descriptions when pages require login, block access, or return incomplete content.

The goal is not to push China-specific behavior upstream, but to keep a maintained Chinese version that benefits from upstream while respecting the market-specific boundary.

[MadsLorentzen]

Thanks for following through on this so quickly after #67 - a China-mainland adaptation with Chinese templates fills a real gap, and it's now listed in the opening post. Held to your own standard from the PR (gitignore discipline around personal job data), which deserved better than a plain decline.

[erikpr1994]

🇪🇸 Spanish market edition — https://github.com/erikpr1994/ai-job-search

A fork adapted for the Spanish job market: adds portal search skills for InfoJobs, Tecnoempleo, and GetManfred (LinkedIn + freehire stay as country-agnostic defaults), with /scrape and search-queries.md pointed at those boards and README/SETUP localized.

Profile files remain upstream placeholders — clone and run /setup to populate your own; no personal data in the repo. Built on the shipped /add-portal contract, so /scrape auto-discovers the portals. Feedback welcome.