Answers from the documentation - opens a ticket when you need a person
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.
Answers come from the docs; check anything important there.
lovable-frontend - Skill - OpenSmartRoute
Skillv1.0.0
lovable-frontend
<!-- LOVABLE:BEGIN --> > [!IMPORTANT] > This project is connected to [Lovable](https://lovable.dev). Avoid rewriting > published git history — force pushing, or rebasing/amending/squashing commits > t
Imported from Yugenjr/Decision-Probe (apps/lovable-frontend/AGENTS.md). Install upstream with npx skills add Yugenjr/Decision-Probe --skill lovable-frontend. Copyright stays with the author.
[!IMPORTANT]
This project is connected to Lovable. Avoid rewriting
published git history — force pushing, or rebasing/amending/squashing commits
that are already pushed — as it rewrites history on Lovable's side and the
user will likely lose their project history.
Commits you push to the connected branch sync back to Lovable and show up in
the editor, so keep the branch in a working state.
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/yugenjr-decision-probe-lovable-frontend/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": "yugenjr-decision-probe-lovable-frontend",
"kind": "skill",
"name": "lovable-frontend",
"description": "<!-- LOVABLE:BEGIN --> > [!IMPORTANT] > This project is connected to [Lovable](https://lovable.dev). Avoid rewriting > published git history — force pushing, or rebasing/amending/squashing commits > that are already pushed — as it rewrites history on Lovable's side and the > user will likely lose their project history. > > Commits you push to the connected branch sync back to Lovable and show up in > the editor, so keep the branch in a working state. <!-- LOVABLE:END -->",
"publisher": "Yugenjr",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"<!-- LOVABLE:BEGIN --> > [!IMPORTANT] > This project is connected to [Lovable](https://lovable.dev). Avoid rewriting > published git history — force pushing, or rebasing/amending/squashing commits > that are already pushed — as it rewrites history on Lovable's side and the > user will likely lose their project history. > > Commits you push to the connected branch sync back to Lovable and show up in > the editor, so keep the branch in a working state. <!-- LOVABLE:END -->"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-agents",
"repository": "https://github.com/Yugenjr/Decision-Probe",
"path": "apps/lovable-frontend/AGENTS.md",
"ref": "2196af8e78579db6faf8dedad032d50781ed3296",
"url": "https://github.com/Yugenjr/Decision-Probe/blob/2196af8e78579db6faf8dedad032d50781ed3296/apps/lovable-frontend/AGENTS.md",
"key": "Yugenjr/Decision-Probe/apps/lovable-frontend/AGENTS.md"
}
},
"instructions": "<!-- LOVABLE:BEGIN -->\n> [!IMPORTANT]\n> This project is connected to [Lovable](https://lovable.dev). Avoid rewriting\n> published git history — force pushing, or rebasing/amending/squashing commits\n> that are already pushed — as it rewrites history on Lovable's side and the\n> user will likely lose their project history.\n>\n> Commits you push to the connected branch sync back to Lovable and show up in\n> the editor, so keep the branch in a working state.\n<!-- LOVABLE:END -->",
"cost": {
"context_tokens": 118
}
}
Fetch it by URL: GET /api/v1/registry/yugenjr-decision-probe-lovable-frontend/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.
