CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-functions

Dev/test workflow for tracer engineers working on the Datadog .NET tracer — build a local Datadog.AzureFunctions NuGet package, deploy it to a test Azure Function App, trigger it, and analyze traces/logs to verify instrumentation behavior. Use this skill whenever the user is working on Azure Functions instrumentation: building or testing the Datadog.AzureFunctions NuGet package, deploying to a test Function App, analyzing instrumentation logs or spans from an Azure Functions app, or configuring Datadog environment variables on Azure — even if they don't explicitly invoke /azure-functions.

69

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

A highly actionable, well-sequenced skill body with strong validation checkpoints and troubleshooting feedback loops. The main weaknesses are token redundancy in repeated command invocations and referenced sibling documents that are not present in the bundle.

Suggestions

Consolidate the repeated Deploy-AzureFunction.ps1 invocations: show the full command once in step 2 and reference it from step 5's pipeline-usage example instead of restating it verbatim.

Add the missing referenced files (environment-variables.md, scripts-reference.md, log-analysis-guide.md) to the skill bundle, or remove the links and inline only the essential variables/parameters the workflow actually needs.

Trim the 'What this does' prose blocks for the wrapper scripts to one-line summaries, since the script behavior is verifiable by reading the scripts themselves.

DimensionReasoningScore

Conciseness

Mostly efficient and actionable, but repeats the full Deploy-AzureFunction.ps1 invocation across steps 2 and 5 and includes several 'What this does' prose blocks that could be tightened or deferred to the scripts themselves.

3 / 5

Actionability

Provides copy-paste-ready PowerShell and Azure CLI commands with concrete parameters throughout every workflow step and troubleshooting section.

5 / 5

Workflow Clarity

A clear five-step sequence with explicit prerequisite verification (nuget.config, env vars), a dedicated verification checklist, and troubleshooting feedback loops for error recovery.

5 / 5

Progressive Disclosure

Well-signaled one-level-deep references to environment-variables.md, scripts-reference.md, and log-analysis-guide.md, but those sibling files are absent from the skill bundle and the main body is long with substantial inlined detail.

4 / 5

Total

17

/

20

Passed

Description

92%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.

A strong, specific description that clearly states both the workflow it performs and when to use it, with concrete trigger phrases and a well-scoped niche. The only minor gap is a lack of synonym variety in the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'build a local Datadog.AzureFunctions NuGet package, deploy it to a test Azure Function App, trigger it, and analyze traces/logs' — giving comprehensive coverage of the workflow.

5 / 5

Completeness

Explicitly answers both 'what' (build/deploy/trigger/analyze) and 'when' ('Use this skill whenever the user is working on Azure Functions instrumentation...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural keywords ('Azure Functions instrumentation', 'deploying to a test Function App', 'analyzing instrumentation logs or spans', 'configuring Datadog environment variables on Azure') with good coverage, but light on synonyms and phrasing variants.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche — Datadog .NET tracer instrumentation on Azure Functions — with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 7 missing

Warning

Total

13

/

16

Passed

Repository
DataDog/dd-trace-dotnet
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.