New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Endgame

by microsoft in microsoft/copilot-for-eclipse

Orchestrate endgame verification for a GitHub milestone issue.

OfficialMITAuto-check passedTesting & QA

Install Endgame

skills CLI
$ npx skills add microsoft/copilot-for-eclipse --skill endgame -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install microsoft/copilot-for-eclipse endgame --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/microsoft/copilot-for-eclipse.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/endgame .claude/skills/endgame && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
endgame
GitHub stars
126
Token cost
~1.4k tokens
SKILL.md length
560 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Orchestrate endgame verification for a GitHub milestone issue.

  • Works in 7 steps: Ask the user for inputs → Fetch the endgame issue (ONE call only) → Process each task via subagent → …
  • Tasks that involve Test generation
  • SKILL.md covers Workflow, Task Details, Your Mission and Notes
  • Calls gh

What it does

Endgame is an agent skill from microsoft/copilot-for-eclipse, published by the product's own GitHub organization. Orchestrate endgame verification for a GitHub milestone issue. Fetches the issue, parses assigned tasks, delegates each task to a subagent that researches the linked PR/issue and writes a test plan, and saves every plan to com.microsoft.copilot.eclipse.swtbot.test/test-plans/ following the project's standard test-plan format.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test generation, Subagents and Project management. It works with GitHub. The repository describes itself as: GitHub Copilot plugin for Eclipse IDE. The licence is MIT.

When your agent uses it

  • Tasks that involve Test generation
  • Tasks that involve Subagents
  • Tasks that involve Project management

Example prompts

  • “/endgame”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Ask the user for inputs
  2. Fetch the endgame issue (ONE call only)
  3. Process each task via subagent
  4. Research the task
  5. Create the test-plan file
  6. Return a brief summary
  7. Final summary

What it can do on your machine

Read from SKILL.md and the folder at commit 00733c2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Endgame loads about 1.4k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 560 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~84
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from microsoft/copilot-for-eclipse at commit 00733c2, republished under its MIT licence (© microsoft). 560 words, ~1,354 tokens.

