Przejdź do treści
Biblioteka skilli
Programowanie · Budowanie i kod

bot-dashboard

/bot-dashboard

Buduje panel WWW i API dla bota discord.py: wspólna baza SQLite, logowanie OAuth2 Discord i żywe statystyki.

Licencja
MIT
Ostatnia zmiana repozytorium
06.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
15
Skrypty
1
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 06.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: scripts/dashboard.py

Co robi i kiedy

Buduje panel WWW i API dla bota discord.py: wspólna baza SQLite, logowanie OAuth2 Discord i żywe statystyki.

Wyzwalacze z opisu

make a dashboard for my botweb panelbot websitelet admins manage the bot from the webshow bot stats on a page
Oryginalny opis (EN)

Build a web dashboard and backend API for a discord.py bot: one SQLite database shared by the bot and the API, Discord OAuth2 login gated by guild and role, live numbers with polling or SSE, and a one-screen layout. Use when the user says 'make a dashboard for my bot', 'web panel', 'bot website', 'let admins manage the bot from the web', or 'show bot stats on a page'. Do NOT use for the bot's Discord commands or embeds; use slash-commands, interactive-components, or design-with-hallmark for those.

Jak działa

  1. Architecture: one database, two processes — with a one-process variant
  2. The demo server
  3. The production server: FastAPI + Pydantic + Depends
  4. Auth: Discord OAuth2, done the boring way
  5. Realtime: per-widget polling intervals
  6. Realtime transport: one seam, swappable transports
  7. Layout: the one-screen dashboard
  8. Revision / audit feed: the events endpoint
  9. Watch / notify: the dashboard that taps you on the shoulder
  10. Configuration: environment variables
Sekcje z nagłówków SKILL.md, w oryginale · 129 linii, 857 słów
Podgląd SKILL.md
---
name: bot-dashboard
description: "Build a web dashboard and backend API for a discord.py bot: one SQLite database shared by the bot and the API, Discord OAuth2 login gated by guild and role, live numbers with polling or SSE, and a one-screen layout. Use when the user says 'make a dashboard for my bot', 'web panel', 'bot website', 'let admins manage the bot from the web', or 'show bot stats on a page'. Do NOT use for the bot's Discord commands or embeds; use slash-commands, interactive-components, or design-with-hallmark for those."
license: MIT
compatibility: "discord.py 2.x, Python 3.10+, no paid services"
metadata:
  version: "0.5.0"
  author: "drewdestar"
---

# Bot Dashboard

A dashboard answers three questions on one screen: is the bot alive,
what is happening, and what needs attention. Everything else is
depth behind a tab. If a visitor cannot answer all three in about
two seconds, the dashboard failed, no matter how good it looks.

This skill teaches the web side the rest of the pack assumes exists:
`design-with-hallmark` themes a dashboard, `deploy-and-monitor`
tells you to add a `/health` endpoint to one, and neither teaches
you to build one. This one does.

## Architecture: one database, two processes — with a one-process variant

One SQLite database, two processes (bot + API), with the one-process variant. See `references/architecture.md`.

## The demo server

The demo server in `scripts/dashboard.py`: what it proves and what it does not. See `references/demo-server.md`.

## The production server: FastAPI + Pydantic + Depends

The production server: FastAPI + Pydantic + Depends, with the limiter and `/metrics`. See `references/production-server.md`.

## Auth: Discord OAuth2, done the boring way

Discord OAuth2 login gated by guild and role, the session, the allowlisted command bridge, and the WebSocket auth gotchas. See `references/auth.md`.

## Realtime: per-widget polling intervals

Per-widget polling intervals, with SSE streamed and progressive states. See `references/realtime-polling.md`.

## Realtime transport: one seam, swappable transports

Structure the live side as `Transport → codec → typed EventBus
→ reactive stores → UI`, with polling, SSE, and WebSocket as
interchangeable `Transport` implementations behind one
interface, plus a `MockTransport` for offline tests. The page
does not know or care which transport is behind the seam: the
polling transport fetches `/api/stats` and `/api/events` on the
per-widget intervals in `references/realtime-polling.md`; the SSE transport subscribes to the
events channel; the WebSocket transport does the same over a
socket. Swapping transports is a one-line change, not a rewrite,
and the UI runs against `MockTransport` with zero bot running —
which is how the page gets tested at all. This is a design
section, not a demo rewrite: the stdlib demo keeps its single
polling timer, and the seam is what you build when the
upgrade to SSE or WebSocket becomes a user-visible need.

## Layout: the one-screen dashboard

The one-screen dashboard layout, empty and loading states, toasts, and destructive actions. See `references/layout.md`.

## Revision / audit feed: the events endpoint

