pysepal-app

Scaffold and restructure pysepal Solara and Voila apps to official architecture best practices.

13|4|Updated Jul 27, 2020
One-click install
npx skills add https://github.com/openforis/pysepal --skill pysepal-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pysepal-app
Source: https://github.com/openforis/pysepal/tree/main/skills/pysepal-app
Command: npx skills add https://github.com/openforis/pysepal --skill pysepal-app

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Building pysepal applications manually often leads to inconsistent architecture, missing required boilerplate, and broken deployment patterns, especially when migrating legacy notebooks or adapting existing repos to current pysepal standards. This Skill eliminates that manual overhead by providing a standardized, validated workflow for scaffolding and restructuring pysepal apps to follow official best practices.

Core Features & Use Cases

  • Standardized Scaffolding: Generates complete, runnable project structures for both GEE/container and local/Voila pysepal apps, including all required configuration files, component directories, and deployment assets.
  • Best Practice Enforcement: Automatically applies current pysepal patterns including reactive solara.reactive() AppState, session-backed Google Earth Engine flows, SepalClient-based user file operations, and notification provider integration, while avoiding deprecated traitlets observer architectures and unsafe container filesystem access for user data.
  • Safe Existing Repo Editing: Safely restructures legacy pysepal apps to match current conventions without overwriting user-owned code, with clear conflict detection and validation checks before any changes are applied.
  • Use Case Example: If you have a Jupyter notebook with Earth Engine analysis logic, use this Skill to map the notebook's computation and UI into a production-ready Solara app with async task handling, export capabilities, and SEPAL user file support.

Quick Start

Use the pysepal-app skill to scaffold a new GEE-enabled pysepal Solara app from my existing Earth Engine analysis notebook, following the standard container deployment pattern.

Frequently Asked Questions about pysepal-app

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

FAQPage Schema
How do I scaffold a SEPAL Solara app from a Jupyter notebook?

You scaffold a SEPAL Solara app by mapping Earth Engine analysis logic into a standardized project structure, replacing manual boilerplate with reactive AppState patterns and session-backed Google Earth Engine flows.

What is the best way to migrate legacy Jupyter notebooks to pysepal apps?

The best way to migrate legacy notebooks to pysepal apps is by restructuring them to follow official architecture best practices, enforcing reactive solara.reactive() AppState and avoiding deprecated traitlets observer architectures.

Can I use Google Earth Engine flows in a local Voila deployment?

Yes, you can select between a GEE/container layout and a local/Voila layout for your SEPAL-integrated geospatial workflows, ensuring the architecture matches the intended deployment target.

Does scaffolding a pysepal app overwrite my existing repository code?

Restructuring legacy pysepal apps is safe and does not overwrite user-owned code, utilizing clear conflict detection and validation checks against existing repo safety rules before applying any changes.

Why does my pysepal app need a SepalClient-based file operation pattern?

A pysepal app needs a SepalClient-based pattern to safely handle user file operations and export layer handling, explicitly avoiding unsafe container filesystem access for user data.