ficilcom/otame4-work-skills / skills/research/scout-message-triage
scout-message-triage
VerifiedSort incoming scout messages and agent-forwarded openings by what they actually disclose: whether the employer is named at all, which of pay, location, employment type, and duties are stated, whether the message refers to the applicant's own history or reads as a mass send, whether a stated salary is an offer or a "up to" figure, and whether the same employer has arrived through more than one route. Use when a user has a backlog of scout messages and wants to know which ones can be researched, what to ask before replying, and what to settle before handing over a resume; do not use to rate how promising an opening is, to judge an employer or an agent, or to reply on the user's behalf.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.5 KB |
| references/report-format.md | markdown | 1.6 KB |
| references/triage-criteria.md | markdown | 5.9 KB |
| scripts/_common.py | script | 9.9 KB |
| scripts/triage_scouts.py | script | 9.4 KB |
references/report-format.md
View on GitHub# 報告書形式
## 1. 仕分けの結果
| ID | 企業 | 職種 | 経路 | 欠けている条件 | 次の段階 |
| --- | --- | --- | --- | --- | --- |
**優先度や点数を付けない。** 並べ替えるなら受信日順か返信期限順にする。文面の印象で並べ替えない。
企業名が明かされていないものは表の先頭に出す。それ以外の分析ができないため。
## 2. 確認すること
企業名、欠けている条件、年収の書き方。**誰に聞くか**(送り主のエージェント、プラットフォーム経由、企業に直接)を添える。
## 3. 経歴を渡す前の判断
登録や面談が必要なものについて、渡す情報の範囲を並べる。
- 渡す範囲(全文か要約か)
- 現職の社名を出すか
- 他社の選考状況を伝えるか
**どれも利用者が決める。** 推奨しない。
## 4. 経路が重なっているもの
同じ企業を複数の経路から受けている場合、その事実と、先に経路を決める必要があることを書く。**どの経路が有利かを書かない。**
## 5. 返信
返信の要否、期限、見送る場合の扱い。**文面の下書きまでにし、送信しない。**
## 書かないこと
- スカウトの熱意、丁寧さ、本気度の評価
- 求人や企業の良し悪し(`company-research` の範囲)
- エージェントや媒体の優劣
- 応募すべきかどうかの結論
- 返信すれば選考が有利になるという見込み
- 期限が短いことを根拠にした急ぎの推奨
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |