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.
html - Skill - OpenSmartRoute
Skillv1.0.0
html
Use semantic markup (`header`, `nav`, `main`, `section`, `footer`) over generic `div`s where an element already means the right thing. - Localized `hreflang` `<link>` tags are injected client-side by
Instruction file imported from omega1119/harmonic-tools (.github/instructions/html.instructions.md). Copyright stays with the author.
Use semantic markup (header, nav, main, section, footer) over generic
divs where an element already means the right thing.
Localized hreflang<link> tags are injected client-side by main.js's
hreflang injector from a HREFLANG_LANGS array (see
agents/instructions/common/js.instructions.md), do not look for them as
static markup in the HTML, and do not hand-add static <link rel="alternate" hreflang="..."> tags (that would duplicate what the script already injects).
When adding a locale, the array and the locale directory must be kept in
sync, not the HTML.
The data-languages JSON attribute on .language-selector elements must be
valid JSON, list every supported locale, and use correct relative paths for the
page's depth (e.g. ./, ../de/, ../../de/products/metric.html). Keep
data-active-lang in sync with the page's actual locale.
Every <img> needs alt text. Empty alt="" is only correct for a purely
decorative image.
Every page needs a <title>, a meta description, and og: / twitter: image
tags that match what the page actually shows: don't copy another page's tags
without updating them.
Use it
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 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}'
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": "omega1119-harmonic-tools-html-instructions",
"kind": "skill",
"name": "html",
"description": "Use semantic markup (`header`, `nav`, `main`, `section`, `footer`) over generic `div`s where an element already means the right thing. - Localized `hreflang` `<link>` tags are injected client-side by `main.js`'s hreflang injector from a `HREFLANG_LANGS` array (see `agents/instructions/common/js.instructions.md`), do not look for them as static markup in the HTML, and do not hand-add static `<link rel=\"alternate\" hreflang=\"...\">` tags (that would duplicate what the script already injects). When adding a locale, the array and the locale directory must be kept in sync, not the HTML. - The `data-languages` JSON attribute on `.language-selector` elements must be valid JSON, list every supported locale, and use correct relative paths for the page's depth (e.g. `./`, `../de/`, `../../de/products/metric.html`). Keep `data-active-lang` in sync with the page's actual locale. - Every `<img>` needs `alt` text. Empty `alt=\"\"` is only correct for a purely decorative image. - Every page needs a `<title>`, a meta `descriptio",
"publisher": "omega1119",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Use semantic markup (`header`, `nav`, `main`, `section`, `footer`) over generic `div`s where an element already means the right thing. - Localized `hreflang` `<link>` tags are injected client-side by `main.js`'s hreflang injector from a `HREFLANG_LANGS` array (see `agents/instructions/common/js.instructions.md`), do not look for them as static markup in the HTML, and do not hand-add static `<link rel=\"alternate\" hreflang=\"...\">` tags (that would duplicate what the script already injects). When adding a locale, the array and the locale directory must be kept in sync, not the HTML. - The `data-languages` JSON attribute on `.language-selector` elements must be valid JSON, list every supported locale, and use correct relative paths for the page's depth (e.g. `./`, `../de/`, `../../de/products/metric.html`). Keep `data-active-lang` in sync with the page's actual locale. - Every `<img>` needs `alt` text. Empty `alt=\"\"` is only correct for a purely decorative image. - Every page needs a `<title>`, a meta `descriptio"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/omega1119/harmonic-tools",
"path": ".github/instructions/html.instructions.md",
"ref": "4e8176664747472ba98cbe14b0d36e2289e618b1",
"url": "https://github.com/omega1119/harmonic-tools/blob/4e8176664747472ba98cbe14b0d36e2289e618b1/.github/instructions/html.instructions.md",
"key": "omega1119/harmonic-tools/.github/instructions/html.instructions.md"
},
"applies_to": "**/*.html"
},
"instructions": "- Use semantic markup (`header`, `nav`, `main`, `section`, `footer`) over generic\n `div`s where an element already means the right thing.\n- Localized `hreflang` `<link>` tags are injected client-side by `main.js`'s\n hreflang injector from a `HREFLANG_LANGS` array (see\n `agents/instructions/common/js.instructions.md`), do not look for them as\n static markup in the HTML, and do not hand-add static `<link rel=\"alternate\"\n hreflang=\"...\">` tags (that would duplicate what the script already injects).\n When adding a locale, the array and the locale directory must be kept in\n sync, not the HTM",
"cost": {
"context_tokens": 296
}
}
Fetch it by URL: GET /api/v1/registry/omega1119-harmonic-tools-html-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.
