ftja-remote
Draft (or redraft) the Remote check's setup for the user to confirm — the remote-work keywords, the categories the model answers, and which answers pass or fail — from where they live, where they want to work, their time zone and their work permit. Invoke when the user says "/ftja-remote", "set up the remote check", "write the remote setup", or when `ftja.run_bridge wait` returns {"status": "remote"} (the Pipeline tab's button).
TaegyuJEONG · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add TaegyuJEONG/ftja --skill ftja-remote技能说明
name: ftja-remote
description: Draft (or redraft) the Remote check's setup for the user to confirm — the remote-work keywords, the categories the model answers, and which answers pass or fail — from where they live, where they want to work, their time zone and their work permit. Invoke when the user says "/ftja-remote", "set up the remote check", "write the remote setup", or when ftja.run_bridge wait returns {"status": "remote"} (the Pipeline tab's button).
FTJA remote check setup
The Remote check is an optional stage of /ftja-run, between the code
filter and Stage 1. A cheap model reads only the title and the sentences
around the user's remote keywords, and answers a few questions (the
"categories") by picking from a fixed list of answers. Code then applies
the rule the user set for each answer. Your job here is to write a good
first version of that setup for this user. They edit it afterwards on the
Pipeline tab, so write something sensible and complete, not something
cautious and empty.
Every python call uses venv/bin/python. On Windows, read every venv/bin/python as venv\Scripts\python (and venv/bin/pip as venv\Scripts\pip), and run commands in PowerShell. The rules for each system (one shell, time limits, never cutting a command's output short) are in .agents/skills/ftja-setup/windows.md and mac.md: read the one for this system first. Write the draft files this skill passes with --file using your file-writing tool, not PowerShell > or Set-Content, which do not write plain UTF-8.
Never edit remote-check.json,
remote-request.json or criteria.json by hand; the commands below write
them.
0. Be in the right folder
Run pwd and git rev-parse --show-toplevel. Continue only in the user's
existing FTJA folder (it has criteria.json). If the session is not
attached to it, attach it as /ftja-run step 0a describes. Do not start
or restart the viewer for this; if it is running it will show your
progress by itself.
1. Work out the user's situation
The setup is written for four facts about the user: where they live, which countries or regions they want to work in, their time zone, and what work permit they hold.
venv/bin/python -m ftja.remote request
First tell the viewer you have started, so the page shows that the draft is being written:
venv/bin/python -m ftja.remote begin
Then settle the four facts, in this order of trust:
answersin the request that are not empty: the user typed or confirmed these on the page. Use them as they are.- For each one that is empty, work it out yourself, without asking:
profile/summary.md(where they live, citizenship, visa or permit, the places they say they want to work), thencriteria.json'slocations(where their searches look is where they want to work), then the usual time zone of where they live. - What you still cannot tell, leave empty. Do not invent a work permit.
Do not ask the user in the chat: they confirm or correct all four on the
page before anything is used. The one exception is when you cannot tell
where they live at all and the request did not come from the page
(status was none): then ask that one question.
From here on, if you cannot finish, run
venv/bin/python -m ftja.remote fail --error "<one plain sentence>" before
you stop, so the page does not wait for you.
2. Read what is there
criteria.json→languages: the languages the user reads postings in (ISO codes; empty means any, then use English plus the main language of where they live). Keywords are written in each of these languages.venv/bin/python -m ftja.remote show: the current setup. Ifsavedis false, what it prints is the general built-in setup: use it as a list of ideas and write a fresh one. Ifsavedis true the user already has one: keep every category you do not recognise as one of the five below (they added it), and keep theidof every category and answer that still exists, even if you reword it.
2b. Only a language is missing? That is another skill
show also prints languages_without_keywords: languages the user reads
postings in that the draft (or, with no draft, the saved setup) has no
keyword for. If that list is not empty and the request did not come from
the page's setup button (status was none, drafted or done), the
user most likely wants just those keywords: stop here and follow the
ftja-keywords skill (.agents/skills/ftja-keywords/SKILL.md) instead. It
adds a language's keywords without touching the rest.
3. Write the setup
Write it as JSON to .ftja-run/remote-check.draft.json (create .ftja-run/
if it is missing):
{"languages": ["en", "fr"],
"keyword_language": {"remote": "en", "télétravail": "fr", "à distance": "fr"},
"drop_without_keywords": true,
"guidance": "<two or three sentences for the model, see below>",
"profile": {"residence": "...", "work_countries": "...", "time_zone": "...", "work_permit": "..."},
"categories": [
{"id": "remote_level", "label": "Remote level",
"question": "How remote is the role itself?",
"keywords": ["remote", "work from home", "hybrid", "..."],
"options": [{"id": "fully_remote", "label": "Fully remote", "rule": "pass"},
{"id": "hybrid", "label": "Hybrid: regular office days", "rule": "fail"},
{"id": "on_site", "label": "On-site", "rule": "fail"}],
"unknown": "pass"}]}
Categories. Write these five, with these ids, wording the labels for this user:
remote_level— how remote the role is. Answers: fully remote (pass), hybrid with regular office days (fail), on-site (fail).work_location— from where the person may work. Answers, named for this user: anywhere (pass); a region or list that includes where they live or want to work, e.g. "Includes France or the EU" (pass); only places that leave those out, e.g. "Only outside the EU" (fail).work_authorization