Menu
Deprecated for GPT-5.6 Sol. Native Codex Plan Mode performs read-first repository grounding and evidence collection.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | repo-map-codex |
| description | Deprecated for GPT-5.6 Sol. Native Codex Plan Mode performs read-first repository grounding and evidence collection. |
Deprecated for GPT-5.6 Sol. Native Codex Plan Mode performs read-first repository grounding and evidence collection. Do not use this package for new work.
Create a durable map of the project so later planning is grounded in evidence rather than memory. The map adapts to software with Git, software without Git, business artifact work, and mixed business-coding projects.
software-git, software-no-git, business-artifact, or mixed-business-coding.rg --files, rg, normal file reads, and parallel reads with multi_tool_use.parallel when available.repo-map.md or equivalent project map.evidence-catalog.md that lists source materials, attempt/outcome status, and relevance..deep-planning/project-mode.md..deep-planning/repo-map.md and .deep-planning/evidence-catalog.md using the deep-planning artifact contract. The evidence catalog must include Failure mechanism for failed, partial, stale, or unreached evidence.N/A in Failure mechanism for successful evidence rows..deep-planning/state.md. Use READY_FOR_PROCEED only when the map and evidence catalog are complete enough for the next planning phase.BLOCKED_BY_MISSING_EVIDENCE and make Next action name the exact source, access, or probe needed.Read the relevant reference before writing the map:
references/software-git.mdreferences/software-no-git.mdreferences/business-artifact.mdreferences/mixed-business-coding.mdThe map must include:
When used inside deep planning, write only to the target project's .deep-planning/repo-map.md and .deep-planning/evidence-catalog.md unless the user specifies another planning workfolder.