CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

author-test

Generate a test given sample. Parameters: <cs_root> C# SDK repository root; <package_name> Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; <sample_name> the sample to use as a starting point for the test.

58

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-author-tests/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 is a tight, actionable instruction sheet: it locates the inputs, prescribes the test structure, and closes with a build-verification loop. Its weaknesses are small — a duplicated build block, a vague "iterate on the error" instruction, and no worked example of a real generated test.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence, but contains minor waste: the identical `dotnet build` block duplicated in both powershell and bash fences, and the garbled sentence "The files, having suffix Base contains the required utility functions". Not 5 because of that duplication; not 3 because nearly every other token earns its place.

4 / 5

Actionability

Concrete directory paths, an explicit test-structure template, and copy-paste build commands make the guidance mostly executable. Minor gaps keep it below 5: the template is placeholder-based with no concrete real example, and the Base utility files are mentioned but never shown how to be used.

4 / 5

Workflow Clarity

A clear sequence is present (inspect sample → write test in the appropriate file → build → iterate on errors) with an explicit build validation step. Below 5 because the feedback loop "iterate on the error" is underspecified (no fix-and-rebuild instruction) and there is no step to actually run the test.

4 / 5

Progressive Disclosure

This is a single-purpose skill well under 50 lines with no need for external references, and its two sections ("Basic information", "Task") are well organized — meeting the rubric's simple-skill exception for a top progressive-disclosure score.

5 / 5

Total

17

/

20

Passed

Description

53%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 gives a clear, parameterized statement of what the skill does and is well-scoped to specific Azure SDK packages, but it entirely lacks any indication of when the skill should be invoked. Adding an explicit trigger clause and natural trigger phrases would materially improve it.

Suggestions

Add a 'Use when...' clause (e.g., "Use when the user asks to create, write, or generate a test for the Azure SDK for .NET, or to turn a sample into a recorded test") to raise completeness above the cap of 3.

Include natural trigger terms and synonyms users would actually say — "write a test", "add a test", "unit test", "recorded test" — alongside the existing technical terms.

State the concrete actions more comprehensively (e.g., locates the matching test file, reuses Base utility functions, builds the project to verify) rather than the single action "Generate a test given sample".

DimensionReasoningScore

Specificity

The description names one concrete action ("Generate a test given sample") with concrete parameters, but does not enumerate multiple specific capabilities. It matches the anchor 'names domain and 1-2 concrete actions, but not comprehensive' rather than 4, which requires several listed actions.

3 / 5

Completeness

The "what" is clear (generate a test from a sample with given parameters), but there is no "when" — no 'Use when...' clause or trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Terms like "test", "sample", "C# SDK", and the Azure package names are relevant, but common natural variations ("write tests", "unit test", "test generation") are missing. It sits between the generic-keyword level and good coverage, fitting 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

Enumeration of specific packages (Azure.AI.Projects, Azure.AI.Projects.Agents, Azure.AI.Extensions.OpenAI) and the C# SDK context creates a distinct niche. Score is not 5 because the opening "Generate a test" phrase overlaps with generic test-generation skills; not 3 because the package constraints keep conflict risk minor.

4 / 5

Total

13

/

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-author-tests/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.