CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

73%

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 content is actionable and self-contained, with real code examples, concrete paths, and an explicit validation loop for the snippet script. Its weaknesses are a typo-ridden, redundant opening paragraph, a missing example of the .md output format, and a flawed script invocation (wrong parameter name and a bash block that cannot run a .ps1 with backslashes).

Suggestions

Replace the run-on opening paragraph with a short bulleted list of the four parameters and the repository layout, removing duplication with the frontmatter.

Add a small example of the expected generated .md file (front matter, code block includes, per-block explanations) so the output format is unambiguous.

Fix the verification commands: use '<package_name>' instead of '<package>', and correct or remove the bash variant since 'eng\\scripts\\Update-Snippets.ps1' cannot be run directly from bash; also fix typos ('tro be', 'the sample provided sample', 'This skill require').

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and its examples are relevant, but the opening paragraph is a garbled run-on that duplicates the frontmatter parameters ('This skill require four inputs... the sample to be processed. the C# package name.'), and the sync/async C# examples are near-duplicates differing by only two lines. It fits anchor 3 ('could be tightened') better than 4, which allows only minor trims.

3 / 5

Actionability

Provides concrete, executable guidance: real C# code for sync and async variants, exact repository paths, the '#region Snippet:' marking convention with an example, and a runnable validation script. Not 5 because no example or template of the generated .md file is given, and the script invocation contains a parameter bug ('ai\<package>' instead of 'ai\<package_name>') plus a bash block that invokes a .ps1 script with Windows path separators.

4 / 5

Workflow Clarity

The sequence is discernible (analyze sample, write C# sample with sync and async variants, split into region blocks, write the .md with explanations, run Update-Snippets.ps1, iterate) and an explicit validation feedback loop exists ('If there are errors, please iterate over it until the script will complete without errors'). Not 5 because steps are not explicitly enumerated, the ordering of .md generation vs. script validation is implicit, and the .md output format is underspecified.

4 / 5

Progressive Disclosure

The skill is self-contained with no bundle files, uses section headers, and keeps inline examples at an appropriate scale for an ~80-line skill. It matches anchor 4 ('good structure, minor organization gaps') rather than 5, since headers like '# Basic information' are loose and the parameter/layout information is an unstructured run-on rather than an organized list.

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 is highly distinctive and specific to its niche, with a clear statement of what the skill does and well-documented parameters. Its main weaknesses are the complete absence of a 'Use when...' trigger clause, missing natural synonyms such as 'port'/'convert', and a typo ('markdownn').

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to translate, port, or convert an Azure SDK sample from Python to C#, or to generate the markdown sample documentation.'

Include natural synonyms users would say ('port', 'convert', 'migrate') alongside 'translate' to broaden trigger coverage.

Fix the 'markdownn' typo and use consistent phrasing for parameter descriptions.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions ('Translate the Azure SDK sample from python to C# and generate markdownn file') plus enumerated parameters, but coverage is not comprehensive (no mention of sync/async generation or snippet validation). This matches anchor 3 ('1-2 concrete actions, but not comprehensive') rather than 4, which requires several specific actions.

3 / 5

Completeness

The 'what' is clear (translate a Python sample to C# and generate a markdown file), but there is no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the judging guidelines. Not 4 because 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'Translate', 'python to C#', 'Azure SDK sample', 'markdown', and concrete package names (Azure.AI.Projects, Azure.AI.Projects.Agents, Azure.AI.Extensions.OpenAI) users would plausibly say. Not 5 because synonyms like 'port' or 'convert' are missing and 'markdownn' is a typo.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche — translating Azure SDK Python samples to C# for three named packages — with distinct triggers and virtually no overlap risk with other skills, matching anchor 5.

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

Path

sdk/ai/.github/skills/azure-ai-projects-sample-skill/SKILL.md

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.