菜单
Official entry point for any GitHub task. Routes every GitHub request to the right specialist - governance, operations, Actions workflows, composite actions, PR lifecycle, or Copilot platform research - or to /internal-github-strategic for high-level decision framing. Use for any GitHub request, scoped or ambiguous.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Use when creating, reviewing, or materially revising a repository-owned Copilot agent under `.github/agents/`.
Use when /internal-aws selects the AWS governance lane for IAM operating models, trust policies, federation, permission boundaries, SCPs, tag policies, exception controls, or access guardrails.
Use when /internal-aws selects the AWS Lambda lane for handlers, event sources, runtimes, packaging, retries, concurrency, cold starts, or Lambda-specific configuration.
Use when /internal-aws selects the AWS research lane to retrieve current official AWS documentation, regional availability, service behavior, IAM state, or policy-simulation evidence.
Use when /internal-aws selects the AWS operations lane for monitoring, logging, rollout validation, backup and restore proof, DR evidence, reporting, or audit evidence.
| name | internal-github |
| description | Official entry point for any GitHub task. Routes every GitHub request to the right specialist - governance, operations, Actions workflows, composite actions, PR lifecycle, or Copilot platform research - or to /internal-github-strategic for high-level decision framing. Use for any GitHub request, scoped or ambiguous. |
| user-invocable | true |
Use this skill as the single explicit entry point for GitHub work. Classify the requested deliverable, invoke the minimum owner set, and stop routing after every requested deliverable has an owner.
Use for any GitHub request, including a scoped implementation, an operational check, a governance decision, a pull-request task, current-platform research, or an ambiguous request whose deliverable is not yet clear.
| Destination | Primary deliverable |
|---|---|
/internal-github-strategic | Platform or operating-model decision with option comparison, tradeoff analysis, or multi-lens framing |
/internal-github-governance | Rulesets, permissions, Apps, Actions permissions, OIDC trust, secrets, environments, CODEOWNERS, or Copilot policy |
/internal-github-operations | Actions health, runners, audit evidence, reporting, drift, preflight, rollout validation, or post-rollout proof |
/internal-github-actions | Workflow authoring or debugging under .github/workflows/, including workflow_call and reuse-pattern selection |
/internal-github-action-composite | Composite-action work under .github/actions/, including inputs, outputs, shell safety, tests, documentation, and compatibility |
/internal-github-pr | Pull-request creation, body updates, readiness, reviews, merge, or terminal-state verification |
/internal-copilot-docs-research | Current Copilot or MCP platform behavior when freshness materially affects the answer |
When independent deliverables are requested, assign each a primary owner and invoke them in dependency order. A decision precedes its resulting control design; a control design precedes rollout evidence; workflow behavior and composite-action authoring remain separate implementation deliverables. Keep each invocation focused on its own output.
