ce-fallback-impl

Emit UserWarning and INFO log for every fallback path in calibrated_explanations.

78|15|Updated May 1, 2023
One-click install
npx skills add https://github.com/Moffran/calibrated_explanations --skill ce-fallback-impl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-fallback-impl
Source: https://github.com/Moffran/calibrated_explanations/tree/main/.claude/skills/ce-fallback-impl
Command: npx skills add https://github.com/Moffran/calibrated_explanations --skill ce-fallback-impl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement a mandated visible fallback policy where every fallback path emits both a UserWarning and an INFO log to ensure users are aware of recoverable actions.

Core Features & Use Cases

  • Enforces visibility by emitting a UserWarning and logging an INFO message for every fallback path.
  • Provides patterns for common fallback scenarios (parallel → sequential, plugin not found → legacy path, visualization simplification) with correct stacklevel handling.
  • Includes testing guidance ensuring warnings are raised and logs are captured in supported paths.

Quick Start

Trigger a failing parallel backend to observe the mandatory UserWarning and INFO log.

Frequently Asked Questions about ce-fallback-impl

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure fallback paths emit both a UserWarning and an INFO log?

To ensure fallback paths emit a UserWarning and an INFO log, implement a visible fallback mechanism that guarantees both outputs are triggered whenever a recoverable action occurs. This enforces user awareness of runtime fallback decisions.

What is the best way to handle missing plugins and fallback to a legacy path?

Handling missing plugins requires a fallback to a legacy path that emits a UserWarning and an INFO log. This visible fallback pattern ensures users are immediately alerted to the missing plugin and the subsequent switch to legacy execution.

How do I test that warnings and logs are raised correctly during a fallback?

Testing fallback warnings and logs involves verifying that both a UserWarning is raised and an INFO message is captured during fallback execution. The mechanism includes testing guidance to ensure proper stacklevel handling and testable messaging.

Does this fallback mechanism work with calibrated explanations visualizations?

Yes, the fallback mechanism works with calibrated explanations by handling visualization simplification failures. It emits a UserWarning and an INFO log across core, plugins, and governance code to maintain visibility during visual fallbacks.