mcpbeat

Update Emitter

azure/update-emitter

Update the TypeSpec emitter for Rust and optionally regenerate all clients

235 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
883
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-rust --skill update-emitter

The instruction itself

2 sections, as written by the author

Run eng/scripts/Update-Emitter.ps1 to update eng/emitter-package.json to the latest @azure-tools/typespec-rust version and regenerate the lock file.

Regenerating clients

After updating the emitter, service crates should be regenerated to pick up the new version.

Service owners should regenerate only their own service crates. To regenerate a single crate, run tsp-client update from within the crate directory:

cd sdk/{service-directory}/{crate-directory}
tsp-client update

To regenerate all crates under a service directory:

find sdk/{service-directory} -name tsp-location.yaml -execdir tsp-client update \;

After regenerating

  • Build and test each affected crate to verify correctness.
  • Review any changes to public APIs and update each crate's CHANGELOG.md accordingly.

How to use it

Copy the folder

Take azure/update-emitter 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.