attest

Calculate reliability metrics from the last 10 trials in reliability-log.jsonl files.

2|1|Updated May 2, 2026
One-click install
npx skills add https://github.com/iroh4-labs/mumei --skill attest-iroh4-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: attest
Source: https://github.com/iroh4-labs/mumei/tree/main/skills/attest
Command: npx skills add https://github.com/iroh4-labs/mumei --skill attest-iroh4-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a quick and detailed reliability assessment for a specified mumei feature, helping users determine if it's stable enough for deployment.

Core Features & Use Cases

  • Reliability Assessment: Computes a reliability metric based on the last 10 trials of a feature.
  • Feature-Specific Analysis: Allows users to focus on specific features, providing a tailored reliability view.
  • Use Case: When considering a feature for production, use this Skill to quickly check its stability and reliability before deployment.

Quick Start

Assess the reliability of the 'REQ-N-123' feature by running: /mumei:attest REQ-N-123

Frequently Asked Questions about attest

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

FAQPage Schema
How do I assess feature reliability for a specific mumei feature?

Feature reliability is assessed by analyzing the most recent 10 trials from the 'reliability-log.jsonl' file within the feature's directory. The Skill calculates the arithmetic mean of pass rates to provide a detailed stability metric.

Can I check feature stability before production deployment?

Feature stability is checked by computing a reliability metric from recent trial logs. This helps determine if a specific feature is stable enough for production deployment.

What is the best way to calculate pass rates from reliability logs?

Pass rates are calculated using the arithmetic mean of the last 10 trial results. This requires accessing the 'reliability-log.jsonl' file located in the target feature's directory.

Do I need specific log files to evaluate mumei feature stability?

Evaluating mumei feature stability requires access to 'reliability-log.jsonl' files within the feature's directory. Without these trial logs, the reliability metric cannot be computed.

Are there limitations when assessing feature reliability with recent trials?

Assessing feature reliability is limited to analyzing only the most recent 10 trials. If the 'reliability-log.jsonl' file lacks sufficient trial history, the stability metric may not reflect long-term trends.