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.
* - Skill - OpenSmartRoute
Skillv1.0.0
*
Your primary goal with this review is attention to detail. Particularly look for where code can be simplified or standardised. For example:
Instruction file imported from pento/claudaborative-editing (.github/instructions/*.instructions.md). Copyright stays with the author.
PR Review Instructions
Your primary goal with this review is attention to detail. Particularly look for where code can be simplified or standardised. For example:
Values that are used repeatedly in similar contexts, that could be turned into CONSTs.
Repeated code patterns that would be better placed in a common library.
Overly complicated type casting or coercing, that could be handled in a more central location.
Documentation and PR Description consistency - sometimes the PR functionality will stray from the initially documented behaviour, the documentation is usually what needs updated.
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/pento-claudaborative-editing-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": "pento-claudaborative-editing-instructions",
"kind": "skill",
"name": "*",
"description": "Your primary goal with this review is attention to detail. Particularly look for where code can be simplified or standardised. For example:",
"publisher": "pento",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Your primary goal with this review is attention to detail. Particularly look for where code can be simplified or standardised. For example:"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/pento/claudaborative-editing",
"path": ".github/instructions/*.instructions.md",
"ref": "aad263b79c87fc1748438651ebb86f5174644646",
"url": "https://github.com/pento/claudaborative-editing/blob/aad263b79c87fc1748438651ebb86f5174644646/.github/instructions/*.instructions.md",
"key": "pento/claudaborative-editing/.github/instructions/*.instructions.md"
}
},
"instructions": "# PR Review Instructions\n\nYour primary goal with this review is attention to detail. Particularly look for where code can be simplified or standardised. For example:\n\n- Values that are used repeatedly in similar contexts, that could be turned into CONSTs.\n- Repeated code patterns that would be better placed in a common library.\n- Overly complicated type casting or coercing, that could be handled in a more central location.\n- Documentation and PR Description consistency - sometimes the PR functionality will stray from the initially documented behaviour, the documentation is usually what needs u",
"cost": {
"context_tokens": 151
}
}
Fetch it by URL: GET /api/v1/registry/pento-claudaborative-editing-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.
