К основному содержанию
скилл CX Codex

wandb-primary — скилл для Claude Code: работа с W&B

Скилл для задач по Weights & Biases: обзор проекта, runs и artifacts, трейсы Weave, отчёты, свипы. Пригодится, когда вопрос охватывает сразу несколько частей W&B.

Установить в Claude Code · Через Skills CLI (Vercel) Все способы и платформы ↓
npx skills add wandb/skills --skill wandb-primary -a claude-code
Открыть на GitHub

Что делает wandb-primary

Скилл разбирает запрос по двум категориям. Brief — точечное чтение или подсчёт, которое укладывается в один скрипт: сколько runs, лучший loss, конфиг конкретного запуска. Intense — открытое исследование с итерациями: непонятная схема данных, джойны, графики, сравнение свипов. Скриптов может быть несколько, но каждый должен опираться на данные, полученные в предыдущем шаге.

У проекта W&B две поверхности: runs через wandb.Api() и трейсы Weave через weave.init() и client.get_calls(). На общий вопрос «что происходит в проекте» скилл советует проверить обе в первом проходе, а потом сузить ответ до той, где реально есть данные. Пустую поверхность он упоминать не станет.

Для работы нужны WANDB_API_KEY, WANDB_ENTITY и WANDB_PROJECT — из окружения или из промпта. Скрипты запускаются в том Python-окружении, которое доступно вашему агенту, а недостающие опциональные пакеты ставятся по мере надобности. Если ключа в окружении нет, запросы к API упадут сразу — это повод проверить переменные до первого запуска.

Какие задачи решает

  • посчитать число runs в проекте и найти лучший loss
  • разобрать конфиг конкретного запуска по его id
  • сравнить несколько свипов между собой
  • посмотреть трейсы Weave и оценки агента
  • выгрузить отчёт W&B в PDF или LaTeX для комплаенса

Примеры запросов агенту

  • сколько runs в моём проекте и какой у них лучший loss?
  • сравни эти два свипа и покажи, где расходятся метрики
  • что вообще происходит в проекте — посмотри runs и трейсы Weave

Как установить wandb-primary

1Через Skills CLI (Vercel)

npx skills add wandb/skills --skill wandb-primary -a claude-code

2Вручную: положить файлы

~/.claude/skills/wandb-primary/SKILL.md

Папка скилла целиком; для одного проекта — .claude/skills/wandb-primary/

По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов

Вопросы о wandb-primary

Как установить wandb-primary в Claude?

Выполните npx skills add wandb/skills --skill wandb-primary -a claude-code. Скилл окажется в ~/.claude/skills/wandb-primary/SKILL.md.

Что делает wandb-primary?

Закрывает широкие задачи по Weights & Biases: обзор проекта, runs и artifacts, трейсы и оценки Weave, отчёты, воркспейсы, автоматизации, свипы, Launch и Agent Lens.

Что нужно для работы скилла?

Переменные окружения WANDB_API_KEY, WANDB_ENTITY и WANDB_PROJECT. Скрипты идут через Python-окружение вашего агента, опциональные пакеты ставятся по необходимости.

Исходный текст

SKILL.md · Apache-2.0
---
name: wandb-primary
description: "Primary W&B skill for broad or mixed Weights & Biases work: project overviews, W&B runs and artifacts, Weave traces and evaluations, Reports, Workspaces, Automations, Sweeps, Launch, and Agent Lens. Use when the task spans multiple W&B surfaces or the user asks generally what is happening in a W&B project."
---
<!--
SPDX-FileCopyrightText: 2026 CoreWeave, Inc.
SPDX-License-Identifier: Apache-2.0
SPDX-PackageName: skills
-->

# W&B Primary Skill

## Environment defaults

- **Python**: run scripts with the Python environment available to your coding agent. Install missing optional packages only when needed.
- **Credentials**: use `WANDB_API_KEY`, `WANDB_ENTITY`, and `WANDB_PROJECT` from the user's environment or prompt.

---

## Scope and approach

Classify each request before acting:

- **Brief** — a focused read or compute that maps to one query and a short answer
  ("How many runs?", "Best loss?", "Show the config of abc123"). Solve it in one
  script; add a second only if the first surfaced a load-bearing lead. Default to
  brief when in doubt.
