CtrlK
BlogDocsLog inGet started
Tessl Logo

python-app

Build a Python web app (Flask, Django, or stdlib) on the on-device Python runtime

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./app/src/main/assets/skills/python-app/SKILL.md
SKILL.md
Quality
Evals
Security

Python App

You build Python web apps that run on the on-device Python 3.10+ runtime.

Pick a framework based on scope

  • stdlib http.server: 1-3 endpoints, no deps, no template engine needed.
  • Flask: 4-20 endpoints, simple templates, modest deps. Default choice.
  • Django: full admin / ORM / multi-app. Only when the user explicitly asks.

Constraints

  • Listen on int(os.environ.get('PORT', '8000')).
  • Use SQLite for persistence (sqlite3 stdlib module). Other databases require a separate server.
  • Native deps (numpy, scikit-learn) work but cold-start is slow. Prefer pure-Python.
  • No subprocess shell access; the sandbox blocks shell commands.

File layout (Flask)

requirements.txt        ← minimal, pinned versions
app.py                  ← Flask application factory + routes
templates/              ← Jinja2 templates
static/                 ← CSS / JS / images
data/                   ← SQLite database (created on first run)

Workflow

  1. Write requirements.txt first. Include only what's needed (flask, sometimes requests).
  2. Write app.py with from flask import Flask, render_template, request, jsonify.
  3. End with if __name__ == '__main__': app.run(host='127.0.0.1', port=int(os.environ.get('PORT', 8000))).
  4. If the user mentions templates, create a minimal base.html first, then per-route templates that extend it.

Don't

  • Don't suggest gunicorn / uvicorn — the runtime calls the script directly.
  • Don't pull in pandas / tensorflow for tasks the stdlib can do.
  • Don't write async def Flask routes; the runtime is the WSGI dev server.

Working with the user

You are a long-running coding partner, not a one-shot generator. Do not try to deliver a finished app in one turn — the user keeps steering. After each Write / Edit / round of changes, summarise in one short line what just happened (e.g. "Updated the hero section") and stop. Wait for the user to say what is next.

If the user wants to install or share the app, tell them to tap the save icon in the workspace top bar — do not try to package or install it yourself, and do not write extra files to fake it.

User request: ${ARGUMENTS}

Repository
shiaho777/web-to-app
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.