The Agent Skills Directory

Use of Well-Known External Services: The skill fetches package information from the official NuGet API (api.nuget.org). This is a standard operation for dependency management and uses a well-known service domain.
Command Execution via Local Scripts: The skill utilizes a C# utility script (MigratePackage.cs) and shell commands to interact with Azure DevOps and perform builds. These tools are bundled with the skill and are used to automate internal development workflows.
Authentication via Established Tooling: The skill's C# script uses Azure.Identity to authenticate with Azure DevOps using the user's existing Azure CLI session. This follows security best practices for internal tooling by leveraging managed identities and local credentials rather than hardcoded secrets.
Indirect Prompt Injection Surface: The skill ingests data from nuget.org to determine available package versions. While this represents an external data entry point, the risk is mitigated by the use of structured JSON parsing and mandatory human confirmation before any significant actions, such as triggering pipelines, are taken.
Ingestion points: Fetches version metadata from api.nuget.org (SKILL.md).
Boundary markers: The instructions explicitly require the agent to present a summary table and use the ask_user tool for confirmation before proceeding.
Capability inventory: Ability to trigger Azure DevOps pipelines, modify repository configuration files, and execute build scripts.
Sanitization: External JSON data is processed using a Python script with standard library parsing logic, which limits the risk of raw content execution.
Interaction with Internal Infrastructure: The skill triggers pipelines in the dnceng Azure DevOps organization. This is a known infrastructure for Microsoft's .NET engineering teams and is consistent with the skill's stated purpose and author identity.

dependency-update