CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

connect-observability

Find or connect an Azure application's or Foundry agent's telemetry for an explicit observability, monitoring, alerting, health or operational diagnosis request. Confirm source scope and task-specific telemetry access; not generic app connection, resource creation or deployment readiness. Instrumentation/collection design can precede deployment; answer conceptual questions directly. No automatic provisioning or changes.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is connect-observability in microsoft/GitHub-Copilot-for-Azure

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 a clearly sequenced, validation-heavy read-only workflow with executable helper commands and well-organized deferred references. Its weaknesses are redundancy — approval-boundary and anti-fabrication rules are restated in most sections — and the absence of inline examples for the central telemetry queries and helper input formats.

Suggestions

Consolidate the approval-boundary rules (separate approvals for installation, connections, sign-in, writes; preserve declines) into one dedicated section, and reference it from the workflow steps instead of restating it in nearly every section.

Add one small inline example of a signal-labeled bounded query (e.g. the `Signal='requests'` vs `Signal='dependencies'` pattern) and a minimal assess-input snippet, or state explicitly in SKILL.md where their formats are defined, to make step 3 immediately executable.

Trim the dense negation chains in the two opening gates (e.g. the availability gate) to the distinct rules, since several sentences restate the same fallback behavior.

DimensionReasoningScore

Conciseness

There is no re-teaching of concepts Claude already knows, but the body repeats the same approval-boundary rules across nearly every section ("New connections, reads and writes keep separate approvals", "Installation, connections, sign-in and writes need separate approvals", "New specialist steps retain existing approval boundaries") and stacks dense negation chains that could be consolidated. Mostly efficient with noticeable tightening possible, matching anchor 3 rather than the 'minor instances' of level 4.

3 / 5

Actionability

The helper command block is fully executable ("python \"<skill-directory>\\scripts\\onboarding.py\" validate \"<mapping-input.json>\"" with flags like --consent and --replace documented), and guidance includes enumerated signal states and explicit bounds (one initial query per declared signal, one correction). Key details are still missing inline — no example telemetry query and no example assess/mapping input format — keeping it at 'mostly executable guidance with minor gaps' rather than copy-paste-ready coverage of the common cases.

4 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced (intent -> scope -> readiness -> report -> retain/hand off) with explicit validation checkpoints (revalidate saved mappings through tools, match each count to its labeled query result, one-correction rule per schema error, report invalid saved files) and error-recovery loops ("disclose the conflict and reconcile with retained query/output or one approved bounded recheck"). Step 4 provides a concrete reporting checklist and an INCONCLUSIVE fallback path; the workflow is read-only so no destructive-operation cap applies.

5 / 5

Progressive Disclosure

SKILL.md works as an overview with well-signaled, purpose-stated references (contract, tools, routing, journey-indicator — all verified to exist in references/), each introduced with clear link text and when to read it. However, the bundle chains two levels deep: routing.md links into shared/specialists.md, shared/next-actions.md and shared/trace-capabilities.md, and tools.md links into vscode-setup.md and cli-setup.md, so references are not strictly one level deep as required for the top anchor.

4 / 5

Total

16

/

20

Passed

Description

82%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 description with explicit what/when coverage, natural trigger terms, and deliberate boundary exclusions that minimize conflict with adjacent skills. Its main weakness is specificity: the capability verbs (find, connect, confirm) stay abstract instead of naming the concrete telemetry signals (logs, metrics, traces) the skill actually works with.

DimensionReasoningScore

Specificity

The description names the domain ("Azure application's or Foundry agent's telemetry") and a couple of actions ("Find or connect", "Confirm source scope and task-specific telemetry access"), but the actions remain at an abstract verb level without concrete signal operations such as reading logs, metrics, or traces. This matches the anchor for naming a domain with 1-2 concrete actions rather than the several specific concrete actions of level 4.

3 / 5

Completeness

It explicitly answers both what ("Find or connect an Azure application's or Foundry agent's telemetry... Confirm source scope and task-specific telemetry access") and when, with concrete trigger phrases ("for an explicit observability, monitoring, alerting, health or operational diagnosis request") plus scope clarifications ("Instrumentation/collection design can precede deployment; answer conceptual questions directly"). Both elements are explicit with concrete triggers, matching the top anchor.

5 / 5

Trigger Term Quality

Natural trigger phrases are well covered: "observability, monitoring, alerting, health or operational diagnosis request" plus "telemetry" — terms users would actually say. A few common variations are missing (logs, metrics, traces, Application Insights, "my API is slow"-style phrasing), which fits the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive-synonym level 5.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (Azure/Foundry telemetry connection for observability requests) and actively reduces conflict risk with explicit exclusions: "not generic app connection, resource creation or deployment readiness" and "No automatic provisioning or changes." This gives minimal overlap risk with adjacent deployment or general-Azure skills, matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

microsoft/azure-skills

Path

.github/plugins/azure-observability/skills/connect-observability/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.