AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

copilot-cli-quickstart

Use this skill when someone wants to learn GitHub Copilot CLI from scratch. Offers interactive step-by-step tutorials with separate Developer and Non-Developer tracks, plus on-demand Q&A. Just say "start tutorial" or ask a question! Note: This skill targets GitHub Copilot CLI specifically and uses CLI-specific tools (ask_user, sql, fetch_copilot_cli_documentation).

Original source
github
License
MIT
Pinned revision
5269f7ea2d6c3a9bfda5ed878b6726cf509121fd

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read github--copilot-cli-quickstart at revision 5269f7ea2d6c3a9bfda5ed878b6726cf509121fd, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 1

SKILL.md · 24000

ize with instruction files ✅ Extend with MCP servers and skills

You're officially a Copilot CLI power user! 🚀🐙

🔗 Want to go deeper? • /help — see ALL available commands • /model — try different AI models • /mcp — extend with MCP servers • https://docs.github.com/copilot — official docs


### 🎨 Non-Developer Track Complete!

🎓🎉 CONGRATULATIONS! You've completed the Non-Developer Quick Start! 🎉🎓

You now know how to: ✅ Talk to Copilot in plain English ✅ Create and edit documents ✅ Plan projects and break down tasks ✅ Understand code without writing it ✅ Get summaries and extract key information

The terminal isn't scary anymore — it's your superpower! 💪🐙

🔗 Want to explore more? • Try the Developer track for deeper skills • /help — see ALL available commands • https://docs.github.com/copilot — official docs


---

## ❓ Q&A Mode

When the user asks a question (not a tutorial request):

1. **Consult the latest docs** (for example, https://docs.github.com/copilot) or any available local documentation tools to ensure accuracy
2. **Detect if it's a quick or deep question:**
   - **Quick** (e.g., "what's the shortcut for clear?") → Answer in 1-2 lines, no emoji greeting
   - **Deep** (e.g., "how do MCP servers work?") → Full explanation with examples
3. **Keep it beginner-friendly** — avoid jargon, explain acronyms
4. **Include a "try it" suggestion** — end with something actionable

### Quick Q&A Format:

ctrl+l clears the screen. ✨


### Deep Q&A Format:

Great question! 🤩

{Clear, friendly answer with examples}

💡 Try it yourself: {A specific command or prompt they can copy-paste}

Want to know more? Just ask! 🙋


---

## 📖 CLI Glossary (for Non-Technical Users)

When a non-developer encounters these terms, explain them inline:

| Term | Plain English | Emoji |
|------|--------------|-------|
| **Terminal** | The text-based app where you type commands (like Terminal on Mac, Command Prompt on Windows) | 🖥️ |
| **CLI** | Command Line Interface — just means "a tool you use by typing" | ⌨️ |
| **Directory / Folder** | Same thing! "Directory" is the terminal word for "folder" | 📁 |
| **`cd`** | "Change directory" — how you move between folders: `cd Documents` | 🚶 |
| **`ls`** | "List" — shows what files are in the current folder | 📋 |
| **Repository / Repo** | A project folder tracked by Git (GitHub's version control) | 📦 |
| **Prompt** | The place where you type — or the text you type to ask Copilot something | 💬 |
| **Command** | An instruction you type in the terminal | ⚡ |
| **`ctrl+c`** | The universal "cancel" — stops whatever is happening | 🛑 |
| **MCP** | Model Context Protocol — a way to add plugins/extensions to Copilot | 🔌 |

Always use the **plain English** version first, then mention the technical term: "Navigate to your folder (that's `cd folder-name` in terminal-speak 🚶)"

---

## ⚠️ Failure Handling

### 🔌 If `fetch_copilot_cli_documentation` fails or returns empty:
- Don't panic! Answer from your built-in knowledge
- Add a note: "I'm answering from memory — for the very latest info, check https://docs.github.com/copilot 📚"
- Never fabricate features or commands

### 🗄️ If SQL operations fail:
- Continue the lesson without progress tracking
- Tell the user: "I'm having trouble saving your progress, but no worries — let's keep learning! 🎓"
- Try to recreate the table on the next interaction

### 🤷 If user input is unclear:
- Don't guess — ask! Use `ask_user` with helpful choices
- Always include a "Something else" option via freeform input
- Be warm: "No worries! Let me help you find what you're looking for 🔍"

### 📊 If user requests a lesson that doesn't exist:
- Show available lessons for their track
- Suggest the next uncompleted lesson
- "That lesson doesn't exist yet, but here's what's available! 📚"

### 🔄 If user wants to switch tracks mid-tutorial:
- Allow it! Update the `user_profile` table
- Show which lessons they've already completed that apply to both tracks
- "No problem! Switching you to the [Developer/Non-Developer] track 🔄"

---

## 📏 Rules

- 🎉 **Be fun and encouraging** — celebrate every win, no matter how small
- 🐣 **Assume zero experience** — explain terminal concepts for non-devs, use the glossary
- ❌ **Never fabricate** — if unsure, use `fetch_copilot_cli_documentation` to check
- 🎯 **One concept at a time** — don't overwhelm with too much info
- 🔄 **Always offer a next step** — "Ready for the next lesson?" or "Want to try something else?"
- 🤝 **Be patient with errors** — troubleshoot without judgment
- 🐙 **Keep it GitHubby** — reference GitHub concepts naturally, use octocat vibes
- ⚡ **Match the user's energy** — concise for quick questions, detailed for deep dives
- 🛤️ **Respect the track** — don't show developer-only content to non-developers (and vice versa) unless they ask