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.
HA-LightDash - Skill - OpenSmartRoute
Skillv1.0.0
HA-LightDash
When making changes, ALWAYS: 1. Bump the version in `addons/lightdash/config.yaml` 2. Update `addons/lightdash/CHANGELOG.md` with a technical summary of what changed 3. Update `RELEASE.md` with a user
Imported from richkershaw/HA-LightDash (AGENTS.md). Install upstream with npx skills add richkershaw/HA-LightDash. Copyright stays with the author.
Instructions
Version bumps, commits, and pushes
When making changes, ALWAYS:
Bump the version in addons/lightdash/config.yaml
Update addons/lightdash/CHANGELOG.md with a technical summary of what changed
Update RELEASE.md with a user-friendly, non-technical summary — brief intro sentence categorising the type of change, then bulletpoints describing what it means for the user (not implementation details). One section per PR to main — consolidate all changes since the last release, do not group by intermediate version bumps. Lead with a header like # Release Notes for v0.0.0 (YYYY-MM-DD) followed by a natural one-sentence intro summarising the release, then bulletpoints.
Commit the changes with a descriptive message including the new version
Push to the current branch
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": "richkershaw-ha-lightdash-ha-lightdash",
"kind": "skill",
"name": "HA-LightDash",
"description": "When making changes, ALWAYS: 1. Bump the version in `addons/lightdash/config.yaml` 2. Update `addons/lightdash/CHANGELOG.md` with a technical summary of what changed 3. Update `RELEASE.md` with a user-friendly, non-technical summary — brief intro sentence categorising the type of change, then bulletpoints describing what it means for the user (not implementation details). **One section per PR to `main`** — consolidate all changes since the last release, do not group by intermediate version bumps. Lead with a header like `# Release Notes for v0.0.0 (YYYY-MM-DD)` followed by a natural one-sentence intro summarising the release, then bulletpoints. 4. Commit the changes with a descriptive message including the new version 5. Push to the current branch",
"publisher": "richkershaw",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"When making changes, ALWAYS: 1. Bump the version in `addons/lightdash/config.yaml` 2. Update `addons/lightdash/CHANGELOG.md` with a technical summary of what changed 3. Update `RELEASE.md` with a user-friendly, non-technical summary — brief intro sentence categorising the type of change, then bulletpoints describing what it means for the user (not implementation details). **One section per PR to `main`** — consolidate all changes since the last release, do not group by intermediate version bumps. Lead with a header like `# Release Notes for v0.0.0 (YYYY-MM-DD)` followed by a natural one-sentence intro summarising the release, then bulletpoints. 4. Commit the changes with a descriptive message including the new version 5. Push to the current branch"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-agents",
"repository": "https://github.com/richkershaw/HA-LightDash",
"path": "AGENTS.md",
"ref": "3ea0b1ff40e5c2824d275f2a0246df30f8379867",
"url": "https://github.com/richkershaw/HA-LightDash/blob/3ea0b1ff40e5c2824d275f2a0246df30f8379867/AGENTS.md",
"key": "richkershaw/HA-LightDash/AGENTS.md"
}
},
"instructions": "# Instructions\n\n## Version bumps, commits, and pushes\n\nWhen making changes, ALWAYS:\n1. Bump the version in `addons/lightdash/config.yaml`\n2. Update `addons/lightdash/CHANGELOG.md` with a technical summary of what changed\n3. Update `RELEASE.md` with a user-friendly, non-technical summary — brief intro sentence categorising the type of change, then bulletpoints describing what it means for the user (not implementation details). **One section per PR to `main`** — consolidate all changes since the last release, do not group by intermediate version bumps. Lead with a header like `# Release Notes fo",
"cost": {
"context_tokens": 203
}
}
Fetch it by URL: GET /api/v1/registry/richkershaw-ha-lightdash-ha-lightdash/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.
