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

73%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/azure-observability/skills/connect-observability/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

48%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 skill has a genuinely well-sequenced five-stage workflow with strong validation checkpoints and feedback loops, and its helper commands are executable, but it is buried in dense, repetitive policy prose that wastes tokens and obscures the main path. Actionability suffers from missing input-format examples, and the bundle's deep, partially unlinked shared/ tree weakens an otherwise good progressive-disclosure design.

Suggestions

Consolidate the repeated approval-boundary rules (separate approvals for connections/reads/writes/installation appear six-plus times) into one 'Approval boundaries' section and reference it once, cutting substantial token overhead in the conciseness dimension.

Add a minimal example of the helper's mapping-input and assessment-input JSON in the 'Local helper' section, plus one sample bounded metadata/telemetry query, so the executable commands have concrete inputs to run against.

Either link the references/shared/ files (specialists.md, next-actions.md, matching.md, trace-capabilities.md, etc.) from SKILL.md or from the top-level references they support, and flatten the shared/investigation/ nesting so no content sits more than one reference level below the files SKILL.md points to.

DimensionReasoningScore

Conciseness

The body is noticeably verbose through redundant policy repetition rather than concept explanation: separate-approval rules recur in at least six places ('New connections, reads and writes keep separate approvals', 'Installation, connections, sign-in and writes need separate approvals', 'Runtime installation requires separate approval'), and nearly every step is wrapped in multi-clause prohibitions ('never silently ignore or replace it', 'do not repeatedly rediscover the same catalog'). It does not explain concepts Claude already knows, which keeps it above the anchor at 1, but the duplicated guardrails and legalese density mean many tokens do not earn their place.

2 / 5

Actionability

There is some genuinely concrete guidance — the four executable helper commands (`python "<skill-directory>\scripts\onboarding.py" validate/assess/save/load`) and the structured report checklist in section 4 — but the bulk of the workflow is abstract direction such as 'Agree the core signals needed for this task' and 'Confirm the environment and app-to-source associations' with no example of a mapping input, an assessment input, or a bounded telemetry query. The commands are copy-paste ready yet their required inputs are never shown, which is a key gap rather than a minor one.

3 / 5

Workflow Clarity

The five numbered stages (establish intent, resolve scope, prove readiness, return, retain/hand off) form a clear sequence with explicit validation checkpoints — 'inspect API completeness and truncation, not just HTTP success', 'match each count and timestamp to its labeled query result' — and genuine feedback loops ('one correction for a concrete schema/syntax error', 'reconcile with retained query/output or one approved bounded recheck'). It falls short of 5 because the sheer density of interleaved caveats within each step obscures the main path, making the effective sequence harder to follow than the section headers suggest.

4 / 5

Progressive Disclosure

The body appropriately pushes detail to clearly signaled one-level references (contract.md, routing.md, tools.md, journey-indicator.md — all verified present), but scored against the actual bundle it shows real organizational problems: references/shared/ contains eleven files including an investigation/ subtree with its own nested references/ and scripts/ directories (2+ levels deep), and most of those files (specialists.md, next-actions.md, matching.md, trace-capabilities.md, cli-setup.md, vscode-setup.md, etc.) are not navigable from SKILL.md itself. That mix of clear top-level pointers and a deep, largely unlinked shared tree sits between the anchors at 3 and 4.

3 / 5

Total

12

/

20

Passed

Description

87%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, highly discriminating description: it explicitly states what the skill does, when to trigger it, and what it is not, with good natural trigger vocabulary for the observability domain. Its only weaknesses are slightly abstract action phrasing and missing common Azure telemetry synonyms like 'logs', 'metrics', 'traces', or 'Application Insights'.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Find or connect an Azure application's or Foundry agent's telemetry", "Confirm source scope and task-specific telemetry access", "answer conceptual questions directly" — with only minor coverage gaps. It falls short of a 5 because the actions are stated as abstract policy verbs rather than concrete deliverables, and the dense boundary phrasing ('not generic app connection, resource creation or deployment readiness') pads rather than specifies.

4 / 5

Completeness

Both halves are explicit: what — "Find or connect an Azure application's or Foundry agent's telemetry"; when — "for an explicit observability, monitoring, alerting, health or operational diagnosis request", plus explicit negative triggers ('not generic app connection, resource creation or deployment readiness') and a pre-deployment design case. The 'when' is embedded rather than a separate 'Use when...' clause, but the rubric accepts equivalent explicit trigger guidance, so it clearly matches the top anchor and not the anchor at 4.

5 / 5

Trigger Term Quality

Natural user phrasing is well covered: "observability, monitoring, alerting, health or operational diagnosis", "telemetry", and "instrumentation/collection" are words users actually say when needing this skill. It misses several equally natural Azure-ecosystem terms ('logs', 'metrics', 'traces', 'Application Insights', 'App Insights'), keeping it below the comprehensive-synonym anchor at 5.

4 / 5

Distinctiveness Conflict Risk

The niche is precise (Azure application / Foundry agent telemetry connection) and the description actively disambiguates against adjacent skills via 'not generic app connection, resource creation or deployment readiness' and 'No automatic provisioning or changes'. Minimal overlap risk with general Azure, coding, or deployment skills.

5 / 5

Total

18

/

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/GitHub-Copilot-for-Azure

Path

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.