🎯 Prerequisites

Before you start, you need: - A coding agent installed (Copilot, Claude Code, Cursor, or Windsurf) - A project folder on your computer - Basic familiarity with command line or your agent's UI

💻 Setup Guide: Using Skills in Your Agent (For Beginners)

This guide walks you through setting up Agent Skills in your favorite coding agent, step by step.

📍 Step-by-Step Setup

Option 1: GitHub Copilot (Most Popular)

<details> <summary><strong>🟢 Setup GitHub Copilot with Skills</strong></summary>

For Project Skills (specific to one repository):

1. In your project folder, create the skills directory:

   mkdir -p .github/skills
   

2. Copy the skills you want from this repository:

   # Copy a single skill
   cp -r skills/vercel .github/skills/
   
   # Or copy all skills
   cp -r skills/* .github/skills/
   

3. Or manually create a skill:

   your-project/
   └── .github/
       └── skills/
           └── my-custom-skill/
               └── SKILL.md
   

1. Open your project in VS Code and start using Copilot Agent
2. Ask Copilot a question related to your skill, and it will automatically load it!

For Personal Skills (available across all your projects):

1. Find your home directory (~ or C:\Users\YourUsername)

2. Create personal skills folder:

   mkdir -p ~/.copilot/skills
   

3. Copy skills there:

   cp -r skills/vercel ~/.copilot/skills/
   

1. Now all your projects can use these skills automatically!

Verify it's working: - Open Copilot Agent - Ask about something covered in your skill (e.g., "How do I deploy to Vercel?") - Copilot will use the skill to help you

</details>

---

Option 2: Claude Code

<details> <summary><strong>🟣 Setup Claude Code with Skills</strong></summary>

For Project Skills:

1. In your project folder, create the skills directory:

   mkdir -p .claude/skills
   

2. Copy the skills you want:

   # Single skill
   cp -r skills/langchain .claude/skills/
   
   # All skills
   cp -r skills/* .claude/skills/
   

1. Open your project in Claude Code
2. Chat with Claude about tasks covered in your skills - it will automatically use them!

For Personal Skills (available everywhere):

1. Create personal skills folder:

   mkdir -p ~/.claude/skills
   

2. Copy skills there:

   cp -r skills/aws-agentcore ~/.claude/skills/
   

Verify it's working: - Open Claude Code in your project - Ask about something in your skill - Claude will reference and use the skill

</details>

---

Option 3: Cursor

<details> <summary><strong>🔵 Setup Cursor with Skills</strong></summary>

For Project Rules:

1. In your project folder:

   mkdir -p .cursor/rules
   

2. Copy SKILL.md files (rename them as rules):

   # Copy a skill as a rule file
   cp skills/figma/SKILL.md .cursor/rules/figma.md
   
   # Or copy multiple
   cp skills/*/SKILL.md .cursor/rules/
   

3. In Cursor Settings, configure which rules to use: - Settings → Rules → Add project rules - Point to .cursor/rules/ folder

1. Start using Cursor - it will apply these rules to your context automatically

</details>

---

Option 4: Windsurf

<details> <summary><strong>🟡 Setup Windsurf with Skills</strong></summary>

For Project Rules:

1. In your project folder:

   mkdir -p .windsurf/rules
   

2. Copy skills as rules:

   # Copy specific skills
   cp skills/vercel/SKILL.md .windsurf/rules/vercel.md
   
   # Or copy all skills
   cp skills/*/SKILL.md .windsurf/rules/
   

1. Windsurf automatically discovers rules in .windsurf/rules/
2. Start building - Windsurf will use these rules contextually

</details>

---

🎓 What Happens After Setup?

Once you've set up your skills:

1. Agent Detects Skills: Your AI agent scans the skill directories
2. Agent Reads SKILL.md: It reads the name and description from frontmatter
3. Agent Activates on Relevance: When you ask a question matching the description, the agent loads the skill
4. Agent Follows Instructions: Your agent now has the context to help you accurately

description: Deploying applications to Vercel. Use this when asked about deploying, hosting, or managing Vercel projects.

```

You ask your agent: > "Help me deploy my React app to Vercel"

Agent automatically: - ✅ Finds vercel-deployment skill - ✅ Loads SKILL.md into context - ✅ Follows the deployment instructions - ✅ Helps you deploy successfully!

Step 3: A Real Example

Here's what a simple SKILL.md looks like:

description: Guide for debugging failing GitHub Actions workflows. Use this when asked to debug CI/CD failures or workflow issues.

🚀 Quick Start

💡 Example: Using a Vercel Skill

You have this SKILL.md:

💻 Usage (Advanced)

---

Contribution Guidelines

• ✅ Include practical, production-ready code examples
• ✅ Add trigger keywords in the description
• ✅ Test all code snippets before submitting
• ✅ Keep explanations concise but complete
• ❌ Don't include basic concepts the AI already knows
• ❌ Don't use placeholder code or TODOs

---

🆕 NEW: Google Workspace CLI Skill

Just added! A comprehensive skill that teaches AI agents to use the gws CLI — one command-line tool for all of Google Workspace: Drive, Gmail, Calendar, Sheets, Docs, Slides, Chat, Tasks, Admin, Meet, Forms, Keep, and more. Your agent can now manage your entire Google Workspace without custom tooling.

🔗 View the Google Workspace CLI Skill →

What it does: - Enables AI agents to interact with every Google Workspace API via gws CLI commands - Covers Drive, Gmail, Calendar, Sheets, Docs, Slides, Chat, Tasks, Meet, Forms, Admin, Keep, Apps Script, and more - Includes 100+ ready-to-use command examples with real JSON payloads - MCP server integration for Claude Desktop, VS Code, Gemini CLI, and other MCP clients - Multiple auth workflows: interactive, headless/CI, service accounts, and multi-account support - Built on Google's Discovery Service — automatically picks up new API endpoints

---

Debugging GitHub Actions Workflows

When debugging a failing workflow:

1. Check the job logs - Look for error messages and stack traces
2. Review recent changes - What changed since the last successful run?
3. Test locally - Reproduce the issue in your local environment
4. Fix and validate - Make changes and verify they work

Issue: Workflow fails with "Command not found"

Solution: Install the required tool in your workflow step

🐛 Troubleshooting

---