midaz-shared

Name: midaz-shared
Availability: InStock
Author: Sparkss

Centralize authentication, response formatting, and safety rules for Midaz CLI skills.

Updated Mar 30, 2026

Search Tags:#security #cli #auth #market #desk #response-format #midaz

Ready to run

npx skills add https://github.com/SparkssL/Midaz-cli --skill midaz-shared

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: midaz-shared
Source: https://github.com/SparkssL/Midaz-cli/tree/main/skills/midaz-shared
Command: npx skills add https://github.com/SparkssL/Midaz-cli --skill midaz-shared

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes foundational Midaz concepts that underpin all midaz-* skills, ensuring consistency in auth, response formats, and governance across the desk, market, and tooling.

Core Features & Use Cases

Establishes a single auth model, response envelope, global flags, and safety rules used by every midaz skill.
Guides CLI behavior and cross-skill conventions to reduce integration friction for developers and agents.
Use case: a developer adds a new midaz-* skill and immediately inherits the shared patterns for auth, data formatting, and error handling.

Quick Start

Start by reading this skill to align authentication, response formats, and safety rules across all Midaz CLI skills.

Frequently Asked Questions about midaz-shared

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

FAQPage Schema

How do I unify authentication and response formatting across multiple CLI skills?▼

To unify CLI authentication and response formatting, use a centralized shared skill that enforces a single auth model and standard data envelopes across all commands. This ensures consistent behavior and reduces integration friction for developers.

What are safety rules in CLI command workflows?▼

Safety rules in CLI command workflows are enforced governance policies that standardize error handling and data formatting across desk, market, and intel tasks, ensuring consistent and secure command execution throughout the system.

Do I need a YAML frontmatter in SKILL.md to standardize CLI behavior?▼

Yes, standardizing CLI behavior requires a SKILL.md file that includes a YAML frontmatter with name and description fields. This enforces structural consistency across the skill set.

How do I handle errors consistently across different CLI commands?▼

To handle errors consistently across different CLI commands, apply a shared response envelope that standardizes error formatting across all workflows. This provides uniform error handling throughout desk, market, and intel operations.

Can I use optional resource directories with shared CLI concepts?▼

Yes, shared CLI concepts support optional resource directories in scripts/, references/, and assets/ when present in the skill structure. This allows you to extend functionality while maintaining core conventions.

Why does my new CLI skill have inconsistent authentication behavior?▼

New CLI skills have inconsistent authentication behavior when they do not inherit shared foundational concepts. Applying a centralized skill enforces a single auth model and global flags, resolving these integration inconsistencies.