.claude/skills/render-on-hermesRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Use whenever any other render-* skill loads, or any time the user asks you to do something on Render. Tells you that this Hermes container has the Render MCP server pre-registered with full MCP tool access for the provided API key and that the `render` CLI is NOT installed in this image, so skip every "install MCP", "install CLI", and "run render CLI" step that upstream render-* skills describe.
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/render-on-hermesRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/render-on-hermesRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/render-on-hermesRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @ojusave/render-on-hermesclawhub inspect @ojusave/render-on-hermes --version 0.1.0This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:1697d84bef09fdd51ca8e62157b51bb4b3619b88c99cf5f9cd0cf292e654a872SKILL.mdInitial release of render-on-hermes: - Provides pre-registered Render MCP server with full MCP tool access using the provided API key. - Clarifies that the `render` CLI is NOT installed; skip all CLI installation and CLI command execution steps. - Explains which upstream skill instructions to ignore or adapt for this Hermes-based environment. - Details steps for workspace selection and using MCP-prefixed tool names. - Provides guidance for handling render-cli-specific tasks and what to do if a CLI-only feature is requested. - Describes how to verify that MCP is functioning and general troubleshooting steps.