Skip to content
Back to skills

Pinn Recovery Evaluation

ASecurity

Convert PINN traces into numeric proxy metrics and mechanism checks for validator-ready recovery evidence.

  • 247 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 9, 2026
toolspython

Security analysis

A100/100

Scanned September 9, 2026

npx -y skills add VectorSpaceLab/AREX-Skill --skill pinn_recovery_evaluation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pinn Recovery Evaluation?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pinn Recovery Evaluation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-pinn-recovery-evaluation/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-pinn-recovery-evaluation)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
---
name: pinn_recovery_evaluation
description: Convert PINN traces into numeric proxy metrics and mechanism checks for validator-ready recovery evidence.
---

# PINN Recovery Evaluation

Use this skill after a PINN experiment command has produced a data item, training trace, and generated-skill invocation evidence. It decides whether the trace proves the declared full or reduced target. Do not use it to train the model or compute PDE derivatives.

## Inputs
- Module-plan target metadata.
- Training trace with loss components and before/after parameters.
- Data item and source-manifest metadata.
- Generated-skill invocation evidence.

## Outputs
- Numeric metrics such as `loss_reduction` and `relative_loss_reduction`.
- Mechanism checks covering data construction, residual computation, composite loss, optimizer update, source boundary, and reduced/full runtime status.
- Recovery-result fields aligned with `module_plan.json.fast_recovery_target`.

## Workflow
1. Load the training trace and compute loss-reduction metrics.
2. Confirm parameter or optimizer-state change evidence.
3. Build mechanism checks for all claimed modules.
4. Preserve target metadata exactly from the module plan.
5. Emit validator-compatible recovery fields.

## Validation
Run `python tests/test_recovery_evaluation.py` or validate with the Distiller skill validator.

## Limitations
This skill accepts reduced recovery only when mechanism checks are explicit. Full paper-scale claims require separate runtime evidence.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…