docs: clarify router vs model slug in analytics-schema and generations skills

[Justin-Summerville]

Summary

Companion to the data-warehouse and Looker PRs — updates skills so agents using the OpenRouter Analytics and Generations APIs understand the router vs model slug distinction.

• openrouter-analytics-schema: model dimension description now states it's the resolved downstream model, not the router, and directs to the router field for router traffic.
• openrouter-generations: model field description clarifies it's the resolved model; router field description explains it identifies the router and should be used for router traffic. The "What you get back" summary also clarifies the relationship.

Link to Devin session: https://openrouter.devinenterprise.com/sessions/65ba8131d98d4c32a2995b7ba0829d7c
Requested by: @Justin-Summerville

[devin-ai-integration]

Original prompt from Justin

SYSTEM:
=== BEGIN THREAD HISTORY (in #intern-fermat) ===
<most_recent_message>
Justin Summerville (U092M3NSGS3): @Devin read this thread and recommend updates to our column descriptions and skills to clarify when to look at router slugs vs model slugs
</most_recent_message>
=== END THREAD HISTORY ===

Thread URL: https://openrouter.slack.com/archives/C0AL411FKK6/p1781476895304359?thread_ts=1781476895.304359&amp;cid=C0AL411FKK6

The latest message is the one right above that tagged you. The <most_recent_message> is the message that you should use to guide your goals + task for this session, and you should use the rest of the slack thread as context.

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR that start with 'DevinAI' or '@devin'.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[perry-the-pr-maintainer]

Perry's Review

Clarifies that model in analytics and generations APIs returns the resolved downstream model (not the router slug), and explains when to use the router field for router traffic analysis.

Verdict: ✅ LGTM

Details

Risk: 🟢 Low — docs-only clarifications, no code changes

CI: 1 pending (perry/review — this review, not a blocker)

Findings (see inline comments for full context):

• nit: the router dimension is referenced in the updated model description but not listed in the Dimension Categories section

Codex: not run (trivial tier)

Research: not run (trivial tier)

Security: no concerns — no code touched, no credentials, no API routes

Test coverage: n/a — docs-only

Unresolved threads: none

---

Scope: first review (full)
Review: tier=trivial · model=claude-sonnet-latest · score=0.1

Superseded by updated Perry review

[perry-the-pr-maintainer]

Perry's Review

Clarifies router vs model slug distinction in analytics-schema and generations skill docs — the prior suggestion about the router dimension redirect has been addressed correctly.

Verdict: ✅ LGTM

Details

Risk: 🟢 Low

CI: all passing ✅

Findings: none

Research: skipped — trivial tier

Security: no concerns

Test coverage: docs-only, no tests applicable

Unresolved threads: 1 outdated (Perry's prior router dimension suggestion — addressed by Devin; code updated to guide agents to generation_id + the openrouter-generations skill or ClickHouse instead)

Scope: incremental — 0 new lines since prior review
Review: tier=trivial · model=claude-sonnet-latest · score=?