mindspeed-fsdp2-verification

Automates end-to-end verification of MindPress FS2DP migrations with evidence capture.

31|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/Ascend/agent-skills --skill mindspeed-fsdp2-verification
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mindspeed-fsdp2-verification
Source: https://github.com/Ascend/agent-skills/tree/main/skills/mindspeed-mm-fsdp2-migration/mindspeed-fsdp2-verification
Command: npx skills add https://github.com/Ascend/agent-skills --skill mindspeed-fsdp2-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MindSpeed FSDP2 migration verification provides gates to ensure functional and reliability checkpoints after migrations, documenting verifiable evidence for end-to-end success.

Core Features & Use Cases

  • Functional and reliability gate enforcement for model, data, and config migrations, with evidence capture.
  • End-to-end distributed verification runs and traceable reporting to support auditability.
  • Reusable templates and artifacts (verification_report.md, evidence.json) to hand off results.

Quick Start

Run the verification workflow with your migrated artifacts and available logs to generate a verification report.

Frequently Asked Questions about mindspeed-fsdp2-verification

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

FAQPage Schema
How do I verify a MindSpeed FSDP2 migration?▼

MindSpeed FSDP2 migration verification requires at least one distributed end-to-end run with documented results to successfully pass functional and reliability gates for migrated artifacts.

What evidence do I need for an end-to-end FSDP2 migration verification?▼

End-to-end FSDP2 migration verification captures evidence by recording commands and exit codes, ultimately producing a verification_report.md and an evidence.json file for full traceability and auditability.

Can I use this verification process for model, data, and config migrations?▼

Yes, this verification process applies directly to migrated model, data, and configuration artifacts, enforcing functional and reliability gates across all these components during the end-to-end distributed run.

What is the best way to document functional gates after an FSDP2 migration?▼

The best way to document functional gates after an FSDP2 migration is to use reusable templates that generate traceable reporting artifacts, specifically a verification_report.md and an evidence.json file.

Why do I need a distributed end-to-end run for FSDP2 verification?▼

A distributed end-to-end run is required for FSDP2 verification to ensure that functional and reliability checkpoints are met across the entire migrated stack, providing documented evidence of success.