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.
Use when adding, renaming, or replacing screenshot assets for Meinhardt tool descriptions so naming, placement, and screenshot type remain standardized.
Instruction file imported from GMDS22/MHTTools.extension-v2 (.github/instructions/meinhardt-tool-description-assets.instructions.md). Copyright stays with the author.
Store tool-description screenshots in this folder and follow the standard naming rules from docs/MHTTools-Tool-Description-Standard.md.
Asset rules:
Use PNG for UI screenshots.
Prefer these filename patterns:
ui-.png
ui--LargeUI.png
ui--step1.png, ui--step2.png, ui--step3.png
panel-.png
Use lowercase kebab-case slugs for new files.
Do not introduce new dot-separated LargeUI variants; keep new files on the hyphenated pattern.
Replace placeholders with real screenshots whenever a tool has a user-facing interface.
Keep filenames stable once referenced in MeinhardtTabTools.html unless the HTML is updated in the same change.
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/gmds22-mhttools-extension-v2-meinhardt-tool-description-39d778/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": "gmds22-mhttools-extension-v2-meinhardt-tool-description-39d778",
"kind": "skill",
"name": "meinhardt-tool-description-assets",
"description": "Use when adding, renaming, or replacing screenshot assets for Meinhardt tool descriptions so naming, placement, and screenshot type remain standardized.",
"publisher": "GMDS22",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Use when adding, renaming, or replacing screenshot assets for Meinhardt tool descriptions so naming, placement, and screenshot type remain standardized."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/GMDS22/MHTTools.extension-v2",
"path": ".github/instructions/meinhardt-tool-description-assets.instructions.md",
"ref": "7fe791c0ac8ec69200d2419c49cd9f8c979b39e5",
"url": "https://github.com/GMDS22/MHTTools.extension-v2/blob/7fe791c0ac8ec69200d2419c49cd9f8c979b39e5/.github/instructions/meinhardt-tool-description-assets.instructions.md",
"key": "GMDS22/MHTTools.extension-v2/.github/instructions/meinhardt-tool-description-assets.instructions.md"
},
"applies_to": "MEINHARDT.tab/Documentation.panel/ToolsDescription.pushbutton/**"
},
"instructions": "Store tool-description screenshots in this folder and follow the standard naming rules from docs/MHTTools-Tool-Description-Standard.md.\n\nAsset rules:\n- Use PNG for UI screenshots.\n- Prefer these filename patterns:\n - ui-<tool>.png\n - ui-<tool>-LargeUI.png\n - ui-<tool>-step1.png, ui-<tool>-step2.png, ui-<tool>-step3.png\n - panel-<tool>.png\n- Use lowercase kebab-case slugs for new files.\n- Do not introduce new dot-separated LargeUI variants; keep new files on the hyphenated pattern.\n- Replace placeholders with real screenshots whenever a tool has a user-facing interface.\n- Keep filenames sta",
"cost": {
"context_tokens": 173
}
}
Fetch it by URL: GET /api/v1/registry/gmds22-mhttools-extension-v2-meinhardt-tool-description-39d778/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.
