메뉴
Builds the full opportunity pipeline markdown report from opportunities.yaml using opportunity_report_tracking template. Use when the user asks for tracking list report, pipeline snapshot, or opportunity-tracking markdown output.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Researches a company and writes a structured SWE-focused brief with source discipline, personal fit vs master.yaml, and Proceed/Pass-style conclusion. Use when the user asks for company research or employer due diligence.
End-to-end JD processing workflow: normalize raw JD, research company, score fit/gap, generate analysis reports, and import to opportunity tracker. One-shot skill that orchestrates the full analysis and opportunity import.
Reads a raw JD and produces a YAML snippet for opportunities.yaml plus optional jd_catalog.csv row. Use when adding a new pipeline opportunity from data/raw, ingesting a JD file, or bootstrapping opportunity id and next_action fields.
Produces next-steps markdown for a single opportunity from opportunities.yaml using opportunity_report_next_steps_one template. Use when the user asks for one-opportunity next actions, 24–72h moves, or snapshot for a given id.
Builds sorted rollup of next actions across all active opportunities using opportunity_report_next_steps_rollup template. Use when user asks for combined backlog, rollup next steps, or sorted pipeline todos by date.
Updates one opportunity in opportunities.yaml (stage, next actions, close outcome, history). Use when the user changes pipeline stage, notes, next_action, or closes an opportunity by id.
| name | opportunity-report-tracking |
| description | Builds the full opportunity pipeline markdown report from opportunities.yaml using opportunity_report_tracking template. Use when the user asks for tracking list report, pipeline snapshot, or opportunity-tracking markdown output. |
Role: Assistant — career / opportunity tracking (see docs/AGENT_ROLES.md).
Context to load:
data/opportunities.yamltemplates/opportunity_report_tracking.mdScope:
Task:
active where stage not Closed (or include Closed in separate subsection if user asks).future_desired (include next_action columns if present).data/reports/pipeline/ (full-detail tracking; gitignored, real company names fine).Output: Markdown ready to save as data/reports/pipeline/opportunity-tracking-<YYYY-MM-DD>.md (path local / gitignored).
Constraints:
My inputs (collect, confirm, or ask):
no and ask confirmation).<yes | no | only counts>