sias-audit

Cross-check source entities, ledger, and UI to audit user score integrity.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/QuicksilverSlick/Metabolic-reset --skill sias-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sias-audit
Source: https://github.com/QuicksilverSlick/Metabolic-reset/tree/main/.claude/skills/sias-audit
Command: npx skills add https://github.com/QuicksilverSlick/Metabolic-reset --skill sias-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The SIAS audit identifies and resolves discrepancies in a user's score by cross-checking source entities, the ledger, and the UI display to preserve trust and accuracy across the 28-Day Metabolic Reset.

Core Features & Use Cases

  • Cross-reference DailyScoreEntity, WeeklyBiometricEntity, UserProgressEntity, and recruits index to verify points.
  • Generate actionable remediation recommendations with full traceability for each discrepancy.
  • Suitable for single-user investigations or batch audits of multiple users.

Quick Start

Provide the target user's name to initiate the SIAS audit and receive a structured discrepancy report.

Frequently Asked Questions about sias-audit

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

FAQPage Schema
How do I audit score integrity discrepancies in a metabolic reset tracking system?

Score integrity auditing cross-checks source entities, the transaction ledger, and UI display points to identify mismatches and generate a traceable remediation report. This preserves data accuracy across the metabolic reset program.

Why does the UI display show different biometric points than the ledger?

Cached UI points diverge from ledger transactions when source entities like DailyScoreEntity or WeeklyBiometricEntity fail to sync properly. A discrepancy analysis traces the exact divergence point across these data layers.

How do I cross-reference source entities and the ledger to verify user points?

Provide a target user's name to initiate the audit, which maps DailyScoreEntity and WeeklyBiometricEntity records against ledger transactions to verify points. This yields a structured discrepancy report for that specific user.

Can I perform a batch audit for multiple users in the 28-Day Metabolic Reset?

Yes, the audit supports both single-user investigations and batch processing of multiple users. Batch audits identify score discrepancies across the entire recruits index to preserve systemic data integrity.

What are the limitations of auditing score discrepancies without source entity traceability?

Without source entity traceability, findings cannot map to ledger transactions or cached UI points, preventing concrete remediation steps. Full traceability across all data layers is required to preserve audit integrity.