Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
playwright-pom - Skill - OpenSmartRoute
Skillv1.0.0
playwright-pom
Page Object Model patterns for Playwright — when to use POM, how to structure page objects, and when fixtures or helpers are a better fit.
Imported from testdino-hq/playwright-skill (pom/SKILL.md). Install upstream with npx skills add testdino-hq/playwright-skill --skill pom. Copyright stays with the author.
Playwright Page Object Model
Structure your test code for maintainability — know when POM helps and when simpler patterns win.
2 guides covering Page Object Model implementation and the decision framework for choosing between POM, fixtures, and helpers.
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install playwright-pom 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.
When a provider is down or over quota the request moves on; the trace says it did.
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
testdino-hq-playwright-skill-pom.ocm.jsonjson
{
"ocm": "1",
"id": "testdino-hq-playwright-skill-pom",
"kind": "skill",
"name": "playwright-pom",
"description": "Page Object Model patterns for Playwright — when to use POM, how to structure page objects, and when fixtures or helpers are a better fit.",
"publisher": "testdino-hq",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Page Object Model patterns for Playwright — when to use POM, how to structure page objects, and when fixtures or helpers are a better fit."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/testdino-hq/playwright-skill",
"path": "pom/SKILL.md",
"ref": "HEAD",
"url": "https://github.com/testdino-hq/playwright-skill/blob/HEAD/pom/SKILL.md",
"key": "testdino-hq/playwright-skill/pom/SKILL.md"
}
},
"instructions": "# Playwright Page Object Model\n\n> Structure your test code for maintainability — know when POM helps and when simpler patterns win.\n\n**2 guides** covering Page Object Model implementation and the decision framework for choosing between POM, fixtures, and helpers.\n\n## Guide Index\n\n| Topic | Guide |\n|---|---|\n| Page Object Model patterns | [page-object-model.md](page-object-model.md) |\n| POM vs fixtures vs helpers | [pom-vs-fixtures-vs-helpers.md](pom-vs-fixtures-vs-helpers.md) |",
"cost": {
"context_tokens": 120
}
}
Fetch it by URL: GET /api/v1/registry/testdino-hq-playwright-skill-pom/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
