aov-mingyu-api

Retrieve structured divination API outputs for bazi, ziwei, tarot, and qimen workflows.

199|43|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/tradecatlabs/fatecat --skill aov-mingyu-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aov-mingyu-api
Source: https://github.com/tradecatlabs/fatecat/tree/main/tools/reference-repos/github/mingyu-main/public/skills/aov-mingyu-api
Command: npx skills add https://github.com/tradecatlabs/fatecat --skill aov-mingyu-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you call a structured divination and astrology API without manually figuring out endpoints, parameters, or response formats. It is designed for users who need reliable, machine-readable outputs for bazi, ziwei, tarot, qimen, liuyao, and related fortune-telling workflows.

Core Features & Use Cases

  • Unified API Access: Query the service manifest, health status, and OpenAPI schema before choosing an endpoint.
  • Multi-Domain Divination: Generate structured results for eight-character astrology, purple star astrology, tarot, I Ching, Qimen Dunjia, Liu Ren, Lenormand, and almanac selection.
  • Prompt-Ready Outputs: Use /prompt endpoints to obtain both calculation results and AI-friendly interpretation prompts in one response.
  • Use Case: An agent can request a career analysis, receive normalized chart data, and then produce an evidence-based interpretation without inventing missing details.

Quick Start

Ask the skill to inspect the API manifest and then generate the correct request for a bazi, ziwei, or divination prompt endpoint based on my question and input data.

Frequently Asked Questions about aov-mingyu-api

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

FAQPage Schema
How do I get structured API outputs for bazi and tarot divination workflows?

You can retrieve structured API outputs for bazi and tarot by querying the service manifest, validating parameters, and calling the normalized machine-readable endpoints to receive calculation results and interpretation prompts.

Can I generate AI interpretation prompts directly from astrology API responses?

Yes, you can use the `/prompt` endpoints to obtain both chart calculation results and AI-friendly interpretation prompts in a single response, enabling agentic analysis without inventing missing details.

What's the best way to integrate divination APIs like ziwei and qimen into an automated agent?

The best way to integrate ziwei and qimen divination APIs is to inspect the OpenAPI schema, validate input parameters, and handle prompt-oriented responses to ensure consistent machine-readable API integration for your agent.

Does this divination API support multiple fortune-telling methods or just eight-character astrology?

The divination API supports multiple fortune-telling methods, including bazi, ziwei, tarot, qimen, liuyao, liu ren, lenormand, and almanac selection, providing normalized outputs across all supported domains.

Why do I need endpoint discovery before calling fortune-telling and astrology APIs?

Endpoint discovery is required before calling fortune-telling APIs to verify the service health status, identify the correct OpenAPI schema, and validate parameters, ensuring reliable and consistent response handling for your divination workflows.

Are there limitations when using prompt generation for I Ching and liuyao chart calculations?

Prompt generation for I Ching and liuyao requires strict parameter validation and endpoint discovery, and while outputs are normalized, you must handle prompt-oriented responses carefully to avoid misinterpreting the machine-readable chart data.