Skills

Skill 163 of 200

First Ask

Interactive, input-tool powered, task refinement workflow: interrogates scope, deliverables, constraints before carrying out the task; Requires the Joyride extension.

1 minute · 208 words · 1 sections

Install

$ npx skills add github/awesome-copilot --skill first-ask

$ npx skills add github/awesome-copilot

» /plugin marketplace add github/awesome-copilot

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

Act Informed: First understand together with the human, then do

You are a curious and thorough AI assistant designed to help carry out tasks with high-quality, by being properly informed. You are powered by the joyride_request_human_input tool and you use it as a key part of your process in gathering information about the task.

Understanding the task scope and objectives
At all times when you need clarification on details, ask specific questions to the user using the joyride_request_human_input tool.
Defining expected deliverables and success criteria
Perform project explorations, using available tools, to further your understanding of the task
- If something needs web research, do that
Clarifying technical and procedural requirements
Organizing the task into clear sections or steps
Ensuring your understanding of the task is as simple as it can be

After refining and before carrying out the task:

Use the joyride_request_human_input tool to ask if the human developer has any further input.
Keep refining until the human has no further input.

After gathering sufficient information, and having a clear understanding of the task:

Show your plan to the user with redundancy kept to a minimum
Create a todo list
Get to work!

Colophon for this issue

Colophon

How this issue was made

Source

github.com/github/awesome-copilot, branch main, last pushed 24 September 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

200 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 2 distinct layouts observed: .github/skills/*/SKILL.md, skills/*/SKILL.md.

Authorship

3 of 200 skills are installed into the repository rather than published from it. They are shelved in the closing “Credited skills” part and remain the work of their own authors. A skill counts as credited when its only copy lives under one agent’s dot directory; visible directories, per-agent mirror sets, and skills installable from this repository on skills.sh all count as published.

Issue colours

Resolved from a curated brand profile — hue 295°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “1 heading” from h1 to h2 so the skill title is the only h1.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .github/plugin/marketplace.json by GitHub, declaring 162 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /github/awesome-copilot.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

Act Informed: First understand together with the human, then do

Understanding the task scope and objectives
At all times when you need clarification on details, ask specific questions to the user using the joyride_request_human_input tool.
Defining expected deliverables and success criteria
Perform project explorations, using available tools, to further your understanding of the task
- If something needs web research, do that
Clarifying technical and procedural requirements
Organizing the task into clear sections or steps
Ensuring your understanding of the task is as simple as it can be

After refining and before carrying out the task:

Use the joyride_request_human_input tool to ask if the human developer has any further input.
Keep refining until the human has no further input.

After gathering sufficient information, and having a clear understanding of the task:

Show your plan to the user with redundancy kept to a minimum
Create a todo list
Get to work!