convert-streamlit-app

Convert single-file Streamlit scripts into stateless Pixie tools with tool.json.

6|1|Updated May 17, 2026
One-click install
npx skills add https://github.com/AlexKapadia/Pixie --skill convert-streamlit-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convert-streamlit-app
Source: https://github.com/AlexKapadia/Pixie/tree/main/.claude/skills/convert-streamlit-app
Command: npx skills add https://github.com/AlexKapadia/Pixie --skill convert-streamlit-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a Streamlit script into a Pixie tool by translating st.* widgets to tool.json inputs and st.* outputs to run results, enabling a smoke-free, reproducible conversion for simple apps.

Core Features & Use Cases

  • Maps Streamlit input widgets to Pixie tool inputs and output render calls to tool results.
  • Enforces a single-file, stateless Streamlit app model and rejects multi-page or stateful patterns.
  • Generates a ready-to-run Pixie skeleton including tool.json, a minimal main.py with a Streamlit stub, and a compatible pyproject.toml.

Quick Start

Provide a single-file Streamlit script path and I will generate a Pixie tool skeleton with tool.json and a stubbed main.py.

Frequently Asked Questions about convert-streamlit-app

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

FAQPage Schema
How do I convert a Streamlit app to a Pixie tool?

To convert a Streamlit app to a Pixie tool, provide a single-file Streamlit script path and the process maps st.* input widgets to tool.json inputs and st.* outputs to run results, generating a ready-to-run Pixie skeleton.

Can I convert a multi-page or stateful Streamlit app to Pixie?

You cannot convert a multi-page or stateful Streamlit app to Pixie using this method because it enforces a single-file, stateless Streamlit app model. It rejects multi-page or stateful patterns to ensure reliable conversion.

What files are generated when converting a Streamlit script to a Pixie tool?

Converting a Streamlit script to a Pixie tool generates a tool.json with mapped inputs and outputs, a minimal main.py that stubs Streamlit, and a compatible pyproject.toml for deployment.

Does the Streamlit to Pixie conversion approach work with complex stateful applications?

The Streamlit to Pixie conversion approach does not work with complex stateful applications. It applies to simple, single-file Streamlit apps described by the user and avoids stateful patterns to ensure reliable, reproducible conversion.

How does the Streamlit widget mapping work when creating a Pixie tool?

The Streamlit widget mapping works by translating st.* input widgets into Pixie tool.json inputs and st.* output render calls into run results. This enables a smoke-free, reproducible conversion for simple apps.

What do I need to start converting my Streamlit script into a Pixie tool?

To start converting your Streamlit script into a Pixie tool, you need to provide the path to a simple, single-file Streamlit script. The process then automatically generates the Pixie tool skeleton with a stubbed main.py.