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.

referencesspeechcollection.md

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

Collect useful client evidence

Confirm SDK language/version and host first. Use the logging APIs by language and platform, or the matching tab in the official Speech SDK logging article, for exact APIs. Do not install or upgrade the SDK just to collect evidence.

Native SDK logging

Prefer the diagnostic logger APIs when the installed binding has them. Their availability differs by binding (see logging APIs), so check the installed version before falling back to the legacy property:

Logger Use
FileLogger A short, controlled reproduction to a local file
MemoryLogger Intermittent failure; dump the bounded ring buffer promptly
EventLogger Integrate diagnostics into an existing logging pipeline

Loggers are process-wide; parallel objects interleave in one log. Capture before constructing the affected recognizer/synthesizer and stop after the reproduction. Keep the surrounding events; filters and fragments can remove correlation. Use a new path to avoid overwriting evidence. Stop a logger only if the application owns it; coordinate with existing process-wide logging.

Example for the reviewed C++ API, enclosing the existing reproduction:

#include <speechapi_cxx.h>
#include <speechapi_cxx_file_logger.h>

namespace logging = Microsoft::CognitiveServices::Speech::Diagnostics::Logging;
logging::FileLogger::Start("speech-sdk-diagnostic.log");
try
{
    // Run the existing reproduction here, including SDK object creation.
}
catch (...)
{
    logging::FileLogger::Stop();
    throw;
}
logging::FileLogger::Stop();

This is a fragment, not a standalone program. Use an accessible, nonexisting file in a restricted directory. Check whether other SDK objects are active. Do not translate these C++ method names to other languages or SDK versions.

JavaScript has a separate implementation/log format: JavaScript SDK. The bundled native-format analyzer does not certify JavaScript coverage. Preserve app-level events and follow the matching SDK documentation instead.

Record app events alongside the SDK log

Record UTC with timezone, SDK package/version, OS/runtime, input type, endpoint type, and the customer-observed failure. At the corresponding events record:

  • SessionStarted/SessionStopped: SessionId.
  • Recognizing/Recognized: ResultId and result reason, without recognized text.
  • Canceled: available SessionId/ResultId, reason, error code, and locally reviewed/redacted error details.
  • Synthesis: ResultId, reason and cancellation details when available.

API/event availability varies by binding. Use Speech samples and the installed SDK's API reference, not invented event fields. Correlate app and SDK observations by explicit IDs, not adjacency.

Do not confuse local diagnostics with service-side audio/content logging. Do not enable that feature, record microphone audio, or upload sample audio without explicit agreement about content, destination and retention.

Raw diagnostics may contain transcript, synthesis text/SSML, phrase lists, reference text, URLs, paths and credentials. Keep originals local and restricted. Do not request keys/tokens. Review even redacted output before external sharing; the analyzer is an allowlist summary, not a general-purpose log sanitizer.

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