Skill marketplace: index format, validator and in-app browse and install

Aperta
#206 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
rust, tauri, typescript

Direzione di ricerca

Start with crates/skills/src/hub/mod.rs and source.rs, then read docs/guide/skills.md to understand the existing index and install flow. The issue asks contributors to comment with a preferred slice and a short format outline before starting, because the trust model needs maintainer input. For a spec slice, define a versioned format compatible with IndexEntry and add docs/skills-index.md plus a JSON Schema; completion is a reviewable spec, with the broader proposal requiring validation, preview approval, UI, and tests.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: daemon area: desktop-ui enhancement help wanted needs design

size: L · first-timer: no

Please comment before starting so we can agree on the design. The trust model (who may publish, what the app trusts by default) is the heart of this issue and needs maintainer input.

Summary

Define a public skill index format and build the experience around it: a validator for index authors, a reference publisher template, and a "browse and install" flow in the desktop app that shows the risk report and requires explicit approval, so people can find and share skills without copying folders.

Why it matters

Skills are the lowest-barrier way for the community to improve what bots can do (how to use a site, an app, a workflow). Today sharing means "send someone a folder". A well-defined index plus a safe install flow turns skills into an ecosystem, and the format is something outside contributors can start using and extending immediately.

Current state

  • The hub library already supports InstallSource::Index { url, name } (crates/skills/src/hub/source.rs). An index is a JSON document served over https:// (at most MAX_INDEX_BYTES, 1 MiB, bounded redirects); each IndexEntry has name, description, git, a full commit hash (required), optional subdir and sha256 fingerprint. Skills install only after preview produced a RiskReport (static scan in scan.rs) and the caller passed back its fingerprint; a lockfile pins what was installed (lock.rs).
  • There is no versioned schema, no documentation of the format, no validator and no reference index.
  • Nothing in the CLI or the daemon exposes install yet (the CLI issue #195 adds bot skills install|update|...). The daemon API only reads lock metadata (crates/daemon-api/src/skills.rs, SkillHubInfoDto) and has owner-only create/import routes (docs/guide/skill-management-api.md).
  • The UI has components/SkillsModal.tsx, AddSkillModal.tsx, SkillsEditor.tsx, BotPanelSkills.tsx; bundled skills live in skills/.

Proposal and suggested approach

Suggested slices, each its own PR:

  1. Format spec (docs/skills-index.md plus a JSON Schema): a version field, per-entry metadata (name, description, tags, author, licence, homepage, minimum Praxi version, git URL, pinned commit, subdir, fingerprint), forward-compatibility rules, size limits. Keep it compatible with today's IndexEntry.
  2. Validator: bot skills index validate <file-or-url> checking schema, https-only URLs, full commit hashes, duplicate names, and (optionally) that each entry fetches and matches its fingerprint.
  3. Publisher template: a minimal repository layout and a GitHub Actions workflow that regenerates and validates an index.
  4. Daemon routes and UI: owner-only routes (classify them in crates/daemon-api/src/owner.rs) to fetch an index, preview an entry and install with the accepted fingerprint; a Skills modal tab to browse/search an index, show the risk report in plain language, and install or update. Indexes are user-added (URL field); decide whether the app ships any default.
  5. Docs: how to publish a skill, how reviews work, what the risk report does and does not prove.

Design questions to settle first: default index or none; whether indexes can be signed; how updates are surfaced; how a bad skill is withdrawn. The scan is advisory (the module docs say so): the UI must never present "no findings" as "safe".

Acceptance criteria

  • A documented, versioned format with a JSON Schema and a validator command with tests (valid, unknown version, short commit hash, duplicate names, oversized document).
  • Installing from an index through the UI always shows the preview and needs an explicit approval bound to the fingerprint; a bot cannot trigger it (never an agent tool).
  • Works offline for already-installed skills; failures show human-readable errors (add the error codes to the human-error layer in both locales).
  • Unit tests for the daemon routes and the UI helpers; check:i18n, lint, typecheck, cargo test -p skills -p daemon-api, OpenAPI snapshot regenerated.

Out of scope

Hosting a central registry service, payments, ratings, signing infrastructure (unless agreed in the design discussion), executable skills.

How to get started

Read crates/skills/src/hub/mod.rs and source.rs, then docs/guide/skills.md. Comment on this issue with which slice you want and a short outline of the format; the spec PR can be reviewed before any code exists.

Lingua principale
Rust
Stelle
0
Fork
1
Merge medio
6h 54m
PR unite (30g)
152

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di emreocell/Praxi-Bot

Tutte le issue di emreocell/Praxi-Bot

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.