How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

lynx-trace-record - Skill - OpenSmartRoute

Name: lynx-trace-record
Author: lynx-community

Imported from lynx-community/skills (skills/lynx-trace-record/SKILL.md). Install upstream with npx skills add lynx-community/skills --skill lynx-trace-record. Copyright stays with the author.

1. Workflow Example

The recording process requires using the trace_record CLI tool. The order of operations is critical.

Step 1. List connected clients:

First, list all connected clients to get the client ID. This helps you identify which app to trace.

If you have multiple connected clients, ask the user to specify the client ID you want to trace. Then, use this ID with the --client parameter to trace.
If you have only one connected client, you can omit the --client parameter.
If no clients are found, prompt the user to connect their device via USB and open the debugging app.
```
node <path_to_the_skill>/scripts/trace_record.bundle.cjs list-clients
```

Step 2. Start recording:

Execute the start command BEFORE building or opening the page on your device. This ensures you capture the entire first frame of the page. Use the --client parameter with the client ID from Step 1.

node <path_to_the_skill>/scripts/trace_record.bundle.cjs start --client <client-id>

Optional start parameters can be controlled from the user's natural language request:

User intent	CLI parameter	Trace config field	Default
Include only specific trace categories	`--include-categories <categories>`	`includedCategories`	`*`
Exclude specific trace categories	`--exclude-categories <categories>`	`excludedCategories`	`*`
Enable memory data collection	`--enable-memory-trace`	`enableMemoryTrace`	`false`
Disable automatic Garbage Collection	`--no-force-gc`	`forceGC`	`true`
Automatically capture heap snapshots for "shared-group" VMs	`--enable-auto-heap-snapshot`	`enableAutoHeapSnapshot`	`false`
Only capture automatic heap snapshots for a specific "shared-group" VM	`--shared-group-id <id>`	`sharedGroupId`	empty string
Specify the JS profile type, such as quickjs or v8	`--js-profile-type <type>`	`JSProfileType`	empty string (JS profile disabled)
Specify the JS profile interval, such as 100	`--js-profile-interval <interval>`	`JSProfileInterval`	`100` when `JSProfileType` is non-empty and interval is `<= 0`; otherwise `-1`

When the user asks in natural language, translate the request into the corresponding start flags. For example, if the user says "record a trace with trace_record, enable memory data collection, and automatically capture heap snapshots for the VM named 'xxx'", run:

node <path_to_the_skill>/scripts/trace_record.bundle.cjs start --client <client-id> --enable-memory-trace --enable-auto-heap-snapshot --shared-group-id xxx

Common trace categories are lynx, vitals, javascript, jsb, and devtool. If the user asks to include only specific event categories, pass them as a comma-separated list with --include-categories. For example, "录制trace时只允许以下类型的事件js，jsb" maps to --include-categories lynx,jsb. If the user asks "录制trace时允许所有事件", do not pass --include-categories; the default includedCategories: ['*'] records all events.

If the user asks to exclude specific event categories, pass them as a comma-separated list with --exclude-categories. For example, "录制trace时关闭devtool事件和vitals事件" maps to --exclude-categories devtool,vitals.

If the user asks to use a specific JS engine profile type, such as "record with v8 JS profile", add --js-profile-type v8. If the user does not ask for JS profile collection, do not pass --js-profile-type; the default empty string disables JS profile collection.

If the user asks to use a specific JS profile interval, such as "record with JS profile interval 100", add --js-profile-interval 100. For example, "record with v8 JS profile and interval 100" maps to --js-profile-type v8 --js-profile-interval 100.

Step 3. Build and Open the Page

Start your development server. If it does not auto-open the page, manually open the target page.

  pnpm run dev

Step 4. Perform Actions

If you are debugging interactions (e.g., scrolling, clicking, data updates), perform those actions on the device now.

Step 5. Stop Recording & Get Stream Handle

Stop the trace recording. The CLI will output a JSON response containing a stream field (this is your stream handle). Use the --client parameter with the same client ID from Step 1.

node <path_to_the_skill>/scripts/trace_record.bundle.cjs end --client <client-id>

Step 6. Read and Save Trace Data

Use the stream handle obtained from Step 5 to download and save the trace file to your local machine. Use the --client parameter with the same client ID from Step 1.

node <path_to_the_skill>/scripts/trace_record.bundle.cjs readData --client <client-id> --stream <stream-handle> --output ./my-trace.pftrace

2. Troubleshooting Common Errors

"Please restart the app to enable tracing functionality"

enable_debug_mode was off. The CLI attempted to enable it automatically. Solution: Force close the app on your device, restart it, and try recording again from Step 1.

"Tracing functionality is not supported in the current version"

Make sure you're using the Lynx development version. For more information, visit: https://lynxjs.org/guide/start/integrate-lynx-dev-version.html

"Tracing is not started, please start tracing first"

You need to run start before running end and readData.

Install lynx-trace-record and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "lynx-community-skills-lynx-trace-record", "kind": "skill", "name": "lynx-trace-record", "description": "This guide provides step-by-step instructions for recording Lynx performance traces. Use this guide when the user asks how to record a trace.", "publisher": "lynx-community", "version": "1.0.0", "capabilities": { "domains": [ "observability" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "This guide provides step-by-step instructions for recording Lynx performance traces. Use this guide when the user asks how to record a trace." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/lynx-community/skills", "path": "skills/lynx-trace-record/SKILL.md", "ref": "HEAD", "url": "https://github.com/lynx-community/skills/blob/HEAD/skills/lynx-trace-record/SKILL.md", "key": "lynx-community/skills/skills/lynx-trace-record/SKILL.md" } }, "instructions": "## 1. Workflow Example\n\nThe recording process requires using the `trace_record` CLI tool. **The order of operations is critical**.\n\n### Step 1. List connected clients:\nFirst, list all connected clients to get the client ID. This helps you identify which app to trace.\n- If you have multiple connected clients, ask the user to specify the client ID you want to trace. Then, use this ID with the `--client` parameter to trace.\n- If you have only one connected client, you can omit the `--client` parameter.\n- If no clients are found, prompt the user to connect their device via USB and open the debuggi", "cost": { "context_tokens": 1354 } }

lynx-trace-record

About

1. Workflow Example

Step 1. List connected clients:

Step 2. Start recording:

Step 3. Build and Open the Page

Step 4. Perform Actions

Step 5. Stop Recording & Get Stream Handle

Step 6. Read and Save Trace Data

2. Troubleshooting Common Errors

"Please restart the app to enable tracing functionality"

"Tracing functionality is not supported in the current version"

"Tracing is not started, please start tracing first"

Install lynx-trace-record and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews