Name: lra
Author: wsollers

Instruction file imported from wsollers/lra-notes (.github/instructions/lra.instructions.md). Copyright stays with the author.

LRA Repository Instructions

This repository uses canonical LRA governance by pointer, not by copied rules.

Repository: lra-notes Canonical repo overlay: capabilities/overlays/lra-notes.md Canonical route resolver: python <governance-root>/scripts/govpy.py capabilities/resolve.py --repo lra-notes --task "<user task>" --root <repo-root> Human route index (lazy reference only): capabilities/task-index.md

Resolve canonical governance in this order:

LRA_GOVERNANCE_ROOT;
sibling ../lra-governance;
an explicit lra-governance checkout supplied by the build image or task.

If canonical governance cannot be resolved, stop and report that lra-governance is not present.

Follow AGENTS.md in this repository as the local pointer wrapper, then run the resolver. Do not treat this file as a local source of truth.

Provider note: Keep provider-specific guidance concise and defer durable policy to canonical governance.

# 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}'

Install lra 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.

{ "ocm": "1", "id": "wsollers-lra-notes-lra-instructions", "kind": "skill", "name": "lra", "description": "Source repo: wsollers/lra-governance Canonical overlay: capabilities/overlays/lra-notes.md", "publisher": "wsollers", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github-instructions" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Source repo: wsollers/lra-governance Canonical overlay: capabilities/overlays/lra-notes.md" ], "primary": false, "metadata": { "source": { "provider": "github-instructions", "repository": "https://github.com/wsollers/lra-notes", "path": ".github/instructions/lra.instructions.md", "ref": "e107a025f209096130a4e1e315be97daf36b109d", "url": "https://github.com/wsollers/lra-notes/blob/e107a025f209096130a4e1e315be97daf36b109d/.github/instructions/lra.instructions.md", "key": "wsollers/lra-notes/.github/instructions/lra.instructions.md" } }, "instructions": "\n\n# LRA Repository Instructions\n\nThis repository uses canonical LRA governance by pointer, not by copied rules.\n\nRepository: `lra-notes`\nCanonical repo overlay: `capabilities/overlays/lra-notes.md`\nCanonical route resolver:\n`python <governance-root>/scripts/govpy.py capabilities/resolve.py --repo lra-notes --task \"<user task>\" --root <repo-root", "cost": { "context_tokens": 300 } }

lra

About

LRA Repository Instructions

Use it

Install lra and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews