.claude/skills/pontx-frankfurterRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Maintain legacy Frankfurter v1 integrations through Pontx. Use for existing v1 applications, reproducible dated reference-rate work, or deciding whether new provider-aware work should move to pontx-frankfurter-v2.
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/pontx-frankfurterRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/pontx-frankfurterRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/pontx-frankfurterRuntime, 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 @pontjs/pontx-frankfurterclawhub inspect @pontjs/pontx-frankfurter --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:31aeb2d7731d79cc7a2625651e1082d9d2d1b7cda4dbe1ae7b4a048dd76c43baskill-card.mdSKILL.mdpontx-frankfurter 1.0.0 - Initial release. - Provides legacy Frankfurter v1 integration for backward compatibility through Pontx. - Suitable for existing v1 applications, reproducible reference-rate requests, or evaluating migration to v2. - Guidance included for contract selection, safe request handling, and maintaining v1-specific semantics. - Recommended for single-product scripts or when strict v1 compatibility is required.