The events endpoint: the revision/audit feed the dashboard polls. See `references/revision-feed.md`.

## Watch / notify: the dashboard that taps you on the shoulder

Watch/notify: the dashboard that taps you on the shoulder, with trend graphs. See `references/watch-notify.md`.

## Configuration: environment variables

Environment variables for the dashboard and the bot. See `references/configuration.md`.

## Server-only vs browser code

What runs server-only and what runs in the browser. See `references/server-vs-browser.md`.

## Licence safety: patterns only, never copied code

Every repo named in this skill is a *pattern* reference, never a
code source. Steal the shape — pi-hole's one-screen layout,
Grafana's panel grid, Refine's provider split, Supabase's
channel model — and write the code yourself, in this pack, under
its MIT licence. Never vendor or copy code from an AGPL or GPL
repo into this pack or into a bot built from it: metabase,
glance, netbird, stable-diffusion-webui, firecrawl, searxng,
and scira are all AGPL-3.0 in the research, and AGPL/GPL code
copied into a shipped project carries copyleft obligations this
pack does not accept. If a pattern only exists in an AGPL repo,
describe it in your own words and implement it from the
description. When in doubt, check the repo's `LICENSE` file
before treating anything as MIT — the GitHub API reports
NOASSERTION for several of these repos, so the API's licence
field is not proof.

## Theme: one system, dealt once

Deal a Hallmark theme with `design-with-hallmark` and use its
`dashboard_tokens()` as the page's CSS variables. Do not invent
colors alongside them. The theme skill owns the look; this skill
owns the structure. If Hallmark is not installed, one neutral
palette plus one accent is the fallback — and that is a valid
subset, not a failure.

Run the dashboard through the same checks the design skills use:
contrast 4.5:1 on body text, visible focus rings, no emoji as
icons (SVG instead), cursor-pointer on clickables, text that
reflows without clipping, `prefers-reduced-motion` respected,
and the page checked at 390, 768, and 1280 widths. Motion is a
token (one duration family), not a one-off, and it stops entirely
under reduced motion.

## Security checklist (before the dashboard leaves localhost)

The security checklist before the dashboard leaves localhost. See `references/security-checklist.md`.

## Cross-platform and all-languages box

Cross-platform and all-languages notes. See `references/cross-platform.md`.

## Verify live

How to verify the dashboard live, step by step. See `references/verify-live.md`.

## What this skill never does

- It never teaches Discord commands, embeds, or components.
  Those are `slash-commands` and `interactive-components`.
- It never themes a page. That is `design-with-hallmark`.
- It never runs a bot 24/7. That is `deploy-and-monitor`.
- It never stores user data. The dashboard reads the bot's
  database; it does not become a second database.
- It never claims a check it did not run. If the FastAPI path,
  the browser widths, macOS, or Windows were not verified, the
  skill says UNVERIFIED and the agent says so to the user too.
Pliki w paczce (15)
  • SKILL.md 6 KB
  • references/architecture.md 2 KB
  • references/auth.md 5 KB
  • references/configuration.md 1 KB
  • references/cross-platform.md 1 KB
  • references/demo-server.md 2 KB
  • references/layout.md 2 KB
  • references/production-server.md 1 KB
  • references/realtime-polling.md 2 KB
  • references/revision-feed.md 1 KB
  • references/security-checklist.md 2 KB
  • references/server-vs-browser.md 1 KB
  • references/verify-live.md 2 KB
  • references/watch-notify.md 2 KB
  • scripts/dashboard.py 19 KB

Wersje

W bazie nie ma innych skilli o nazwie bot-dashboard.

Migawka bazy z 13.11.2026 · wersja paczki f26074461ad7 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100build-discord-bot
    Buduje produkcyjnego bota Discord w discord.py: intencje, moduły, konfigurację ze zmiennych i logowanie.
  • 100discord-expert
    Wspiera tworzenie botów Discord w discord.js i discord.py: komendy slash, embedy, kanały głosowe, moderacja i wdrożenie bota.
  • 95discord-bot-helper
    Wspiera budowę botów Discord w discord.js v14: komendy slash, zdarzenia, komponenty, embedy i uprawnienia.
  • 100design-with-hallmark
    Stosuje motyw Hallmark do embedów, panelu WWW i grafik README bota Discord, żeby wszystkie funkcje wyglądały jak jeden bot.
  • 100discord
    Buduje i automatyzuje integracje z Discordem: boty, webhooki, komendy slash i przepływy REST API, w tym z użyciem discord.js i discord.py.
  • 100discord
    Tworzy aplikację i bota Discord w discord.js 14: dobiera gateway intents, rejestruje komendy slash, odpowiada na interakcje, wysyła embedy i przyciski oraz obsługuje limity zapytań i webhooki.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.