Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Tweaks Skill · 参数化变体面板 · nexu-io | DecimalAI

nexu-io/tweaks

NewSkillScoreMaintained

Wrap any HTML artifact with a side panel of live, parameterized controls — accent color, type scale, density, motion, theme — that rewrite CSS custom properties in real time and persist to localStorage. Lets the user explore variants of a design without re-prompting the agent. Use when the brief asks for "variants", "side-by-side options", "tweak this", "let me adjust", "live knobs", or "实时调参".

Frontendby nexu-io

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Frontend / UI pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/nexu-io-tweaks/SKILL.md

decimalai skills pull nexu-io-tweaks --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/nexu-io-tweaks/SKILL.md https://app.decimal.ai/s/nexu-io-tweaks/SKILL.md

Raw file: /s/nexu-io-tweaks/SKILL.md ↗ · machine-readable summary at /s/nexu-io-tweaks.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 17h ago

Yes — +50% lift · at higher cost+51% tokens0% turns68% of whole cases pass with skill (15/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-01	✗→✓	▲ Improved	36%	0%
case-02	✗→✓	▲ Improved	36%	0%
case-08	✗→✓	▲ Improved	36%	0%
case-09	✗→✓	▲ Improved	36%	0%
case-11	✗→✓	▲ Improved	35%	0%

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v5 — 8/22/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

nexu-io / open-design

design-templates/tweaks/SKILL.md

View on GitHub ↗

License Apache-2.0Imported 8/22/2026Version v3Bundled 1 file

Skill contents

assets/

SKILL.md

Tweaks Skill · 参数化变体面板

Wrap any HTML artifact with a side panel of live controls that rewrite CSS custom properties in real time and persist to localStorage. Inspired by the huashu-design tweak pattern.

What you produce

A single self-contained HTML file with two layers:

Stage — the original artifact (landing page / deck / dashboard)

re-keyed so all visual decisions read from CSS custom properties: --accent, --scale, --density, --mode, --motion.

Panel — a fixed sidebar (or drawer on small viewports) with

form controls bound to those custom properties via a tiny vanilla-JS bridge. Persists every change to localStorage keyed by the artifact identifier.

The user can:

Open the artifact and see the stage rendered with their saved

preferences (or sensible defaults).

Adjust accent / scale / density / mode / motion in the panel and

watch the stage update instantly — no rerender.

Press <kbd>T</kbd> to hide / reveal the panel; <kbd>R</kbd> to

reset to defaults.

Refresh the page — every choice is persisted.

When to use

The user generated something they like 80% of, and wants to dial

in the last 20% themselves.

You're presenting a design system / brand and want the audience to

feel the variants live (instead of you re-running the agent).

You're shipping a stand-alone demo (e.g. a portfolio piece) and

want viewers to play.

When not to use

One-shot artifacts that won't be iterated on (e.g. a runbook —

parameters don't help).

When the artifact's value is in fixed ratios (e.g. an infographic

with carefully balanced data viz — knobs would degrade it).

The 5 standard knobs

> Pick a subset that suits the artifact. Don't ship all 5 if only 2 > matter — clutter is a regression.

1. `--accent` — Accent color

