CtrlK
BlogDocsLog inGet started
Tessl Logo

translate-a-sample

Translate the Azure SDK sample from python to C# and generate markdownn file for the sample. Parameters: <cs_root> C# SDK repository root; <python_root> python SDK repository root; <package_name> Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; <sample_name> The name of sample file in Python SDK repository.

58

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./sdk/ai/.github/skills/azure-ai-projects-sample-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers concrete, executable guidance with a useful validation feedback loop and clear sections, but is held back by parameter restatement, near-duplicate sync/async blocks, and a prose rather than numbered workflow.

Suggestions

Collapse the near-identical sync and async C# examples into one block with a note on the await/async difference to reduce redundancy and raise conciseness.

Number the workflow steps explicitly (analyze -> generate -> split into regions -> run Update-Snippets.ps1 -> iterate until clean) with validation checkpoints to push workflow clarity toward 5.

Stop restating the four input parameters in the Basic information section since they are already in the frontmatter description, or vice versa.

DimensionReasoningScore

Conciseness

The body is mostly efficient and action-oriented, but restates the four input parameters already given in the description and includes near-identical sync/async C# blocks, which could be tightened. It is above the verbose anchor of 2 but not lean enough for 4 given this redundancy.

3 / 5

Actionability

Provides executable C# examples, a concrete #region snippet format, and specific validation commands ('eng\scripts\Update-Snippets.ps1 ai\<package>'). Minor gaps (the exact .md layout is described only abstractly, and a .ps1 script appears in a bash block) keep it just below the fully copy-paste-ready anchor of 5.

4 / 5

Workflow Clarity

The flow is analyzable — analyze sample, generate C# + .md, split into snippet regions, run Update-Snippets.ps1, and iterate until no errors — and includes an explicit validation/feedback loop. It is not 5 because the sequence is prose rather than crisply numbered checkpoints with clear preconditions.

4 / 5

Progressive Disclosure

The content is self-contained with clear section headers (Basic information, Instruction, Asynchronous/Synchronous Sample) and no external references are needed. It is well-organized but slightly over 50 lines with inline code that could be separated, so it sits at 'good structure' rather than the ideal 5.

4 / 5

Total

15

/

20

Passed

Description

65%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states a specific, distinctive task and names concrete parameters, but lacks an explicit 'Use when...' trigger clause and has a typo ('markdownn'), which together cap completeness and slightly diminish polish.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when porting an Azure AI Projects Python sample to the C# SDK and its markdown docs') to raise completeness above 3.

Include 1-2 more concrete actions or synonyms (e.g., 'port/convert', 'split code into snippet regions') to broaden trigger term coverage and specificity.

Fix the typo 'markdownn' -> 'markdown'.

DimensionReasoningScore

Specificity

Names the domain (Azure SDK sample, python to C#) and two concrete actions — 'Translate the Azure SDK sample from python to C#' and 'generate markdownn file for the sample' — but coverage is not comprehensive (no mention of sync/async handling or block structure). It fits the 1-2 concrete actions anchor and is not the level above, which requires several specific actions.

3 / 5

Completeness

The 'what' is clear (translate a sample and generate a markdown file), but there is no 'Use when...' clause or equivalent explicit trigger guidance; the 'when' is only weakly implied. Per the guidelines, a missing explicit trigger clause caps completeness at 3, so it cannot reach 4.

3 / 5

Trigger Term Quality

Natural phrases a user would say are present ('Translate the Azure SDK sample from python to C#', 'markdown'), with good coverage of the core terms. Missing synonyms like 'port', 'convert', or 'migrate', so it falls just below the comprehensive-coverage anchor of 5.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear, narrow niche (translating Azure SDK samples from Python to C# with a markdown companion) with distinct triggers and minimal overlap with other skills, matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Azure/azure-sdk-for-net
Reviewed

Table of Contents

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.