القائمة
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.
التثبيت باستخدام 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.
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.
| name | opportunity-update |
| description | 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. |
Role: Assistant — career / opportunity tracking (see docs/AGENT_ROLES.md).
Context to load:
data/opportunities.yaml — read for context; use opp.py for writestemplates/opportunities_tracker_template.yamlScope:
opportunities.yaml + schema.Task:
id (or company + role — resolve to id first).python scripts/opp.py for all scalar field changes. Run python scripts/opp.py --help first; see docs/opp-cli.md for exceptions and tests only.contacts[] — add/update/remove contact entry (name, role, channels map, notes). Merge with existing list; don't wipe unmentioned entries.links — add/update URL key (application_portal, job_posting, or free key). Merge with existing keys.python scripts/opp.py get <id> after any write.Output:
opp.py command(s) run + outputConstraints:
Inputs (collect, confirm, or ask):
data/opportunities.yaml: ask before proposing patch.<...><...>