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.

spfx-accessibility-and-content-quality - Skill

Name: spfx-accessibility-and-content-quality
Author: paalolav

Imported from paalolav/pol-rss (.claude/skills/spfx-accessibility-and-content-quality/SKILL.md). Install upstream with npx skills add paalolav/pol-rss --skill spfx-accessibility-and-content-quality. Copyright stays with the author.

SPFx Accessibility and Content Quality

Use for

Keyboard, focus, and screen-reader validation.
Placeholder/fallback/empty/error state quality.
UI text clarity, tone, and actionability.

Do not use for

Build pipeline changes.
Back-end/service-only updates with no UI impact.

Trigger conditions

New command surfaces or interaction flows.
Any user-visible text or state model changes.

Enterprise guardrails

Ensure non-mouse operation parity.
Avoid ambiguous microcopy.
Provide clear recovery paths from error and empty states.

Output expectations

Accessible and understandable UI.
Reduced support burden from unclear interactions.

Typical target paths (any SPFx project)

src/webparts/**/components
src/shared/components
src/shared/licensing-ui

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install spfx-accessibility-and-content-quality 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": "paalolav-pol-rss-spfx-accessibility-and-content-quality", "kind": "skill", "name": "spfx-accessibility-and-content-quality", "description": "Accessibility and UX text quality guidance for enterprise SPFx experiences.", "publisher": "paalolav", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Accessibility and UX text quality guidance for enterprise SPFx experiences." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/paalolav/pol-rss", "path": ".claude/skills/spfx-accessibility-and-content-quality/SKILL.md", "ref": "a9b87508d2a37f344ed5ed5654b7d3d389d5ef6d", "url": "https://github.com/paalolav/pol-rss/blob/a9b87508d2a37f344ed5ed5654b7d3d389d5ef6d/.claude/skills/spfx-accessibility-and-content-quality/SKILL.md", "key": "paalolav/pol-rss/.claude/skills/spfx-accessibility-and-content-quality/SKILL.md" } }, "instructions": "# SPFx Accessibility and Content Quality\n\n## Use for\n\n1. Keyboard, focus, and screen-reader validation.\n2. Placeholder/fallback/empty/error state quality.\n3. UI text clarity, tone, and actionability.\n\n## Do not use for\n\n1. Build pipeline changes.\n2. Back-end/service-only updates with no UI impact.\n\n## Trigger conditions\n\n1. New command surfaces or interaction flows.\n2. Any user-visible text or state model changes.\n\n## Enterprise guardrails\n\n1. Ensure non-mouse operation parity.\n2. Avoid ambiguous microcopy.\n3. Provide clear recovery paths from error and empty states.\n\n## Output expectations\n\n1", "cost": { "context_tokens": 205 } }

spfx-accessibility-and-content-quality

About

SPFx Accessibility and Content Quality

Use for

Do not use for

Trigger conditions

Enterprise guardrails

Output expectations

Typical target paths (any SPFx project)

Use it

Install spfx-accessibility-and-content-quality 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

Manifest

Reviews