Skill Seekers Builder
yusufkaraaslan/Skill_Seekers
Detects the type of a knowledge source and uses the Skill Seekers MCP tools to turn docs, repos, PDFs or videos into packaged AI skills.
Validate that Copilot CLI can see all repo skills, MCP servers, and custom instructions.
Install Testing CLI Compatibility
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill testing-cli-compatibility -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp testing-cli-compatibility --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/testing-cli-compatibility .claude/skills/testing-cli-compatibility && rm -rf skills-srcUse ~/.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/
Install the "testing-cli-compatibility" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/testing-cli-compatibility into .claude/skills/testing-cli-compatibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-cli-compatibility", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/testing-cli-compatibilityType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill testing-cli-compatibility -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp testing-cli-compatibility --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/testing-cli-compatibility .agents/skills/testing-cli-compatibility && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "testing-cli-compatibility" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/testing-cli-compatibility into .agents/skills/testing-cli-compatibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-cli-compatibility", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill testing-cli-compatibility -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp testing-cli-compatibility --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/testing-cli-compatibility .cursor/skills/testing-cli-compatibility && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "testing-cli-compatibility" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/testing-cli-compatibility into .cursor/skills/testing-cli-compatibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-cli-compatibility", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/microsoft-foundry/foundry-agent-webapp.git --path .github/skills/testing-cli-compatibility--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill testing-cli-compatibility -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp testing-cli-compatibility --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/testing-cli-compatibility .gemini/skills/testing-cli-compatibility && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "testing-cli-compatibility" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/testing-cli-compatibility into .gemini/skills/testing-cli-compatibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-cli-compatibility", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install microsoft-foundry/foundry-agent-webapp testing-cli-compatibilityInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill testing-cli-compatibility -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/testing-cli-compatibility .github/skills/testing-cli-compatibility && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "testing-cli-compatibility" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/testing-cli-compatibility into .github/skills/testing-cli-compatibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-cli-compatibility", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill testing-cli-compatibility -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp testing-cli-compatibility --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/testing-cli-compatibility .opencode/skills/testing-cli-compatibility && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "testing-cli-compatibility" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/testing-cli-compatibility into .opencode/skills/testing-cli-compatibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-cli-compatibility", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
testing-cli-compatibility- GitHub stars
- 127
- Token cost
- ~736 tokens
- SKILL.md length
- 272 words
- Files
- 1
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- MIT
At a glance
Validate that Copilot CLI can see all repo skills, MCP servers, and custom instructions.
- Works in 3 steps: Copilot CLI installed: npm install -g… → Authenticated: Run copilot login if not… → MCP servers synced: Run the…
- Setting up CLI for the first time
- SKILL.md covers Quick Start, What It Tests, Prerequisites and How It Works, plus 3 more sections
- Calls npm
What it does
Testing CLI Compatibility is an agent skill from microsoft-foundry/foundry-agent-webapp. Validate that Copilot CLI can see all repo skills, MCP servers, and custom instructions. Use when setting up CLI for the first time, after adding skills, or to diagnose CLI issues.
Its SKILL.md is about 740 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 Agent Workflows, covering MCP servers. It works with Model Context Protocol and GitHub. The repository describes itself as: GitHub Copilot enabled repo for building and deploying a web application with Entra ID authentication and integrated with Azure AI Foundry Agents. The licence is MIT.
When your agent uses it
- Setting up CLI for the first time
- After adding skills
- Diagnose CLI issues
Example prompts
- “/testing-cli-compatibility”
Requirements
- Node.js
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Copilot CLI installed: npm install -g @anthropic-ai/copilot-cli or via GitHub
- Authenticated: Run copilot login if not already logged in
- MCP servers synced: Run the syncing-mcp-servers skill first if MCP tests fail
What it can do on your machine
Read from SKILL.md and the folder at commit f6cb362. 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:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.github.com
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
Testing CLI Compatibility loads about 736 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 272 words of instructions outside code blocks.
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-foundry/foundry-agent-webapp at commit f6cb362, republished under its MIT licence (© microsoft-foundry). 272 words, ~736 tokens.
Download SKILL.mdSave it as
.claude/skills/testing-cli-compatibility/SKILL.md (or your agent's skills folder).- name
- testing-cli-compatibility
- description
- Validate that Copilot CLI can see all repo skills, MCP servers, and custom instructions. Use when setting up CLI for the first time, after adding skills, or to diagnose CLI issues.
Testing CLI Compatibility
Validates that the standalone Copilot CLI works correctly with this repo's skills and MCP servers.
Quick Start
# Run all tests (including MCP)
./deployment/scripts/test-cli-compatibility.ps1
# Skip MCP server tests (faster, no tool approval needed)
./deployment/scripts/test-cli-compatibility.ps1 -SkipMcpWhat It Tests
| # | Test | What It Checks |
|---|---|---|
| 1 | CLI Version | copilot command is installed and responds |
| 2 | Custom Instructions | .github/copilot-instructions.md is loaded (identifies project name) |
| 3 | Skills | All .github/skills/*/SKILL.md files are visible (count auto-detected) |
| 4 | MCP Servers | playwright and microsoftdocs servers are connected |
Prerequisites
- Copilot CLI installed:
npm install -g @anthropic-ai/copilot-clior via GitHub - Authenticated: Run
copilot loginif not already logged in - MCP servers synced: Run the
syncing-mcp-serversskill first if MCP tests fail
How It Works
The script uses copilot -p "<prompt>" -s --no-auto-update to invoke the CLI in non-interactive mode:
-p— Single prompt, exits after response-s— Silent mode, output only the agent response (no stats)--no-auto-update— Skip update check for faster execution--allow-all-tools— Used only for MCP test (needs tool access)
Each test sends a prompt asking the CLI to list what it can see, then validates the response against expected values.
When to Run
- After adding or modifying skills in
.github/skills/ - After syncing MCP servers with the
syncing-mcp-serversskill - When a user reports CLI issues (missing agents, skills, or tools)
- As a smoke test after CLI updates (
copilot update)
Manual Testing
If the script isn't available, you can test manually:
# Check version
copilot --version
# Test custom instructions
copilot -p "What project is this repo for?" -s
# Test skills
copilot -p "List all custom skills" -s
# Test MCP (needs --allow-all-tools)
copilot -p "List all MCP servers" -s --allow-all-toolsTroubleshooting
| Issue | Fix |
|---|---|
copilot not found | Install CLI or add to PATH |
| Custom instructions not loaded | Ensure you're in the repo directory |
| Agents missing | No custom agents expected — this repo uses skills + copilot-instructions only |
| Skills missing | Check .github/skills/*/SKILL.md files exist with valid frontmatter |
| MCP servers not connected | Run syncing-mcp-servers skill to sync .vscode/mcp.json → ~/.copilot/mcp-config.json |
© microsoft-foundry, 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/testing-cli-compatibility of microsoft-foundry/foundry-agent-webapp.
Open the folder on GitHubat commit f6cb362
Compare with similar skills
Testing CLI Compatibility 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Testing CLI Compatibility this skillmicrosoft-foundry/foundry-agent-webapp | 127 | — | ~736 | Automated safety check: Pass | MIT | |
| Skill Seekers Builderyusufkaraaslan/Skill_Seekers | 15k | — | ~760 | Automated safety check: Pass | MIT | |
| MCP Apps Builderawslabs/cli-agent-orchestrator | 1.4k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Releasejgravelle/jcodemunch-mcp | 2.7k | — | ~6.5k | Automated safety check: Pass | Custom licence | |
| Open PRArcadeAI/arcade-mcp | 1k | — | ~2.9k | Automated safety check: Pass | MIT | |
| MCP Clientcoleam00/second-brain-skills | 832 | — | ~1k | Automated safety check: Pass | None |
Similar skills
- Official
MCP Apps Builder
awslabs/cli-agent-orchestrator
Load the official MCP Apps builder skills (create-mcp-app, migrate-oai-app, add-app-to-server, convert-web-app) from github.com/modelcontextprotocol/ext-apps.
Release
jgravelle/jcodemunch-mcp
Publishing a jMunch release (jcodemunch-mcp, jdocmunch-mcp, jdatamunch-mcp, jragmunch-cli), reviewing/merging/closing PRs, and responding to the community.
Open PR
ArcadeAI/arcade-mcp
Prepare arcade-mcp changes for review by verifying intended behavior, filling the repository PR template, and creating or updating the PR.
MCP Client
coleam00/second-brain-skills
Universal MCP client for connecting to any MCP server with progressive disclosure.
Project Release
swimmwatch/cloakbrowser-mcp
Prepare, publish, verify, or recover a cloakbrowser-mcp release only when the user explicitly requests release work.
More from microsoft-foundry/foundry-agent-webapp
All 19 skills in this repoCommitting Code
microsoft-foundry/foundry-agent-webapp
Provides commit message format and workflow for this repository.
Implementing Chat Streaming
microsoft-foundry/foundry-agent-webapp
Provides SSE streaming patterns for the chat API and frontend.
Planning Features
microsoft-foundry/foundry-agent-webapp
Provides structured plan template for feature implementation.
Researching Azure AI SDK
microsoft-foundry/foundry-agent-webapp
Provides research patterns for Foundry Agent Service SDK. An agent skill from microsoft-foundry/foundry-agent-webapp.
Deploying To Azure
microsoft-foundry/foundry-agent-webapp
Provides deployment commands and troubleshooting for Azure Container Apps.
Syncing MCP Servers
microsoft-foundry/foundry-agent-webapp
Synchronize MCP server configuration between VS Code (.vscode/mcp.json) and Copilot CLI (~/.copilot/mcp-config.json).
Related
Works with
Categories
Questions about Testing CLI Compatibility
What does Testing CLI Compatibility do?
Validate that Copilot CLI can see all repo skills, MCP servers, and custom instructions. Testing CLI Compatibility is an agent skill from microsoft-foundry/foundry-agent-webapp. Validate that Copilot CLI can see all repo skills, MCP servers, and custom instructions.
When should I use Testing CLI Compatibility?
Testing CLI Compatibility fits situations like: setting up CLI for the first time; after adding skills; diagnose CLI issues.
How do I install Testing CLI Compatibility in Claude Code?
Run `npx skills add microsoft-foundry/foundry-agent-webapp --skill testing-cli-compatibility -a claude-code`. Or copy the skill folder (.github/skills/testing-cli-compatibility in microsoft-foundry/foundry-agent-webapp) into .claude/skills/testing-cli-compatibility in your project. Claude Code loads it when a task matches its description.
How do I install Testing CLI Compatibility in Codex?
Run `npx skills add microsoft-foundry/foundry-agent-webapp --skill testing-cli-compatibility -a codex`. Or copy the skill folder (.github/skills/testing-cli-compatibility in microsoft-foundry/foundry-agent-webapp) into .agents/skills/testing-cli-compatibility in your project. Codex loads it when a task matches its description.
Can I use Testing CLI Compatibility 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-foundry/foundry-agent-webapp --skill testing-cli-compatibility -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing-cli-compatibility, .gemini/skills/testing-cli-compatibility, .github/skills/testing-cli-compatibility and .opencode/skills/testing-cli-compatibility in your project.
What does Testing CLI Compatibility need to run?
Going by SKILL.md and its folder, Testing CLI Compatibility needs the command-line tools its instructions call (npm). Our summary lists: Node.js.
Does Testing CLI Compatibility access the network?
SKILL.md names 1 domain. As links in the text: docs.github.com. This is read from the text; nothing was executed.
Is Testing CLI Compatibility 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 Testing CLI Compatibility use?
Testing CLI Compatibility 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 Testing CLI Compatibility use?
About 736 tokens (SKILL.md is roughly 2.9k 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 Testing CLI Compatibility?
Skills that share tags, products or a category with Testing CLI Compatibility: Skill Seekers Builder (yusufkaraaslan/Skill_Seekers, 15k stars), MCP Apps Builder (awslabs/cli-agent-orchestrator, 1.4k stars), Release (jgravelle/jcodemunch-mcp, 2.7k stars) and Open PR (ArcadeAI/arcade-mcp, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Testing CLI Compatibility?
microsoft-foundry (a GitHub organization) maintains it in microsoft-foundry/foundry-agent-webapp, which has 127 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on April 21, 2026.
Source: microsoft-foundry/foundry-agent-webapp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.