minimax-secrets-chit

Map GitHub Secrets, Vault, and Supabase into CHIT manifests without cleartext.

6|Updated Aug 26, 2025
One-click install
npx skills add https://github.com/POWERFULMOVES/PMOVES.AI --skill minimax-secrets-chit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: minimax-secrets-chit
Source: https://github.com/POWERFULMOVES/PMOVES.AI/tree/main/.kilocode/skills/minimax-secrets-chit
Command: npx skills add https://github.com/POWERFULMOVES/PMOVES.AI --skill minimax-secrets-chit

SYSTEM DOCUMENTATION & REQUIREMENTS

Map secrets stores into CHIT manifests without cleartext commits for PMOVES infrastructure. This skill should be used when syncing GitHub secrets, vault labels, or Supabase runtime values to CHIT manifests.

What problem does it solve?

Secret data often needs to be propagated across PMOVES environments without exposing plaintext credentials. This skill enables safe transformation of secrets from GitHub Secrets, Vault, and Supabase into CHIT manifests suitable for versioned deployment.

Core Features & Use Cases

  • Map GitHub secrets to CHIT manifest entries
  • Correlate vault labels to secret references
  • Sync Supabase runtime environment values
  • Never expose cleartext secrets in commits
  • Generate verification reports for audit

Quick Start

Run the minimax secrets CHIT workflow to generate a non-cleartext manifest from your secret sources.

Frequently Asked Questions about minimax-secrets-chit

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

FAQPage Schema
How do I map GitHub secrets to a deployment manifest without exposing cleartext values?

To map GitHub secrets to a deployment manifest without exposing cleartext, this Skill securely references secret sources and generates environments-aware manifest entries, ensuring sensitive values are never committed in plaintext for verifiable deployment and audit processes.

What is the best way to sync Supabase runtime values to CHIT manifests for versioned deployment?

The best way to sync Supabase runtime values to CHIT manifests is to securely map the runtime environment values from Supabase into environments-aware manifest entries, avoiding plaintext credentials while producing verifiable manifests for versioned deployment workflows.

Does this approach support correlating Vault labels with secret references for audit reports?

Yes, this approach supports correlating Vault labels with secret references. It securely maps the Vault labels into CHIT manifests and can generate verification reports specifically designed to satisfy audit requirements without exposing sensitive values.

Can I use this to generate verification reports for secrets mapped across multiple environments?

Yes, you can use this to generate verification reports for secrets mapped across multiple environments. It applies the secret mapping across your specified environments to produce verifiable manifests and corresponding reports tailored for audit workflows.

How do I avoid plaintext secret commits when propagating data across infrastructure environments?

To avoid plaintext secret commits when propagating data across infrastructure environments, securely map the secret data from your sources into CHIT manifests by referencing the sources rather than copying the values, producing safe, environments-aware entries for versioned deployment.