Conciseness

The body is dense operational prose with no padding and no explanations of concepts Claude already knows; even the JS-portal rendering note is domain-specific knowledge (job.10086.cn etc. return empty shells) that Claude would not have. Every section carries rules or commands that earn their tokens.

Actionability

Guidance is copy-paste executable: concrete commands with defined variables ("python3 \"$S/radar.py\" --root \"$ROOT\" doctor", "radar.py --root \"$ROOT\" --run <run> init --plan <that file>", "collect-ats --config source.json", "ingest --input observations.json", "radar.py watch --add <entry.json>") plus named plan fields (scope, instances, max_records, priority) and concrete file paths.

Workflow Clarity

The procedure is a clearly numbered doctor → init → collect → screen → export → closeout sequence with explicit validation checkpoints and feedback loops: closeout refuses runs missing quota_note, watch_missing entries, current rules, or a current workbook; failures are reported as "not complete" with reasons; amend/resume paths handle mid-run changes and lease contention. Batch operations are well covered by validation, so no cap applies.

Progressive Disclosure

Verified against the actual bundle: all six references cited in the body (hosts.md, record-schema.md, feishu-source.md, collection.md, portals.md, jev.md) exist in references/, are one level deep with no nested references, and each link is signaled with when to read it; detailed schemas and scripts (radar.py, initial_filter.py, workbook.py) are properly deferred out of the overview.

Specificity

The description lists four concrete actions — "搜索大陆与国际官方招聘和结构化岗位合集", "交叉核查来源", "执行有证据的第一轮硬条件淘劣", "记录标准化的初筛结果（本地工作表可选）" — giving comprehensive coverage of the stage-1 workflow rather than only minor-gap coverage.

Completeness

It explicitly answers both what (search, cross-check, hard-condition elimination, standardized recording) and when ("用于岗位搜索、初筛和批次更新"), and adds explicit negative triggers ("不做评级排序或飞书交付（交给 potential-position），不投递"), matching the anchor for both what and when with concrete trigger phrases.

Trigger Term Quality

Natural trigger phrases are present ("岗位搜索", "初筛", "批次更新", "招聘"), so it exceeds the some-relevant-keywords level, but common variations users would say in this domain are missing (e.g. 校招/秋招/求职/找工作, and no plain English "job search" triggers beyond the "stage-1 job radar" gloss), so it is not at the comprehensive-synonyms level.

Distinctiveness Conflict Risk

It carves out a clear niche (stage-1 search/hard elimination only) and explicitly hands ranking, shortlists and Feishu delivery to a sibling skill, so it is unlikely to trigger for the wrong skill.