mcpbeat

Test Proxy

azure/test-proxy

Push test-proxy recordings/assets using the test-proxy CLI (e.g., test-proxy push -a assets.json). Use when publishing recordings.

319 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
2566
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Azure/azure-sdk-for-java --skill test-proxy

The instruction itself

6 sections, as written by the author

Test Proxy Recordings

Use this skill to publish recordings to the test-proxy assets repo.

Command

test-proxy push -a assets.json

Steps

  • Check if test-proxy is installed by running test-proxy --version.
  • If the command is not found, install it (see Installation below).
  • Confirm the assets file path (default: assets.json in the current directory).
  • If the file location is unclear, search for it or ask the user.
  • Run test-proxy push -a <assets-file>.
  • Report success or any errors.

Installation

If test-proxy is missing, install it as a .NET global tool.

Prerequisites

.NET 8.0 (LTS) or later must be installed. Verify with dotnet --version.

If missing, ask the user to install the .NET SDK from https://dotnet.microsoft.com/download.

Install command

dotnet tool update azure.sdk.tools.testproxy --global --prerelease --add-source https://pkgs.dev.azure.com/azure-sdk/public/_packaging/azure-sdk-for-net/nuget/v3/index.json --ignore-failed-sources

After installation, verify with test-proxy --version.

How to use it

Copy the folder

Take azure/test-proxy from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.