dpg-migration
Migration logic for Azure SDK for .NET data-plane libraries migrating from AutoRest/Swagger to TypeSpec-based generation. Uses MCP tools from the generator-agent server for automated deterministic fixes.
61
72%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.github/skills/dpg-migration/SKILL.mdLow
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The required workflow uses the `discover_project` MCP tool to read project/spec context from the SDK repo and local spec checkout (incl. `src/autorest.md` and `*.tsp` files) and feed that information into the agent/LLM context; since those spec/customization files can be authored by outsiders (e.g., upstream `azure-rest-api-specs` repo), this creates an indirect prompt-injection path via runtime ingestion of outsider-authored free-form text.
- Repository
- Azure/azure-sdk-for-net
- Commit
0afb185
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.