Speech-To-Text-With-Databricks: Skill for Claude Code

.claude/skills/analyze-mlflow-trace/SKILL.md

analyzing-mlflow-trace is a skill for Claude Code from alessandro9110/Speech-To-Text-With-Databricks. It costs 93 tokens per session (2,100 once invoked), scanned A, a copy of analyzing-mlflow-trace, MIT.

A guide for analyzing one MLflow trace, which records the steps taken by a machine-learning or AI application. It examines the operations, inputs, outputs, timing, errors, and quality feedback recorded in that run.

In plain words
What is it for?
Use it to investigate a trace by ID, debug failed operations, inspect tool or model calls, and assess the quality of an AI application's behavior.
Why use it?
It helps explain what happened during a single execution and find the cause of an error or poor result without guessing from the final output alone.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is alessandro9110/Speech-To-Text-With-Databricks's own configuration. It tells Claude Code how to work on Speech-To-Text-With-Databricks itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Speech-To-Text-With-Databricks configures →

Reuse

Borrowing it

Nothing to install: this file belongs to alessandro9110/Speech-To-Text-With-Databricks. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/alessandro9110/Speech-To-Text-With-Databricks/main/.claude/skills/analyze-mlflow-trace/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/alessandro9110/Speech-To-Text-With-Databricks

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for analyzing-mlflow-trace

README.md
[![agentmods](https://agentmods.dev/badge/skills/alessandro9110/speech-to-text-with-databricks/analyze-mlflow-trace/github.svg)](https://agentmods.dev/skills/alessandro9110/speech-to-text-with-databricks/analyze-mlflow-trace)
Your own site
<a href="https://agentmods.dev/skills/alessandro9110/speech-to-text-with-databricks/analyze-mlflow-trace"><img src="https://agentmods.dev/badge/skills/alessandro9110/speech-to-text-with-databricks/analyze-mlflow-trace/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for analyzing-mlflow-trace

Your own site · 80×15
<a href="https://agentmods.dev/skills/alessandro9110/speech-to-text-with-databricks/analyze-mlflow-trace"><img src="https://agentmods.dev/badge/skills/alessandro9110/speech-to-text-with-databricks/analyze-mlflow-trace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,100 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00093 $0.02100
Opus 5.5 $0.00037 $0.00840
Sonnet 5.5 $0.00019 $0.00420
Haiku 4.5 $0.00009 $0.00210

Measured 1mo ago against content hash 58131b3b7e05, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

analyzing-mlflow-trace scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to analyzing-mlflow-trace — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/analyze-mlflow-trace/SKILL.md · 138 lines

How it starts

The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Analyzing a Single MLflow Trace

Trace Structure

A trace captures the full execution of an AI/ML application as a tree of spans. Each span represents one operation (LLM call, tool invocation, retrieval step, etc.) and records its inputs, outputs, timing, and status. Traces also carry assessments — feedback from humans or LLM judges about quality.

It is recommended to read references/trace-structure.md before analyzing a trace — it covers the complete data model, all fields and types, analysis guidance, and OpenTelemetry compatibility notes.

Handling CLI Output

Traces can be 100KB+ for complex agent executions. Always redirect output to a file — do not pipe mlflow traces get directly to jq, head, or other commands, as piping can silently produce no output.

# Fetch full trace to a file (traces get always outputs JSON, no --output flag needed)
mlflow traces get --trace-id <ID> > /tmp/trace.json

# Then process the file
jq '.info.state' /tmp/trace.json
jq '.data.spans | length' /tmp/trace.json

Prefer fetching the full trace and parsing the JSON directly rather than using --extract-fields. The --extract-fields flag has limited support for nested span data (e.g., span inputs/outputs may return empty objects). Fetch the complete trace once and parse it as needed.

JSON Structure

The trace JSON has two top-level keys: info (metadata, assessments) and data (spans).

{
  "info": { "trace_id", "state", "request_time", "assessments", ... },
  "data": { "spans": [ { "span_id", "name", "status", "attributes", ... } ] }
}

Key paths (verified against actual CLI output):

What jq path
Trace state .info.state
All spans .data.spans
Root span .data.spans[] | select(.parent_span_id == null)
Span status code .data.spans[].status.code (values: STATUS_CODE_OK, STATUS_CODE_ERROR, STATUS_CODE_UNSET)
Span status message .data.spans[].status.message
Span inputs .data.spans[].attributes["mlflow.spanInputs"]
Span outputs .data.spans[].attributes["mlflow.spanOutputs"]
Assessments .info.assessments
Assessment name .info.assessments[].assessment_name
Feedback value .info.assessments[].feedback.value
Feedback error .info.assessments[].feedback.error
Assessment rationale .info.assessments[].rationale

Read the full file on GitHub · 138 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 138 lines · 93 tokens per session scan A 58131b3b7e05

Subscribe to this mod's changes

analyzing-mlflow-trace is a skill published in the GitHub repository alessandro9110/Speech-To-Text-With-Databricks (4 stars, last pushed 8mo ago), licensed MIT. It adds 93 tokens to every session and 2,100 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to analyzing-mlflow-trace, differing in 2 lines, and is treated as a copy.

Related

analyzing-mlflow-trace compared with skills from other repositories

analyzing-mlflow-trace next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
analyzing-mlflow-tracealessandro9110/Speech-To-Text-With-DatabricksSkill48mo agoMITA93Claude Code
databricks-expertpersonamanagmentlayer/pclSkill4411d agoApache-2.0A74Claude Code
redosPurpleAILAB/DecepticonSkill6.5k8d agoApache-2.0A117Claude Code
potpie-clipotpie-ai/potpieSkill5.8k7d agoApache-2.0A60Codex
pattern-exhaustionPurpleAILAB/DecepticonSkill6.5k8d agoApache-2.0A33Claude Code, Codex
potpie-debug-memorypotpie-ai/potpieSkill5.8k7d agoApache-2.0A41Claude Code, Codex
scanner-overviewPurpleAILAB/DecepticonSkill6.5k8d agoApache-2.0A40Claude Code, Codex