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.
parsing - Skill - OpenSmartRoute
Skillv1.0.0
parsing
Before writing or editing any parser, quote in your reply the fixture file path and the actual HTML snippet you are parsing. If the fixture does not exist, stop and say so. Never infer element IDs or
Instruction file imported from anppakbr/vahandashboard (.github/instructions/parsing.instructions.md). Copyright stays with the author.
On the Vahan HTML — the single most important rule in this file:
Never write a parser against HTML you have not seen. Fetch a real response, save it
to tests/fixtures/, inspect it, then write the parser against that saved fixture
with a test that asserts on real values. If your environment cannot reach
vahan.parivahan.gov.in, stop and tell me — I will capture a HAR file and the
raw responses from my machine and commit them. Do not invent element IDs, do not
guess at table structures, and do not write a parser that "should work".
Before writing or editing any parser, quote in your reply the fixture file
path and the actual HTML snippet you are parsing. If the fixture does not
exist, stop and say so. Never infer element IDs or table structure.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/anppakbr-vahandashboard-parsing-instructions/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "anppakbr-vahandashboard-parsing-instructions",
"kind": "skill",
"name": "parsing",
"description": "Before writing or editing any parser, quote in your reply the fixture file path and the actual HTML snippet you are parsing. If the fixture does not exist, stop and say so. Never infer element IDs or table structure.",
"publisher": "anppakbr",
"version": "1.0.0",
"capabilities": {
"domains": [
"data_analysis"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Before writing or editing any parser, quote in your reply the fixture file path and the actual HTML snippet you are parsing. If the fixture does not exist, stop and say so. Never infer element IDs or table structure."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/anppakbr/vahandashboard",
"path": ".github/instructions/parsing.instructions.md",
"ref": "91230733c3a4bb4d97570cab19989b4e7452264d",
"url": "https://github.com/anppakbr/vahandashboard/blob/91230733c3a4bb4d97570cab19989b4e7452264d/.github/instructions/parsing.instructions.md",
"key": "anppakbr/vahandashboard/.github/instructions/parsing.instructions.md"
},
"applies_to": "src/vahan/parsing/**"
},
"instructions": "**On the Vahan HTML — the single most important rule in this file:**\n\n> Never write a parser against HTML you have not seen. Fetch a real response, save it\n> to `tests/fixtures/`, inspect it, then write the parser against that saved fixture\n> with a test that asserts on real values. If your environment cannot reach\n> `vahan.parivahan.gov.in`, **stop and tell me** — I will capture a HAR file and the\n> raw responses from my machine and commit them. Do not invent element IDs, do not\n> guess at table structures, and do not write a parser that \"should work\".\n\nBefore writing or editing any parser, q",
"cost": {
"context_tokens": 194
}
}
Fetch it by URL: GET /api/v1/registry/anppakbr-vahandashboard-parsing-instructions/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.