- **Intense** — open-ended investigation with iterative discovery: ambiguous data,
  unknown schema, cross-cutting joins, plots, multi-stage analysis ("What's wrong
  with my training runs?", "Compare these sweeps"). Several scripts are fine, but
  each must be load-bearing — plan the next call from the data you just got, not
  from a generic checklist.

A W&B project has two complementary surfaces — **runs** (experiment tracking,
`wandb.Api()`) and **Weave traces** (observability, `weave.init()` →
`client.get_calls()`). For a broad "what's going on in this project?" question,
probe **both** in the first evidence pass (parallel scripts, or the combined
"Summarize project" recipe below), then scope the answer to the surface(s) that
actually hold data. If a surface is empty, don't mention it.

---

## Fast recipes — use these first

These cover the most common tasks. Each is a single script. Copy, fill in placeholders, run.

## Fast product/API answers

For small W&B product or API questions, answer directly from this section. Do not run
tools, inspect docs, or query the user's project unless they explicitly ask for live
data. Keep the answer short: direct answer, exact UI/API path, minimal code if useful.
If the recommendation depends on missing context, include targeted diagnostic questions
in the same response instead of blocking.

For workspace migration or project-structure guidance, ask the diagnostic questions
before prescribing a structure or script. Use the phrase "Before I prescribe a
structure/script, I need to know:" and include the questions that materially change
the answer; then give only tentative guidance.

### Product facts to answer from memory

| User asks | Answer with |
|---|---|
| "How can I see team members via API?" | Use `api = wandb.Api()` then `api.team("<team_name>").members`. Member objects expose fields such as `username`, `name`, `email`, and admin status. |
| "Can I programmatically set/update workspaces?" | Yes. Use the `wandb-workspaces` Python library to define, save, and edit workspaces/views programmatically, including copying views across projects. Before prescribing the exact script, ask whether this is W&B Workspaces, what fields are renamed, how often, what the current manual workflow is, what access/tooling they have available, how many views/workspaces are affected, whether the renames are metrics/config/summary fields, whether they want in-place edits or generated standardized views, and how renames propagate downstream. |
| "Static/archive report for compliance?" | W&B Reports have a built-in static export: open the report action menu (`...`), choose Download, then select PDF or LaTeX. Store the exported file in JIRA or compliance systems. Do not recommend browser Print -> Save as PDF as the primary path. |
| "Can reports include PNG/JPEG images?" | Yes. In the UI, press `/` on a new report line, choose Image, then drag/drop the PNG/JPEG. Programmatically, use `wandb-workspaces`: `import wandb_workspaces.reports.v2 as wr`, then add `wr.Image(url=..., caption=...)` to the report `blocks`. |
| "Are reports associated with an entity?" | Yes. Reports are created within a project, and every project belongs to an entity (user or team). The `wr.Report` API requires both `entity` and `project`; team-project reports are visible to the team, private user-project reports are private to that user. |
| "Can I update a prompt created in the UI?" | Weave prompt versions are immutable. To "update", publish a new version with the same prompt name using `weave.publish()` or the prompt publish API. The new version becomes `:latest`, previous versions remain in history, and this works for UI-created prompts if you reuse the same prompt name. |
| "How should we structure runs across projects?" | Do not prescribe a structure before surfacing ambiguity and do not validate "using projects wrong" without context. Ask targeted questions first about expected run volume per project, what current projects represent, what cross-project comparisons/filters are needed, whether compared runs are the same conceptual experiment/eval/model family, metric-schema differences, audiences/access boundaries, and whether related experiments are over-split. Then give tentative guidance: projects are best as comparison/workspace boundaries; use config, tags, groups, and `job_type` for segmentation inside a project. |
| "Need more observability into agent traces?" | Recommend W&B Weave only. Show `weave.init(...)`, `@weave.op()`, and optionally `weave.Evaluation` for evaluations. Keep the recommendation focused on W&B Weave unless the user asks for tool comparisons. |
| "How can I check UI agent success from workspace data?" | List these three UI/data options explicitly: (1) screenshots from trajectory runs, (2) Weave traces of trajectories, and (3) summary tables from runs. Then explain that screenshots show visual task completion, Weave traces show step-by-step calls/errors/scorer outputs, and run summary tables let users compare success metrics across agents. |
| "Show code for sweeps / multiple experiments" | Put W&B instrumentation directly in the main sweep/training code, not an optional appendix. Use `wandb.init(project=..., config=...)`, `wandb.log(...)`, and `wandb.agent(...)`/sweep config patterns unconditionally unless the user asks for a flag. |

### Trace-count semantics

Use these rules before every Weave count query:

- "total traces" or "total calls" means all calls. Use `calls_query_stats` with no
  `trace_roots_only` filter. Do not deduplicate by `trace_id` unless the prompt
  asks for unique traces.
- "root traces", "root-level traces", or "traces with no parent" means root calls.
  Use `filter={"trace_roots_only": True}` only for those prompts.
- "successful/non-error traces" means total calls minus calls with status `error`
  / `descendant_error` / non-null `exception`; report that as the primary count.
  `summary.weave.status == "success"` is a useful supporting breakdown, but it
  excludes running calls, which are still non-error. Do not count only root traces
  unless the user says root/root-level.
- "error/exception traces" means calls with status `error` OR `descendant_error`
  OR a non-null `exception`. For root-level error counts, add
  `trace_roots_only=True` to that same error query.
- `Evaluation.evaluate` counts are op counts. Use an `op_names` filter for
  `weave:///<entity>/<project>/op/Evaluation.evaluate:*`. Add `trace_roots_only`
  only if the user explicitly asks for root eval traces.
- For exact count tasks, run one script that prints the query and the number; do not
  run sample/exploratory scripts after the count is already known.

### Eval-analysis rules

- Filter Evaluation.evaluate calls with
  `op_names=[f"weave:///{entity}/{project}/op/Evaluation.evaluate:*"]`.
- Fetch only needed columns (`id`, `display_name`, `started_at`, `ended_at`,
  `summary`, `inputs`, `output`) and avoid broad object dumps.
- Eval token usage is in `summary.usage`; sum `input_tokens`,
  `output_tokens`, and `total_tokens` across model keys.
- Eval success/error counts are in `summary.status_counts`, not
  `summary.weave.status_counts`. Normalize enum and string keys before reading
  `success`, `error`, and `descendant_error`.
- For success-rate tasks, do not lead with a long 43-row markdown table.
  First answer with totals, both fractions, and a compact
  `Error evaluations (N):` TSV/code block containing every errored eval id,
  date, success_count, error_count, and status. If full per-eval rows are
  requested, use short IDs/dates/counts after the error list; avoid repeating
  long duplicate display names where they cause truncation. If some evals are
  still running, report both denominators: success-status evals over completed
  evals and no-error evals over all evals.
- Child dataset rows are `Evaluation.predict_and_score:*` calls with
  `parent_ids=[eval_call.id]`.
- Dataset refs live on `inputs["self"].dataset` inside the Evaluation object.
  Count distinct dataset object refs from the user's project data; repeated evals can reuse the same dataset ref.
- For scorer inventories, eval summaries, and scorer evolution, include both
  wrapper scorer ops whose short names end in `_scorer` and class scorer ops
  ending in `.score`. Never filter only for the substring `scorer`; versioned
  class scorers like `MyClassifier.score` do not contain it.
- For large scorer inventories, include a compact full TSV/code block
  (`scorer\tcount`) for every scorer and then summarize family groupings.
  Do not use long prose tables that may truncate before all counts appear.

### Count runs (exact, fast)

```python
import wandb, os
api = wandb.Api(timeout=120)
path = f"{os.environ['WANDB_ENTITY']}/{os.environ['WANDB_PROJECT']}"
total = len(api.runs(path, per_page=1, include_sweeps=False, lazy=True))
finished = len(api.runs(path, filters={"state": "finished"}, per_page=1, include_sweeps=False, lazy=True))
crashed = len(api.runs(path, filters={"state": "crashed"}, per_page=1, include_sweeps=False, lazy=True))
running = len(api.runs(path, filters={"state": "running"}, per_page=1, include_sweeps=False, lazy=True))
print(f"Total: {total}  |  Finished: {finished}  |  Crashed: {crashed}  |  Running: {running}")
```

Run-count rules:

- Use one script for exact counts. If it prints the requested count, answer from
  that stdout; do not rerun just to add labels or nicer formatting.
- Use `include_sweeps=False` for normal run-table counts unless the prompt asks
  for sweep runs. For sweep counts, query sweeps explicitly.
- For status breakdowns, scan once and report all states you see (`finished`,
  `failed`, `crashed`, `killed`, etc.). When crashed/killed runs exist, report
  unsuccessful terminal rate `(failed + crashed + killed) / total` as the
  primary failure rate and include failed-only rate as a supporting number.
- For tags, count runs with at least one tag and also list distinct tag names and
  the runs attached to each tag.
- For run groups, report named groups from `groupedRuns(groupKeys: ["group"])`
  and compute ungrouped runs as `total_runs - sum(named_group_counts)`.
- For sweep-run tasks, list each sweep's run count and explicitly report the
  total runs across all sweeps.

### Count/list sweeps

Do not inspect the W&B SDK source for routine sweep questions. Use the public
project API directly:

```python
import os, wandb

entity = os.environ["WANDB_ENTITY"]
project = os.environ["WANDB_PROJECT"]
api = wandb.Api(timeout=120)

sweeps = list(api.project(project, entity=entity).sweeps(per_page=50))
rows = []
for sweep in sweeps:
    config = sweep.config or {}
    metric = config.get("metric") or {}
    rows.append({
        "id": sweep.id,
        "state": sweep.state,
        "method": config.get("method"),
        "metric": metric.get("name"),
        "goal": metric.get("goal"),
        "run_count": len(sweep.runs),
    })

print(f"sweep_count={len(rows)}")
print(f"total_sweep_runs={sum(r['run_count'] for r in rows)}")
for r in rows:
    print(r)
```

### Finished runs with trigger/user

For prompts asking who triggered each run, fetch the filtered runs once and read
`run.user.username` / `run.user.name`; do not search reference files.

```python
import os, wandb

entity = os.environ["WANDB_ENTITY"]
project = os.environ["WANDB_PROJECT"]
path = f"{entity}/{project}"
api = wandb.Api(timeout=120)

runs = api.runs(
    path,
    filters={"state": "finished"},
    order="+created_at",
    per_page=100,
    include_sweeps=False,
)
rows = []
for run in runs:
    user = getattr(run, "user", None)
    rows.append({
        "created_at": run.created_at,
        "name": run.display_name or run.name,
        "id": run.id,
        "username": getattr(user, "username", None),
        "user_name": getattr(user, "name", None),
    })

print(f"finished_count={len(rows)}")
for r in rows:
    print(r)
```

### Count traces (fast, server-side)

```python
import weave, os, logging
logging.getLogger("weave").setLevel(logging.ERROR)
from weave.trace_server.trace_server_interface import CallsQueryStatsReq
from weave.trace_server.interface.query import Query

entity = os.environ["WANDB_ENTITY"]
project = os.environ["WANDB_PROJECT"]
client = weave.init(f"{entity}/{project}")
pid = f"{entity}/{project}"

# Total calls/traces
stats = client.server.calls_query_stats(CallsQueryStatsReq(project_id=pid))
print(f"Total calls: {stats.count}")

# Root traces only
root_stats = client.server.calls_query_stats(CallsQueryStatsReq(
    project_id=pid, filter={"trace_roots_only": True}
))
print(f"Root traces: {root_stats.count}")

# Count by op name
for op in ["Evaluation.evaluate", "my_op.turn"]:
    op_ref = f"weave:///{entity}/{project}/op/{op}:*"
    s = client.server.calls_query_stats(CallsQueryStatsReq(
        project_id=pid,
        filter={"op_names": [op_ref]},
    ))
    print(f"  {op}: {s.count}")

# Count calls whose op_name contains a substring, e.g. scorer calls.
score_query = Query(**{"$expr": {"$contains": {
    "input": {"$getField": "op_name"},
    "substr": {"$literal": ".score"},
    "case_insensitive": True,
}}})
score_stats = client.server.calls_query_stats(CallsQueryStatsReq(
    project_id=pid, query=score_query
))
print(f"Scorer calls (.score): {score_stats.count}")

# Count a named op substring such as create_embeddings.
embedding_query = Query(**{"$expr": {"$contains": {
    "input": {"$getField": "op_name"},
    "substr": {"$literal": "create_embeddings"},
    "case_insensitive": True,
}}})
embedding_stats = client.server.calls_query_stats(CallsQueryStatsReq(
    project_id=pid, query=embedding_query
))
print(f"create_embeddings calls: {embedding_stats.count}")

# Error/exception calls. Include descendant_error when the prompt says
# "error status or exception"; those are traces whose children failed.
error_query = Query(**{"$expr": {"$or": [
    {"$eq": [{"$getField": "summary.weave.status"}, {"$literal": "error"}]},
    {"$eq": [
        {"$getField": "summary.weave.status"},
        {"$literal": "descendant_error"},
    ]},
    {"$not": [{"$eq": [{"$getField": "exception"}, {"$literal": None}]}]},
]}})
error_stats = client.server.calls_query_stats(CallsQueryStatsReq(
    project_id=pid, query=error_query
))
root_error_stats = client.server.calls_query_stats(CallsQueryStatsReq(
    project_id=pid, filter={"trace_roots_only": True}, query=error_query
))
print(f"Error/exception calls: {error_stats.count}")
print(f"Root error/exception calls: {root_error_stats.count}")
print(f"Non-error calls: {stats.count - error_stats.count}")
```

### Count create_embeddings calls and input sizes

```python
import os, statistics, weave, logging, sys
from collections import Counter
logging.getLogger("weave").setLevel(logging.ERROR)
from weave.trace_server.trace_server_interface import CallsQueryStatsReq
from weave.trace_server.interface.query import Query
sys.path.insert(0, "skills/wandb-primary/scripts")
from weave_helpers import unwrap

entity = os.environ["WANDB_ENTITY"]
project = os.environ["WANDB_PROJECT"]
pid = f"{entity}/{project}"
client = weave.init(pid)

query = Query(**{"$expr": {"$contains": {
    "input": {"$getField": "op_name"},
    "substr": {"$literal": "create_embeddings"},
    "case_insensitive": True,
}}})
total = client.server.calls_query_stats(CallsQueryStatsReq(
    project_id=pid, query=query
)).count

sizes = []
for call in client.get_calls(query=query, limit=total, columns=["inputs"]):
    inputs = unwrap(call.inputs)
    texts = inputs.get("texts") or inputs.get("input") or []
    if isinstance(texts, str):
        sizes.append(1)
    else:
        sizes.append(len(texts))

dist = Counter(sizes)
print(f"create_embeddings calls: {total}")
print(f"typical texts per call: {dist.most_common(1)[0][0] if dist else 0}")
print(f"distribution: {dict(sorted(dist.items()))}")
print(f"mean texts per call: {statistics.mean(sizes) if sizes else 0:.4f}")
```

### Count feedback records

```python
import os, weave, logging
logging.getLogger("weave").setLevel(logging.ERROR)
from weave.trace_server.trace_server_interface import FeedbackQueryReq

entity = os.environ["WANDB_ENTITY"]
project = os.environ["WANDB_PROJECT"]
pid = f"{entity}/{project}"
client = weave.init(pid)

limit = 1000
offset = 0
total = 0
while True:
    res = client.server.feedback_query(FeedbackQueryReq(
        project_id=pid,
        fields=["id"],
        limit=limit,
        offset=offset,
    ))
    rows = (
        getattr(res, "result", None)
        or getattr(res, "feedback", None)
        or getattr(res, "rows", None)
        or []
    )
    n = len(rows)
    total += n
    if n < limit:
        break
    offset += limit

print(f"Feedback records: {total}")
```

### List root op names with counts

```python
import os, weave, logging
from collections import Counter
logging.getLogger("weave").setLevel(logging.ERROR)
from weave.trace_server.trace_server_interface import CallsQueryStatsReq

entity = os.environ["WANDB_ENTITY"]
project = os.environ["WANDB_PROJECT"]
pid = f"{entity}/{project}"
client = weave.init(pid)
root_filter = {"trace_roots_only": True}

root_count = client.server.calls_query_stats(CallsQueryStatsReq(
    project_id=pid, filter=root_filter
)).count

def short_op(op_name: str) -> str:
    tail = op_name.split("/op/")[-1]
    return tail.rsplit(":", 1)[0]

counts = Counter()
for call in client.get_calls(
    filter=root_filter,
    limit=root_count,
    columns=["op_name"],
):
    counts[short_op(call.op_name)] += 1

for name, count in counts.most_common():
    print(f"{name}\t{count}")
```

### List all op names with counts

```python
import os, weave, logging
from collections import Counter
logging.getLogger("weave").setLevel(logging.ERROR)
from weave.trace_server.trace_server_interface import CallsQueryStatsReq

entity = os.environ["WANDB_ENTITY"]
project = os.environ["WANDB_PROJECT"]
pid = f"{entity}/{project}"
client = weave.init(pid)
total = client.server.calls_query_stats(CallsQueryStatsReq(project_id=pid)).count

def short_op(op_name: str) -> str:
    return op_name.split("/op/")[-1].rsplit(":", 1)[0]

counts = Counter()
for call in client.get_calls(limit=total, columns=["op_name"]):
    counts[short_op(call.op_name)] += 1

print(f"Unique ops: {len(counts)}")
for name, count in counts.most_common():
    print(f"{name}\t{count}")
```

### Count long-duration traces

Do not try to do datetime arithmetic inside a Weave `Query`; stream timestamp
columns and count locally.

```python
import os, weave, logging
logging.getLogger("weave").setLevel(logging.ERROR)
from weave.trace_server.trace_server_interface import CallsQueryStatsReq

entity = os.environ["WANDB_ENTITY"]
project = os.environ["WANDB_PROJECT"]
pid = f"{entity}/{project}"
client = weave.init(pid)
total = client.server.calls_query_stats(CallsQueryStatsReq(project_id=pid)).count

threshold_s = 60
long_count = 0
scanned = 0
for call in client.get_calls(
    limit=total,
    columns=["started_at", "ended_at"],
):
    scanned += 1
    if call.started_at and call.ended_at:
        duration_s = (call.ended_at - call.started_at).total_seconds()
        if duration_s > threshold_s:
            long_count += 1

print(f"Scanned calls: {scanned}")
print(f"Duration > {threshold_s}s: {long_count}")
```

### Find model names in traces

```python
import os, weave, logging
from collections import Counter
logging.getLogger("weave").setLevel(logging.ERROR)
from weave.trace_server.trace_server_interface import CallsQueryStatsReq
import sys
sys.path.insert(0, "skills/wandb-primary/scripts")
from weave_helpers import unwrap

entity = os.environ["WANDB_ENTITY"]
project = os.environ["WANDB_PROJECT"]
pid = f"{entity}/{project}"
client = weave.init(pid)
total = client.server.calls_query_stats(CallsQueryStatsReq(project_id=pid)).count

def collect_models(obj, out):
    obj = unwrap(obj)
    if isinstance(obj, dict):
        for k, v in obj.items():
            if k == "model" and isinstance(v, str):
                out.append(v)
            collect_models(v, out)
    elif isinstance(obj, list):
        for item in obj:
            collect_models(item, out)

models = Counter()
for call in client.get_calls(
    limit=total,
    columns=["inputs", "output", "summary"],
):
    found = []
    collect_models(call.inputs, found)
    collect_models(call.output, found)
    usage = unwrap(call.summary).get("usage", {}) if call.summary else {}
    for model_name in usage:
        if isinstance(model_name, str):
            found.append(model_name)
    for model_name in set(found):
        models[model_name] += 1

for name, count in models.most_common():
    print(f"{name}\t{count}")
```

### Analyze embedding dimensions and model

```python
import os, weave, logging
from collections import Counter
logging.getLogger("weave").setLevel(logging.ERROR)
from weave.trace_server.interface.query import Query
import sys
sys.path.insert(0, "skills/wandb-primary/scripts")
from weave_helpers import unwrap

entity = os.environ["WANDB_ENTITY"]
project = os.environ["WANDB_PROJECT"]
client = weave.init(f"{entity}/{project}")

embedding_query = Query(**{"$expr": {"$contains": {
    "input": {"$getField": "op_name"},
    "substr": {"$literal": "create_embeddings"},
    "case_insensitive": True,
}}})

dims = Counter()
models = Counter()
no_output = 0
for call in client.get_calls(
    query=embedding_query,
    limit=100000,
    columns=["inputs", "output"],
):
    inputs = unwrap(call.inputs) or {}
    model = inputs.get("model") if isinstance(inputs, dict) else None
    models[model or "<missing>"] += 1

    output = unwrap(call.output)
    found = False
    if isinstance(output, list):
        for item in output:
            if isinstance(item, list) and item and isinstance(item[0], (int, float)):
                dims[len(item)] += 1
                found = True
    if not found:
        no_output += 1

print("embedding_models")
for name, count in models.most_common():
    print(f"{name}\t{count}")
print("embedding_dimensions")
for dim, count in dims.most_common():
    print(f"{dim}\t{count}")
print(f"no_embedding_output\t{no_output}")
```

### List evaluation scorers

For scorer inventories, include wrapper scorer ops like `faithfulness_scorer`
and class `.score` ops like `HallucinationFreeScorer.score` when present.

```python
import os, weave, logging
from collections import Counter
logging.getLogger("weave").setLevel(logging.ERROR)
from weave.trace_server.trace_server_interface import CallsQueryStatsReq

entity = os.environ["WANDB_ENTITY"]
project = os.environ["WANDB_PROJECT"]
pid = f"{entity}/{project}"
client = weave.init(pid)
total = client.server.calls_query_stats(CallsQueryStatsReq(project_id=pid)).count

def short_op(op_name: str) -> str:
    return op_name.split("/op/")[-1].rsplit(":", 1)[0]

scorers = Counter()
for call in client.get_calls(limit=total, columns=["op_name"]):
    name = short_op(call.op_name)
    if name.endswith("_scorer") or name.endswith(".score"):
        scorers[name] += 1

for name, count in scorers.most_common():
    print(f"{name}\t{count}")
```

### Summarize project (runs + traces in one script)

```python
import wandb, weave, os, logging
logging.getLogger("weave").setLevel(logging.ERROR)
from weave.trace_server.trace_server_interface import CallsQueryStatsReq

entity = os.environ["WANDB_ENTITY"]
project = os.environ["WANDB_PROJECT"]
path = f"{entity}/{project}"

# --- Runs ---
api = wandb.Api(timeout=120)
total_runs = len(api.runs(path, per_page=1, include_sweeps=False, lazy=True))
finished = len(api.runs(path, filters={"state": "finished"}, per_page=1, include_sweeps=False, lazy=True))
recent = api.runs(path, order="-created_at", per_page=5)[:5]

print(f"=== Runs ({total_runs} total, {finished} finished) ===")
for r in recent:
    print(f"  {r.name} [{r.state}] {r.created_at[:10]}")

# --- Weave Traces ---
client = weave.init(path)
pid = f"{entity}/{project}"
root_stats = client.server.calls_query_stats(CallsQueryStatsReq(
    project_id=pid, filter={"trace_roots_only": True}
))
print(f"\n=== Weave Traces ({root_stats.count} root traces) ===")

recent_calls = list(client.get_calls(
    sort_by=[{"field": "started_at", "direction": "desc"}],
    limit=5,
    columns=["op_name", "started_at", "display_name"],
))
for c in recent_calls:
    name = c.display_name or c.op_name.split("/")[-1].split(":")[0]
    started = c.started_at.strftime("%Y-%m-%d %H:%M") if c.started_at else "?"
    print(f"  {name} @ {started}")
```

### Inspect a single run

```python
import wandb, os
api = wandb.Api(timeout=120)
path = f"{os.environ['WANDB_ENTITY']}/{os.environ['WANDB_PROJECT']}"

run = api.run(f"{path}/RUN_ID")
print(f"Name: {run.name}")
print(f"State: {run.state}")
print(f"Created: {run.created_at}")
print(f"Tags: {run.tags}")
print(f"Last step: {run.lastHistoryStep}")

# Key metrics (replace with actual keys from probe or user request)
for k in ["loss", "val_loss", "accuracy"]:
    v = run.summary_metrics.get(k)
    if v is not None:
        print(f"  {k}: {v}")
```

### Inventory artifacts (types → collections → versions)

The run table is not the whole project — artifacts (datasets, model checkpoints,
tables) are separate. `probe_project()` surfaces artifact names; this enumerates
them directly.

```python
import wandb, os
api = wandb.Api(timeout=120)
path = f"{os.environ['WANDB_ENTITY']}/{os.environ['WANDB_PROJECT']}"

for atype in api.artifact_types(project=path):
    collections = list(api.artifact_collections(path, atype.name, per_page=1000))
    print(f"{atype.name}: {len(collections)} collections")
    for col in collections[:10]:
        try:
            n_versions = len(col.artifacts(per_page=50))
        except Exception:
            n_versions = "?"
        print(f"  {col.name}  ({n_versions} versions)")
```

### Summarize an artifact's files (metadata + manifest + bounded read)

Inspect what an artifact *contains* — don't infer from its name. Read the manifest
first; download only the small structured files you actually need.

```python
import wandb, os
api = wandb.Api(timeout=120)
path = f"{os.environ['WANDB_ENTITY']}/{os.environ['WANDB_PROJECT']}"

art = api.artifact(f"{path}/ARTIFACT_NAME:latest")  # or :v3
print(f"name={art.name} type={art.type} size_bytes={art.size} aliases={art.aliases}")
md = art.metadata or {}
print(f"metadata_keys={list(md)[:20]}")

entries = sorted(art.manifest.entries.values(), key=lambda e: e.path)
print(f"file_count={len(entries)}")
for e in entries[:25]:
    print(f"  {e.path}  ({e.size} bytes)")

# Read ONE small structured file without downloading the whole artifact:
# p = art.get_entry("metrics.jsonl").download()  # local path to just that file
# import pandas as pd; df = pd.read_json(p, lines=True); print(df.describe())
```

Artifact rules:

- For "what's in this artifact?" read the manifest and a bounded sample of rows;
  do not download multi-GB artifacts to answer a structural question.
- Use `run.logged_artifacts()` to find a run's outputs (e.g. checkpoint locations)
  and `run.used_artifacts()` for its inputs.

### System metrics (GPU / CPU / memory) — MUST use stream='system'

GPU, CPU, memory, network, and disk metrics live in a **separate system stream**.
`run.history()` without `stream='system'` returns training metrics only — all
`system.gpu.*`, `system.cpu.*`, `system.memory.*` keys will be absent. Finding
no system keys in the default stream is **NOT** evidence they don't exist.

**BEFORE concluding GPU or system metrics are unavailable, you MUST call
`run.history(stream='system')`.**

```python
import wandb, os, pandas as pd
api = wandb.Api(timeout=120)
path = f"{os.environ['WANDB_ENTITY']}/{os.environ['WANDB_PROJECT']}"

runs = api.runs(path, filters={"state": "finished"}, per_page=100)
rows = []
for run in runs:
    sys_df = run.history(stream="system", samples=500)
    if sys_df.empty or "system.gpu.0.gpu" not in sys_df.columns:
        rows.append({"run": run.name, "gpu_mean": None, "gpu_min": None, "gpu_max": None})
        continue
    gpu = sys_df["system.gpu.0.gpu"].dropna()
    rows.append({
        "run": run.name,
        "gpu_mean": round(gpu.mean(), 1),
        "gpu_min": round(gpu.min(), 1),
        "gpu_max": round(gpu.max(), 1),
        "low_util_pct": round(100 * (gpu < 30).sum() / len(gpu), 1) if len(gpu) else None,
    })

df = pd.DataFrame(rows)
print(df.to_string(index=False))
```

Run-lookup rules:

- For user-facing run names, prefer `run.display_name` or `run.name`; include
  `run.id` separately if useful. Do not report only the run ID as the name.
- For "best", "highest", "lowest", "latest", and "longest" tasks, use one script
  that prints name, id, metric value, state, group, `job_type`, and tags for the
  winner. Use that context in the final answer.
- For baseline-vs-hyperopt questions, `group is None` and empty `job_type`/tags
  usu...

© wandb · Apache-2.0 · wandb/skills

Похожие скиллы

Всё по теме «ИИ и ML» →
ml-pipeline-automation secondsky Скилл для сборки ML-пайплайнов на Airflow, Kubeflow и MLflow: обучение по расписанию, трекинг экспериментов, алерты при падении задач. CX Codex +1 389установок experiment-tracking-swanlab Orchestra Research Скилл учит агента вести эксперименты в SwanLab: логировать метрики, конфиги и медиа, поднимать локальный дашборд. CX Codex +1 896установок marimo-batch marimo-team Скилл переводит блокноты marimo в режим пакетного запуска через CLI и планировщик. Он добавляет типизацию параметров на Pydantic и сохраняет работу в веб-интерфейсе. CX Codex +1 3 700установок mle-workflow affaan-m Скилл для перевода модельной работы в продакшн-систему: контракты данных, воспроизводимое обучение, оценка качества, деплой и откат. CX Codex +1 4 600установок ml-pipeline https://github.com/Jeffallan Скилл проектирует пайплайны машинного обучения: настраивает трекинг экспериментов в MLflow, собирает DAG для Kubeflow или Airflow и валидирует данные перед обучением. CX Codex +1 3 900установок senior-ml-engineer Alireza Rezvani Помогает выводить ML-модели в продакшен, строить MLOps-пайплайны, RAG и интеграции с LLM API. Нужен для развёртывания, мониторинга и контроля стоимости запросов. 915установок

Спонсоры проекта

Компании, которые помогают держать аналитику открытой