menuyukti-analytics

Author and consume analytics with DataFrame contracts and GraphQL integration.

Updated Nov 16, 2025
One-click install
npx skills add https://github.com/daniel-dihardja/menuyukti --skill menuyukti-analytics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: menuyukti-analytics
Source: https://github.com/daniel-dihardja/menuyukti/tree/main/.agents/skills/menuyukti-analytics
Command: npx skills add https://github.com/daniel-dihardja/menuyukti --skill menuyukti-analytics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Author and consume analytics in the shared MenuYukti Python package, standardizing DataFrame contracts, pipeline calculations, Instagram signal composition, weekly demand patterns, and boundaries with apps/graphql to speed analytics work.

Core Features & Use Cases

  • Analytics modules for DataFrame contracts, calculate_/compute__from_orders pipelines, Instagram signals, and weekly demand patterns.
  • Clear boundaries with GraphQL integration and a registry/helper structure to support scalable analytics development.
  • Companion skills: pandas-pro for data manipulation and python-design-patterns for clean, modular design.

Quick Start

Inspect the analytics modules under packages/menuyukti/src/menuyukti/core/analytics to identify available pipelines and contracts.

Frequently Asked Questions about menuyukti-analytics

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

FAQPage Schema
How do I build analytics pipelines for sales trends and category mix using DataFrame contracts?

Analytics pipelines for sales trends and category mix are built using standardized DataFrame contracts and calculate_*/compute_*_from_orders modules. They enforce typed interfaces and standardized exports to ensure consistent analytics development across shared Python packages.

What is the best way to integrate weekly demand patterns and Instagram signals into a GraphQL analytics payload?

Integrating weekly demand patterns and Instagram signals into GraphQL payloads requires clear boundaries with apps/graphql alongside a registry/helper structure. This supports scalable analytics development and standardized exports for agent-facing payloads.

How do I author menu engineering analytics without breaking existing operating profile pipelines?

Authoring menu engineering analytics requires using standardized DataFrame contracts and compute pipelines within the shared analytics package. This enforces typed interfaces and standardized exports to maintain operating profile pipeline integrity during changes.

Can I use Python design patterns and pandas to manage complex revenue trend calculations?

Managing complex revenue trend calculations uses pandas for data manipulation and python-design-patterns for clean, modular design. These companion skills guide implementation of calculate_*/compute_*_from_orders pipelines within the analytics package.

Does the analytics package support adding new agent-facing analytics payloads alongside existing modules?

Adding agent-facing analytics payloads is supported through a registry/helper structure with clear GraphQL integration boundaries. This structure enforces typed interfaces and standardized exports across analytics modules for scalable development.

What limitations exist when modifying DataFrame contracts for category mix and revenue trend pipelines?

Modifying DataFrame contracts for category mix and revenue trends requires maintaining standardized exports and typed interfaces across all analytics modules. Breaking these contracts disrupts GraphQL integration and existing Instagram signal composition pipelines.