Hyperliquid perps strategist: market scans, funding rates, position sizing, and user-signed EIP-712 order execution & cancellation with drawdown guardrails.
Identity and source
Publisher attributionFarmDashregistry owner unverified by skillvetai
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.
This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
Status
completed
Coverage
full text content
Files
4 / 4 inspected as text
Checked
11/5/2026, 8:01:08 PM
Scanner
0.1.3
Policy
1.0.3
2 inferred permission indicators
network access — automatically inferred
filesystem write — automatically inferred
4 dependency and API indicators
api: api.hyperliquid.xyz
api: clawhub.ai
api: json-schema.org
api: www.farmdash.one
External clawhub result: clean
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.
Evidence checked
11/5/2026, 9:10:15 AM
Release binding
Matches this record
skillspector: suspicious
llm: clean
Recorded files
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
Adds Scout execution allowances and expanded futures execution controls. - Defines separate daily Scout futures and spot lifecycle pools, with owner-bound identity, admission checks, and handling for accepted, rejected, or ambiguous submissions. - Adds read-only continuation selection for stored execution context; selected context does not grant authorization or guarantee capacity. - Documents USER_SIGNED and BOUNDED_AUTONOMOUS execution requirements, including owner-signed policy setup and ongoing authority checks. - Removes `skill-card.md`.
Release security diff
mediumCompared fixed releases 1.0.27 and 1.0.29; 0 finding and 0 permission indicators were added.
Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.
Change reasons and limitations
content hash changed
Observed release history
These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.