Analyze crop planning data models across stock templates and live plans.
npx skills add https://github.com/tylermorganme/crop_plan_2025 --skill crop-data
Please help me install this Agent Skill. Skill: crop-data Source: https://github.com/tylermorganme/crop_plan_2025/tree/main/.claude/skills/crop-data Command: npx skills add https://github.com/tylermorganme/crop_plan_2025 --skill crop-data
This Skill provides essential context for working with the crop planning data model used to organize crops, configurations, plantings, and products across stock and live plans.
Use the crop-data skill to review how stock data maps to live plan data and what fields drive key calculations.
High-intent search queries and answers about installing and using this skill.
To map crop planning data for migrations, you link stock templates (crop-config-template.json and crops.json) to live plan data (plan.cropCatalog). This relationship supports cloning configurations and governing plan data across plantings and products.
The crop planning data model architecture follows a strict hierarchy: Crop → Config → Planting → Product. This structure organizes stock templates and live plans while validating field classifications to enable calculations and data migrations.
Validating calculated fields in a crop data architecture requires checking field classifications against the defined data model. This ensures calculations for plantings and products are accurate before executing data migrations or building UI components.
Yes, stock crop templates support live plan governance and cloning. The data model distinguishes source template files from the live plan.cropCatalog, allowing you to safely clone configurations and manage plan data without altering base templates.
Migrating crop-config data between plans requires strict adherence to entity relationships (Crop → Config → Planting → Product) and validated field classifications. Failing to validate calculated fields before migration can break downstream UI components and data integrity.
The crop planning data model supports product configurations by defining entity relationships within the Crop → Config → Planting → Product hierarchy. It documents field definitions and calculated fields to ensure custom configurations map correctly during migrations.
pradyumnasagarAutomate inter-skill data transfer and provenance capture via JSON Material Passports.
Snowflake-LabsA concise summary of your roleplay character: name,</name> personality, and/or behavior, formatted as a single string sentence. Typically不超过50字，此处省略
xjtulycExtract cloud-masked NDVI/EVI/LSWI time series and phenological metrics from Sentinel-2 imagery.
myrtlepnDesign database schemas, ERDs, and migration plans for software features.