Download SKILL.mdSave it as .claude/skills/endgame/SKILL.md (or your agent's skills folder).
name
endgame
description
Orchestrate endgame verification for a GitHub milestone issue. Fetches the issue, parses assigned tasks, delegates each task to a subagent that researches the linked PR/issue and writes a test plan, and saves every plan to com.microsoft.copilot.eclipse.swtbot.test/test-plans/ following the project's standard test-plan format.

Endgame Verification Skill

Use this skill to run an endgame verification pass for a GitHub milestone issue. Each task in the issue is delegated to a subagent that researches the linked PR/issue and writes a test plan under com.microsoft.copilot.eclipse.swtbot.test/test-plans/.

Workflow

⚠️ CRITICAL — YOU MUST FOLLOW THESE RULES:

  1. Do NOT run gh pr view or gh issue view for individual tasks — only run it once for the main endgame issue.
  2. Do NOT research or analyse any task yourself.
  3. Do NOT create any test-plan files yourself.
  4. IMMEDIATELY call runSubagent for each task after parsing the issue — no delays, no research.
Step 1 — Ask the user for inputs

Ask for:

  • The GitHub endgame issue URL (e.g. https://github.com/microsoft/copilot-for-eclipse/issues/XXXX)
  • The user's GitHub account name
Step 2 — Fetch the endgame issue (ONE call only)
shell
gh issue view <issue_number> --repo microsoft/copilot-for-eclipse --json body --jq '.body'

Parse the body to find all tasks (checkboxes) assigned to the specified user. Extract each task's title and any linked PR/issue URL as plain text.

STOP — do NOT fetch any of the linked PRs or issues.

Step 3 — Process each task via subagent

For each task, call runSubagent with:

  • description: "Endgame: <short_task_title>"
  • prompt: the template below, filled in with only the info you extracted.
Subagent prompt template

Task Details

  • Task Number: <N>
  • Task Title: <task_title>
  • Assignee: <username>
  • Related Issue/PR: <link_if_available> (NOT YET FETCHED — you must fetch this)

Your Mission

YOU (the subagent) must research this task AND create the test-plan file.

Step 1: Research the task
  • Fetch the linked PR or issue with gh pr view / gh issue view.
  • Understand what feature or fix needs to be verified.
  • If anything is ambiguous or unclear after reading the PR/issue, ask the user for clarification before proceeding. Keep asking until you have enough information to write concrete, accurate test steps.
Show full SKILL.md (271 more words)Show less
Step 2: Create the test-plan file

Determine a short <feature-slug> (lowercase, hyphens, no special chars) derived from the task title (e.g. chat-history-restore).

Create the directory and file:

com.microsoft.copilot.eclipse.swtbot.test/test-plans/<feature-slug>/<feature-slug>.md

Use exactly this format, matching the project's existing test plans (see com.microsoft.copilot.eclipse.swtbot.test/test-plans/thinking-persistence/thinking-persistence.md for a live example):

markdown
# <Feature / Task Title>

## Overview
<1–3 sentences: what is being verified and why it matters.>

---

## Test Cases

### TC-001: <Specific test case title>

**Type:** `Happy Path`
**Priority:** `P0`

#### Preconditions
- <Specific state required before starting these steps>

#### Steps
1. <Detailed, concrete step>
2. <Next step>
3. <Continue as needed>

#### Expected Result
- <Observable outcome that proves the feature works>

#### 📸 Key Screenshots
- [ ] **<Label>** — <What to capture>

---

### TC-002: <Next scenario if needed>
<!-- Repeat TC block for each distinct scenario. Use TC-003, TC-004, … -->

---

## Screenshots Checklist
> Consolidated list of all key screenshot moments.

- [ ] `TC-001` <Label>
- [ ] `TC-002` <Label>

Guidelines:

  • Overview: 1–3 sentences max. Do not repeat what is already covered by Preconditions or Steps.
  • Type values: Happy Path, Negative, Edge Case, Regression.
  • Priority values: P0 (must-pass), P1 (high), P2 (medium).
  • Use 3-digit zero-padded TC numbers: TC-001, TC-002, TC-003, …
  • Omit 📸 Key Screenshots within a TC block if there are no meaningful screenshots to capture for that case.
  • Keep the ## Screenshots Checklist section at the end — list every screenshot across all TC blocks.
  • If you are still unsure about any step after researching, ask the user before writing that step — do not guess.
Step 3: Return a brief summary

Return ONLY:

  • File path created (e.g. com.microsoft.copilot.eclipse.swtbot.test/test-plans/chat-history-restore/chat-history-restore.md)
  • One-line summary of what needs to be verified
Step 4 — Final summary

After all subagents complete, provide:

  • A table of all generated test-plan files
  • Total tasks processed
  • Any tasks that could not be processed (with reasons)

Notes

  • NEVER run gh pr view or gh issue view on task links yourself — only on the main endgame issue. Subagents handle the individual links.
  • NEVER analyse or research tasks yourself — immediately delegate to subagents.
  • Each subagent runs independently.
  • Subagents should be concise — create the file and return a brief summary.
  • If a task is still unclear after the user is asked, note the outstanding question inside the test-plan file.
  • Use slugified task titles for the feature slug and directory name (lowercase, hyphens, no special characters).

© microsoft, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/endgame of microsoft/copilot-for-eclipse.

Open the folder on GitHubat commit 00733c2

Compare with similar skills

Endgame next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Endgame compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Endgame this skillmicrosoft/copilot-for-eclipse126—~1.4kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Gh Issuestrpc-group/trpc-agent-go1.8k8 repos~8.7kAutomated safety check: PassApache-2.0
Explore Feature E2E Testcomet-ml/opik22k—~3.4kAutomated safety check: PassApache-2.0
Kane CLI Browser TestingLambdaTest/kane-cli247—~8.4kAutomated safety check: PassApache-2.0
Megatron GB200 One-Node Test OnboardingNVIDIA/Megatron-LM18k—~1.3kAutomated safety check: PassApache-2.0

Similar skills

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Gh Issues

    trpc-group/trpc-agent-go

    Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments.

    1.8k GitHub starsUsed in 8 repos~8.7k tokens
    Agent WorkflowsAuto-check passed

  • Explore Feature E2E Test

    comet-ml/opik

    Turns a code change into one committed, passing Playwright end-to-end spec by resolving the change scope and handing authoring to a companion skill.

    22k GitHub stars~3.4k tokensUpdated today
    Testing & QAAuto-check passed

  • Kane CLI Browser Testing

    LambdaTest/kane-cli

    Drives a real browser through the kane-cli tool and designs requirement-linked test suites from a PRD or a plain description, with mobile and cloud-grid runs.

    247 GitHub stars~8.4k tokensUpdated 2 days ago
    Testing & QAAuto-check passed

  • Megatron GB200 One-Node Test Onboarding

    NVIDIA/Megatron-LM

    Official

    Creates one-node GitHub merge-request variants of existing two-node GB200 functional tests in Megatron-LM, adjusting parallelism settings to fit four GPUs.

    18k GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-check passed

  • Agent Integration Testing

    av/mi

    Writes plain-English integration test specs with verifiable steps and expectations, then runs each one through a subagent that reports pass or fail with logs.

    102 GitHub stars~908 tokensUpdated 11 days ago
    Testing & QAAuto-check passed

More from microsoft/copilot-for-eclipse

  • UI Action

    microsoft/copilot-for-eclipse

    Official

    Authors and validates SWTBot JSON probe scripts for GitHub Copilot for Eclipse UI flows against a real Eclipse workbench.

    126 GitHub stars~1.1k tokensUpdated 8 days ago
    Auto-check passed

Works with

Categories

Questions about Endgame

What does Endgame do?

Orchestrate endgame verification for a GitHub milestone issue. Endgame is an agent skill from microsoft/copilot-for-eclipse, published by the product's own GitHub organization. Orchestrate endgame verification for a GitHub milestone issue.

When should I use Endgame?

Endgame fits situations like: tasks that involve Test generation; tasks that involve Subagents; tasks that involve Project management.

How do I install Endgame in Claude Code?

Run `npx skills add microsoft/copilot-for-eclipse --skill endgame -a claude-code`. Or copy the skill folder (.github/skills/endgame in microsoft/copilot-for-eclipse) into .claude/skills/endgame in your project. Claude Code loads it when a task matches its description.

How do I install Endgame in Codex?

Run `npx skills add microsoft/copilot-for-eclipse --skill endgame -a codex`. Or copy the skill folder (.github/skills/endgame in microsoft/copilot-for-eclipse) into .agents/skills/endgame in your project. Codex loads it when a task matches its description.

Can I use Endgame in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft/copilot-for-eclipse --skill endgame -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/endgame, .gemini/skills/endgame, .github/skills/endgame and .opencode/skills/endgame in your project.

What does Endgame need to run?

Going by SKILL.md and its folder, Endgame needs the command-line tools its instructions call (gh).

Does Endgame access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Endgame safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Endgame use?

Endgame is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Endgame use?

About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Endgame?

Skills that share tags, products or a category with Endgame: CCPM Project Management (automazeio/ccpm, 8.4k stars), Gh Issues (trpc-group/trpc-agent-go, 1.8k stars), Explore Feature E2E Test (comet-ml/opik, 22k stars) and Kane CLI Browser Testing (LambdaTest/kane-cli, 247 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Endgame?

microsoft (a GitHub organization, an official publisher) maintains it in microsoft/copilot-for-eclipse, which has 126 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 30, 2026.

Source: microsoft/copilot-for-eclipse on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.