Index of every page on this site: llms.txt
All skills
microsoft avatar

/azure-ai

@0d60658
by microsoftmicrosoft/skills3.2k stars
373
Run it yourself

Build and troubleshoot Azure AI Search, Speech, Document Intelligence, Content Understanding, Translator, Content Safety, and OpenAI apps. WHEN: AI Search, vector search, hybrid search, semantic search, indexer, speech-to-text, text-to-speech, fast or batch transcription, Speech SDK logs, session ID, result ID, OCR, document translation, glossary.

Use this Skill: https://skilld.dev/gh/microsoft/skills/azure-ai

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesspeechinterpretation.md

≈969 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Interpret observations, not assumptions

Read source boundaries for the reviewed release. Every finding needs an analyzer line anchor; avoid broad root-cause statements.

Configuration and feature evidence

property observations distinguish a property write from a read on a property-bag object. Neither proves the user explicitly configured it, nor that it belongs to the nearest session. Values can change; retain conflicting observations, not a process-global "last value".

request_context observations summarize selected speech.context JSON fields: language identification, pronunciation assessment presence, phrase-list count, segmentation, output options, and speaker diarization. They mean the SDK generated that context, not that transport succeeded or the server adopted it. Do not print phrase/reference text, JSON bodies or unknown properties.

Observation Safe interpretation
Locale, voice or format property A value was observed on that object
LID context with mode/candidate languages Those fields occurred in generated context
Pronunciation assessment object Assessment configuration was present; scoring success is unknown
Speaker diarization context Diarization configuration was present; not proof of speaker accuracy
Detailed output/word timings Requested output; may be set by another feature
No feature entry Not observed, not disabled

IDs and lifecycle

The ID inventory is typed, not a count of unique business requests. Session ID is not ResultId. STT intermediate/final IDs can reflect phrase IDs; do not count every occurrence as a new request. TTS result/request equivalence is supported only by the reviewed implementation. One connection can serve multiple synthesis requests. Preserve protocol request IDs separately.

Final recognition records retain numeric reasonCode, not a guessed cause. For the reviewed version, ResultReason defines NoMatch as 0 and RecognizedSpeech as 3. Other values/versions require their matching enum; cancellation details must come from app events when the native trace does not expose them.

Only IDs explicit in the same record are attached to observations. Result IDs on unrelated records remain unassociated. Same thread, time overlap, or similar GUID spelling is insufficient.

Client evidence Next check; not a conclusion
WebSocket upgrade status other than 101 Preserve exact status; compare endpoint/auth mode and error details
DNS error code Resolve the confirmed host from the affected environment
401/403 Verify resource/endpoint, auth method and relevant configuration; no single-cause mapping
NoMatch Read NoMatch details and inspect input/configuration; do not label an outage
TLS certificate verification error (not extracted by the analyzer) Keep the exact line; compare the trust store and any TLS-inspecting proxy of the affected host; never disable validation
Log ends without a terminal event Incomplete capture is possible; do not invent a disconnect

The analyzer does not implement all these diagnoses or echo unknown errors.

Relative milliseconds are not wall-clock UTC or audio offsets. Embedded timestamps are separate observations, not automatic cross-clock anchors. SDK latency properties are reported as SDK metrics, not microphone-to-display or playback latency. Use matching API definitions before deriving a breakdown: TTS latency.

Never disable certificate validation, remove network controls, rotate keys, increase quota, or delete/recreate resources as a generic troubleshooting fix.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning11d4 checks · Risk SAFE
  • Gen Agent Trust Hub11d

    This skill provides tools and guidance for developing and troubleshooting Azure AI services. It includes a local diagnostic script for analyzing Speech SDK logs with robust safety controls, along with comprehensive references for official Azure SDKs and secure authentication practices.

  • Socket11d

    No alerts

  • Snyk11d

    Risk: LOW · No issues

  • Runlayer9mo

    15/15 files flagged

Signed by skilld at 0d60658. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 days ago
metadata
{
  "author": "Microsoft",
  "version": "1.2.6"
}

README badge

README badge for microsoft/skills/azure-ai