A select with 5–8 curated swatches (don't ship a free color picker — the user will pick a bad color and blame you).

js
const ACCENT_PRESETS = [
  { id: 'rust',    val: '#c96442', label: 'Rust' },
  { id: 'cobalt',  val: '#2c4d8e', label: 'Cobalt' },
  { id: 'sage',    val: '#4a7a3f', label: 'Sage' },
  { id: 'plum',    val: '#7a3f6a', label: 'Plum' },
  { id: 'graphite',val: '#3a3a3a', label: 'Graphite' },
];

The artifact uses var(--accent) everywhere it had a hard-coded accent before. Border / link / pull-quote rule / CTA all flip together.

2. `--scale` — Type scale (0.85 / 1.0 / 1.15)

Three settings: Compact (0.85), Normal (1.0), Generous (1.15). All font-size declarations multiply by var(--scale) via calc(... * var(--scale)).

Don't go beyond ±15% — beyond that the layout breaks (column flow, breakpoints, line counts).

3. `--density` — Layout density (Tight / Normal / Roomy)

Three settings that swap the spacing scale: Tight (0.75) / Normal (1.0) / Roomy (1.4). All padding / gap / margin declarations multiply by var(--density).

This is the highest-impact knob — it's also the most fragile, so every layout-critical container must declare its base spacing in custom properties before you wrap.

4. `--mode` — Light / Dark

A 2-state toggle. Sets data-mode="light" vs "dark" on the <html> element and the artifact's :root selector responds with two color sets.

If the artifact already has a media-query-based dark mode, replace it with the data-attr version — the user's choice should win over their OS.

5. `--motion` — Off / Subtle / Lively

Three settings. Maps to a CSS variable --motion-mult that scales all transition-duration / animation-duration declarations:

Off — 0s (also disables WebGL canvases / decorative animation).
Subtle — 1.0 (the artifact's authored timing).
Lively — 1.6 (slower transitions, more visible motion).

Respect prefers-reduced-motion: default to Off if the user has that set, regardless of stored preference.

Host integration contract (REQUIRED)

The OpenDesign viewer toolbar has a Tweaks toggle that drives panel visibility from outside the iframe. For the toggle to bind to your panel, your artifact must speak one of these two protocols (pick one; don't mix). The toolbar enables itself the moment it sees either signal.

Protocol A — postMessage (recommended for agent-generated artifacts)

Use this when the panel mounts via JS (React, vanilla, anything dynamic).

Artifact → host:

On mount, post { type: '__edit_mode_available', visible?: boolean } to

window.parent. Tells the toolbar a panel exists; the optional visible reports the panel's initial state so the toolbar toggle starts in sync. Omit visible for the common "panel is already on screen" case (the host treats a missing field as true so the legacy zero-arg message keeps working). Pass visible: false to declare a default-closed panel.

When the user closes the panel locally (× button, Esc, etc.), post

{ type: '__edit_mode_dismissed' }. Toolbar flips to "off".

Host → artifact:

{ type: '__activate_edit_mode' } — open the panel (setOpen(true)).
{ type: '__deactivate_edit_mode' } — close the panel (setOpen(false)).

Minimal listener:

js
window.addEventListener('message', (e) => {
  const t = e?.data?.type;
  if (t === '__activate_edit_mode') setOpen(true);
  else if (t === '__deactivate_edit_mode') setOpen(false);
});
// Or, for a default-closed panel:
//   window.parent.postMessage({ type: '__edit_mode_available', visible: open }, '*');
window.parent.postMessage({ type: '__edit_mode_available' }, '*');
// in your close handler:
const dismiss = () => {
  setOpen(false);
  window.parent.postMessage({ type: '__edit_mode_dismissed' }, '*');
};

Panel may default to open or closed — the host syncs its toggle to whichever state the artifact reports.

Protocol B — class-based (used by `assets/wrap.html`)

Use this only when you wrap the template verbatim. The artifact ships a .tw-panel element and toggles a .tw-hidden class for visibility. The viewer's iframe bridge (in apps/web/src/runtime/srcdoc.ts) hides the panel on initial paint, watches the class via MutationObserver, and relays state both directions. No JS required in the artifact beyond what the template already includes.

Selectors are fixed: .tw-panel (the panel root) and .tw-hidden (the hidden state). If you rename either, the bridge can't find it.

Anti-pattern

Don't invent a third protocol or rename either set of identifiers. The toolbar toggle only binds to A or B. Custom panels with custom classes and no postMessage will leave the toolbar greyed out.

Implementation primitives

Read assets/wrap.html — it ships the panel + bridge as an inert template. Your job is to:

Take the user's existing artifact HTML.
Lift its accent / mode / spacing / scale into custom properties

(search for hard-coded #hex / Npx / Nrem and convert).

Paste the contents into the marked region of wrap.html.
Edit assets/wrap.html's KNOBS array to keep only the knobs

you decided are relevant to this artifact. Don't ship 5 if 2 matter.

Patch the STORAGE_KEY to a unique slug (tweaks-<artifact-slug>).

The bridge in wrap.html:

Loads localStorage[STORAGE_KEY] JSON on first paint.
Applies values as document.documentElement.style.setProperty('--accent', ...).
Listens to every form control's change event and writes back.
Exposes <kbd>T</kbd> (toggle panel) and <kbd>R</kbd> (reset).

Workflow

Step 1 — Acquire the artifact

Same options as the critique skill:

Project file (index.html in the project folder).
Pasted HTML in the chat.
Generated by you in this turn.

Step 2 — Decide which knobs apply

Read the artifact's CSS first. For each knob, decide yes / no:

--accent — yes if the artifact has 1 accent color used ≥ 3 times.
--scale — yes if the artifact is type-driven (article, deck,

pricing page).

--density — yes if the artifact has consistent gap / padding

rhythm (deck, dashboard, landing). No for runbooks (already dense).

--mode — yes if the artifact has authored dark mode tokens, or

you're willing to derive them.

--motion — yes if the artifact has any transition / animation

worth scaling. No for static reports / critique reports.

Default: 3 knobs is the sweet spot. Five is too busy, one is not worth a panel.

Step 3 — Lift hard-coded values into custom properties

Open assets/wrap.html's <style> block — copy its custom-property naming scheme (--accent, --scale, etc.). In the user's artifact, find every place those concerns live and rewrite:

color: #c96442 → color: var(--accent)
font-size: 18px → font-size: calc(18px * var(--scale))
padding: 24px 32px → padding: calc(24px * var(--density)) calc(32px * var(--density))
transition: opacity 200ms → transition: opacity calc(200ms * var(--motion-mult))

If the artifact uses clamp() or vw already, multiply the outer value by the custom property — don't tear apart clamp(...).

Step 4 — Paste into the wrap

Copy the artifact's <style> and <body> into the marked regions of wrap.html. Keep the panel + bridge intact.

Step 5 — Test the loop

Open the result, click each knob at least once, refresh the page, confirm the choice persists. If a knob breaks the layout — remove it, don't ship it.

Output contract

<artifact identifier="tweaks-<artifact-slug>" type="text/html" title="<Artifact Title> · Tweaks">
<!doctype html>
<html>...</html>
</artifact>

One sentence before the artifact ("Wrapped X with a 3-knob tweak panel — accent / scale / mode."). Stop after </artifact>.

Hard rules

Don't ship a free color picker — only curated swatches. Users

pick bad colors when given freedom; saving them from that is the whole point.

Persist by artifact identifier — tweaks-<slug>, not a global

key. Two artifacts open in two tabs must not share state.

Respect prefers-reduced-motion — default to Off for motion

if the user has that set, override only on explicit click.

Single-file — no external CSS / JS / fonts beyond the artifact's

existing imports. Inline the panel + bridge.

Panel hidden by default on viewports < 720px — slide-in drawer

via a "T" button at top-right.

Don't ship more than 5 knobs. Three is the sweet spot.

Want to see if nexu-io/tweaks would activate on your phrasing? Try it before you install — no LLM call, no signup.

Latest benchmark · publisher runVerified

8/28/2026, 16:45 UTC · 22 cases

Lift

+50%

68% vs 18%

Agent turns

1.0 vs 1.0

Tokens

+51%

10,361.5 vs 6,871.86

fail → pass · 13pass → pass · 2fail → fail · 5pass → fail · 2

Per-case results (22)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-03 I am sharing a presentation slide deck formatted in HTML/CSS. I'd like a customizable version containing an overlay control sidebar that lets viewers fine-tune aesthetic choices live. Replace static CSS values with variable properties for theme elements, pair them with form inputs that modify the page instantly without page reloads, persist all adjustments across page refreshes using key-based browser storage, and implement host frame messaging so the viewer container toolbar can control panel visibility. Deliver the complete document inside `<artifact>` tags, placed immediately after a one-sentence recap.	fail→fail	49,550	37,428	-24%	1	1	0%	8,298	11,260	+36%	0	0	—
case-01 I have a single-page landing page HTML snippet that I am presenting to clients. Convert it into an interactive standalone HTML file equipped with a control panel for real-time style adjustments. Extract fixed visual properties like colors, font sizing, and spacing layout into root CSS variables, and link form controls to update those variables on the fly. User selections should save to local storage under a unique key for this artifact, and the sidebar must send and receive messages with the parent iframe to sync toggle state with the host toolbar. Format the output inside an `<artifact>` XML block, preceded by one short explanatory sentence.	fail→pass	48,812	52,330	+7%	1	1	0%	8,310	11,272	+36%	0	0	—
case-02 Here is an HTML dashboard mockup I built. Turn this into an interactive showcase where visitors can adjust key design traits using an embedded side drawer. Refactor hardcoded style values into custom CSS properties driven by a lightweight JS bridge, save state changes to browser storage so choices persist per artifact, and integrate postMessage communication so an outer viewer window toolbar can show or hide the control drawer. Output the final result as a standalone file wrapped in `<artifact>` tags with title and identifier attributes, preceded by a single sentence summary.	fail→pass	37,776	48,327	+28%	1	1	0%	8,292	11,254	+36%	0	0	—
case-04 Here is an emergency database failover runbook HTML file with step-by-step shell commands, warning callouts, and code blocks. We want to convert this runbook into an interactive document. Should we add a live visual tweaking side panel with knobs for type scale, density, accent colors, dark mode, and motion speed so engineers can customize the layout while following recovery steps? Provide your analysis and recommendation.	pass→pass	19,844	10,644	-46%	1	1	0%	2,567	4,308	+68%	0	0	—
case-05 We have an SVG/HTML data visualization infographic showing quarterly financial breakdowns with precisely calculated chart element proportions, label offsets, and color-coded risk bands. We are considering wrapping it with live user controls to adjust spacing density, scale multiplier, and color schemes. Evaluate whether wrapping this balanced data graphic with a parameter tweak sidebar is suitable.	pass→pass	17,941	8,961	-50%	1	1	0%	2,286	3,986	+74%	0	0	—
case-06 I am drafting a static UX audit report in HTML summarizing usability test findings and heuristic violations. We want to make the audit document interactive. Should we integrate a persistent tweak panel with visual sliders for density and color themes for the client reading the report?	pass→fail	16,898	52,308	+210%	1	1	0%	1,976	11,200	+467%	0	0	—
case-07 I am wrapping a SaaS pricing table HTML artifact with a style control panel. I want users to pick any custom hex code for brand buttons, so I plan to put an `<input type='color'>` in the panel. Convert this pricing table into a tweakable HTML artifact. Output the artifact wrapped in `<artifact identifier='tweaks-pricing-table' type='text/html' title='Pricing Table · Tweaks'>` tags, preceded by a single sentence.	fail→fail	37,801	34,468	-9%	1	1	0%	8,284	11,246	+36%	0	0	—
case-08 I have a blog reader HTML artifact with font sizes defined as 16px, 24px, and 36px. I want to add a standard type scale knob with Compact, Normal, and Generous settings. Apply font size scaling in CSS and construct the complete wrapped file inside an `<artifact identifier='tweaks-blog-reader' type='text/html' title='Blog Reader · Tweaks'>` block, preceded by a single sentence.	fail→pass	52,477	36,453	-31%	1	1	0%	8,284	11,246	+36%	0	0	—
case-09 I am building a tweak panel for a card grid dashboard layout. The grid cards use hardcoded padding of 20px and gap of 16px. I want to allow users to pick between Tight, Normal, and Roomy spacing. Update the CSS for spacing and output the final HTML wrapped in `<artifact identifier='tweaks-card-grid' type='text/html' title='Card Grid · Tweaks'>` tags, preceded by one sentence summary.	fail→pass	36,400	47,991	+32%	1	1	0%	8,285	11,247	+36%	0	0	—
case-10 An HTML landing page artifact contains `@media (prefers-color-scheme: dark)` styles in its CSS. I want to add a light/dark mode toggle control in a tweak panel so users can force dark or light themes manually. Convert the theme switcher logic and output the file inside an `<artifact identifier='tweaks-landing-page' type='text/html' title='Landing Page · Tweaks'>` block, preceded by one sentence.	fail→fail	36,553	36,431	-0%	1	1	0%	8,281	11,243	+36%	0	0	—
case-11 I have an animated portfolio hero section artifact with CSS transitions and animations. I want to add a motion knob (Off, Subtle, Lively). If a user has `prefers-reduced-motion: reduce` configured in their browser, how should the initial motion knob default behave, and how should transition durations scale? Provide the full HTML artifact inside `<artifact identifier='tweaks-portfolio-hero' type='text/html' title='Portfolio Hero · Tweaks'>` preceded by a single sentence.	fail→pass	99,427	36,434	-63%	1	1	0%	8,290	11,189	+35%	0	0	—
case-12 I am creating a React-based dynamic tweak panel inside an HTML web component artifact that will run inside an iframe viewer toolbar host. On component mount, the panel needs to notify the host application toolbar about its presence and initial state. Write the postMessage call sent to window.parent inside the HTML artifact. Precede the `<artifact identifier='tweaks-dynamic-view' type='text/html' title='Dynamic View · Tweaks'>` with one sentence.	fail→pass	24,624	28,713	+17%	1	1	0%	4,305	9,216	+114%	0	0	—
case-13 In a dynamic JS tweak panel artifact, the user clicks an 'X' close button to dismiss the sidebar. Write the close handler function so that both the local panel state closes and the outer host iframe toolbar is informed to turn off its edit mode toggle. Output the HTML artifact in `<artifact identifier='tweaks-dismissable-panel' type='text/html' title='Dismissable Panel · Tweaks'>` format, preceded by one sentence.	fail→pass	51,276	47,535	-7%	1	1	0%	8,280	11,242	+36%	0	0	—
case-14 I am embedding a custom JS tweak panel in an iframe viewer. The host toolbar sends message events to toggle panel visibility remotely. Should I invent a custom event structure like `toggle-sidebar` and `close-sidebar`? Implement the message event listener for the host toolbar messages, and output the artifact inside `<artifact identifier='tweaks-toolbar-sync' type='text/html' title='Toolbar Sync · Tweaks'>` tags, preceded by one sentence.	fail→pass	37,780	47,520	+26%	1	1	0%	6,463	11,118	+72%	0	0	—
case-20 I am creating a tweaked HTML showcase artifact for a design component. I want to import external JS control libraries via CDN script tags and separate panel CSS into a second file. Convert the component into a tweaked file wrapped in `<artifact identifier='tweaks-design-comp' type='text/html' title='Design Component · Tweaks'>` preceded by a single sentence recap.	fail→pass	49,889	48,042	-4%	1	1	0%	8,265	11,227	+36%	0	0	—
case-15 I am using the verbatim wrap template approach (Protocol B) without custom JS message handlers. What specific element class name and hidden state class name must be used so the outer host viewer's MutationObserver bridge can detect panel state? Wrap an HTML artifact adhering to this class specification inside `<artifact identifier='tweaks-template-wrap' type='text/html' title='Template Wrap · Tweaks'>` preceded by one sentence.	fail→pass	16,373	46,191	+182%	1	1	0%	2,642	9,558	+262%	0	0	—
case-16 I have two separate HTML presentation artifacts being customized in different browser tabs: a sales deck and a product roadmap. I want to save their tweak control settings to browser storage. Should I use a global storage key like `localStorage.setItem('user_tweaks', ...)` so all artifacts share settings? Show the correct localStorage key naming approach and output the artifact in `<artifact identifier='tweaks-sales-deck' type='text/html' title='Sales Deck · Tweaks'>` format.	fail→pass	49,669	30,643	-38%	1	1	0%	8,289	10,199	+23%	0	0	—
case-17 I want to add keyboard accessibility to a tweak panel artifact so users can quickly toggle panel visibility and reset controls to default values without using the mouse. Implement the window keydown listener and output the complete document inside `<artifact identifier='tweaks-key-nav' type='text/html' title='Key Nav · Tweaks'>` tags preceded by one short sentence.	fail→fail	52,306	34,669	-34%	1	1	0%	8,263	11,225	+36%	0	0	—
case-18 I am designing the CSS layout for a tweak panel overlay. On desktop displays, it displays as a fixed right sidebar. How should the panel display on small mobile viewports (e.g. less than 720px wide) on initial load, and how is it toggled? Implement the responsive CSS rules and wrap the code inside `<artifact identifier='tweaks-responsive-layout' type='text/html' title='Responsive Layout · Tweaks'>` preceded by one sentence.	pass→fail	28,758	48,100	+67%	1	1	0%	6,707	11,251	+68%	0	0	—
case-19 I have a marketing product page HTML snippet with 12 different style attributes (border radius, box shadow, font weight, line height, header color, body color, button color, spacing, scale, dark mode, motion speed, backdrop blur). I want to create form sliders for all 12 attributes in the tweak panel. Convert this product page into a tweaked artifact inside `<artifact identifier='tweaks-marketing-page' type='text/html' title='Marketing Page · Tweaks'>` preceded by one sentence summary.	fail→pass	36,260	37,629	+4%	1	1	0%	8,297	11,259	+36%	0	0	—
case-21 I have a feature announcement HTML card snippet. Add a live style control sidebar with accent color, mode, and scale parameters. Provide your output wrapped in `<artifact>` tags with proper identifier and title attributes, preceded by exactly one summary sentence.	fail→fail	35,707	35,547	-0%	1	1	0%	8,237	11,199	+36%	0	0	—
case-22 An HTML landing page artifact has hardcoded hex colors `#c96442` on CTA buttons, hero borders, pull-quote left rules, and link hover states. Replace these hardcoded hex values to support live color theme changes via a tweak panel. Output the resulting file wrapped in `<artifact identifier='tweaks-hero-landing' type='text/html' title='Hero Landing · Tweaks'>` preceded by a single sentence.	fail→pass	54,010	35,511	-34%	1	1	0%	8,280	11,008	+33%	0	0	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +50 percentage points is the difference between those two pass rates over the 22 comparable cases. 2 cases got worse with the skill loaded, and they are included in that figure.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 18.2%
Pass rate with the skill: 68.2%
Cases attempted: 22
Cases counted toward lift: 22
Cases that regressed: 2
Skill version measured: v3
Run completed: 8/28/2026, 16:45 UTC

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-01

Prompt

I have a single-page landing page HTML snippet that I am presenting to clients. Convert it into an interactive standalone HTML file equipped with a control panel for real-time style adjustments. Extract fixed visual properties like colors, font sizing, and spacing layout into root CSS variables, and link form controls to update those variables on the fly. User selections should save to local storage under a unique key for this artifact, and the sidebar must send and receive messages with the parent iframe to sync toggle state with the host toolbar. Format the output inside an `<artifact>` XML block, preceded by one short explanatory sentence.

Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.

Show both answers

SkillScore blends 4 signalsno signals yet

BenchmarkRun a verified benchmark with positive lift

Live evalNeeds ≥20 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

No signals yet — run a benchmark or collect evaluated traces to earn a score.

Verified on gemini-3.6-flash · re-tested today

Other measured skills in the registry, with their headline benchmark lift.