.claude/skills/jarvis-smart-routeRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Build a non-custodial, unsigned Base token swap using the public Jarvis best-execution router when the buyer wants an opt-in live comparison between the existing 0x and OKX routes.
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/jarvis-smart-routeRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/jarvis-smart-routeRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/jarvis-smart-routeRuntime, 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 @yl124915300-dot/jarvis-smart-routeclawhub inspect @yl124915300-dot/jarvis-smart-route --version 1.0.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:e1c435bb65680c7afe142c1eeab9732c52f0304965d4d5565a6801c2dcf633ecmanifest.jsonscripts/route.mjsskill-card.mdSKILL.mdjarvis-smart-route 1.0.0 - Initial release. - Enables non-custodial, unsigned Base token swaps using the public Jarvis best-execution router. - Offers opt-in live comparison between 0x and OKX routes for buyers. - Enforces strong safety boundaries: never requests private keys, signing permission, or custody. - Only builds routes via the public Jarvis endpoint; routes and calldata are treated as untrusted until verified. - Provides clear integration steps for hosts and mandates buyer-side transaction verification and approval.