القائمة
Use when the user asks for a handoff, session summary, context packet, continuation note, or wants another agent or future session to pick up the current work.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
native microsoft excel automation for windows .xlsx/.xlsm/.xls/.csv/.tsv workflows. use when chatgpt, codex, or claude code is running on windows with microsoft 365 excel installed and needs to refresh, recalculate, validate, or route a workbook through excel com automation. trigger for workbook connections, cached values, pivottables, calculation correctness, refreshing an existing power query connection, data model-aware routing, chart-ready data, no-template spreadsheet deliverables, or excel environment self-test. does not support authoring or editing power query m code, or macro execution -- see "known gaps" below. do not use for cloud execution, non-windows environments, google sheets api workflows, or machines without excel desktop installed.
Archived. Do not install or invoke for Claude Code or Codex GPT-5.6 Sol. Use the repository's scaffolds/agent-project-scaffold for the maintained scaffold or native Codex planning and execution controls.
Create a comprehensive project archive and handoff package — curated workfolder copy, evidence and state, agent context, and dark-mode HTML memo — from Claude Code or Codex projects. Use for milestone archives, cold-start continuation packages, or comprehensive handoffs; use a lightweight session-handoff skill for a short continuation note.
use only in Claude Code as an explicit provider router when Graphify, code-mapper, or selective CodeQL availability must be assessed. do not install or auto-trigger for Codex GPT-5.6 Sol; native direct inspection, Plan Mode, explorer work, and subagents cover this routing without an added analyzer.
Generate deterministic Python import, reference, artifact, contract, catalog, OpenLineage, and explicitly authorized local CodeQL maps. Use for explicit Python blast-radius, callers, inputs/outputs, APIs/schemas, Backstage relationships, lineage, or local value/taint evidence; do not use for ordinary code search, broad repository exploration, or simple edits.
Deprecated for GPT-5.6 Sol. Use native Codex Plan Mode, with focused verification or adversarial review skills when needed.
| name | handoff-codex |
| description | Use when the user asks for a handoff, session summary, context packet, continuation note, or wants another agent or future session to pick up the current work. |
Write a concise handoff document so a fresh agent or future session can continue the work without rereading the whole conversation.
Save the handoff under the active session folder unless the user specifies another destination. For projectless sessions, follow the workstation policy for resolving the real Documents folder and creating a dated session folder.
Use the operating system temporary directory only when the active instructions explicitly permit it. Do not modify repository files for a handoff unless the user explicitly asks for a repo-tracked artifact.
After writing the file, tell the user its absolute path.
Treat the user's invocation text as the intended focus of the next session. If the user gives no focus, infer it from the latest active task and call out that inference in the handoff.
Include:
Do not duplicate content already captured in PRDs, plans, ADRs, issues, commits, diffs, or other artifacts. Reference those artifacts by path or URL instead.
