.claude/skills/expflow-pipeline-hpoRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
PDEBench competition workflow orchestration with expflow — three pipeline modes (full/fast/skip), distributed HPO, pruner integration, and ClearML HyperParameterOptimizer native mode.
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/expflow-pipeline-hpoRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/expflow-pipeline-hpoRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/expflow-pipeline-hpoRuntime, 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 @diamond2nv/expflow-pipeline-hpoclawhub inspect @diamond2nv/expflow-pipeline-hpo --version 0.7.2This 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:1c8d30b0b8dc772c088bafba65f018a02fb5bb61a8debc5b2674f05db46b6451skill-card.mdSKILL.mdCross-link the Exo suite (entry skill `exo-suite-linkage`: literature → experiments → proofs, cost tiers low → medium → high) · pin `uvx` launch versions (rug-pull hygiene; `uvx` otherwise reuses an installed tool env and can run an older release).
Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.
These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.
sha256:baa4d2da77b2bff58c9561147691b9102778eefefc4fcf05041a41910b3a2c9a