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.
writing-documentation - Skill - OpenSmartRoute
Skillv1.0.0
writing-documentation
Always update existing architecture and documentation files in place. Keep the documentation factual, concise and free of speculation. Avoid editorializing or making assumptions about intent. When upd
Instruction file imported from EverlastEngineering/DrumToMIDI (.github/instructions/writing-documentation.instructions.md). Copyright stays with the author.
Always update existing architecture and documentation files in place.
Keep the documentation factual, concise and free of speculation. Avoid editorializing or making assumptions about intent.
When updating documentation, the final result should read like the it has always been this way. It should not appear like a change log, but rather a single source of truth.
When writing documentation, use present tense and active voice.
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/everlastengineering-drumtomidi-writing-documentation-ins-33ed11/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": "everlastengineering-drumtomidi-writing-documentation-ins-33ed11",
"kind": "skill",
"name": "writing-documentation",
"description": "Always update existing architecture and documentation files in place. Keep the documentation factual, concise and free of speculation. Avoid editorializing or making assumptions about intent. When updating documentation, the final result should read like the it has always been this way. It should not appear like a change log, but rather a single source of truth. When writing documentation, use present tense and active voice.",
"publisher": "EverlastEngineering",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Always update existing architecture and documentation files in place. Keep the documentation factual, concise and free of speculation. Avoid editorializing or making assumptions about intent. When updating documentation, the final result should read like the it has always been this way. It should not appear like a change log, but rather a single source of truth. When writing documentation, use present tense and active voice."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/EverlastEngineering/DrumToMIDI",
"path": ".github/instructions/writing-documentation.instructions.md",
"ref": "96d63f7faa3f6f9e218483d647a15310ef87a0e1",
"url": "https://github.com/EverlastEngineering/DrumToMIDI/blob/96d63f7faa3f6f9e218483d647a15310ef87a0e1/.github/instructions/writing-documentation.instructions.md",
"key": "EverlastEngineering/DrumToMIDI/.github/instructions/writing-documentation.instructions.md"
},
"applies_to": "**"
},
"instructions": "Always update existing architecture and documentation files in place.\nKeep the documentation factual, concise and free of speculation. Avoid editorializing or making assumptions about intent.\nWhen updating documentation, the final result should read like the it has always been this way. It should not appear like a change log, but rather a single source of truth.\nWhen writing documentation, use present tense and active voice.",
"cost": {
"context_tokens": 107
}
}
Fetch it by URL: GET /api/v1/registry/everlastengineering-drumtomidi-writing-documentation-ins-33ed11/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.
