beclab/olares

olares-knowledge

Olares Knowledge via olares-cli knowledge — manage download-server URL, yt-dlp, aria2, torrent, HuggingFace, and Wise download tasks: create/list/inspect/pause/resume/cancel/remove, prefs, sync, and file probes.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/beclab/olares --skill olares-knowledge

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

knowledge

Shared front door: load `../olares-shared/SKILL.md` for suite routing, active-profile selection, platform entry points, and the auth proceed/stop gate. Load its auth reference only when login, profile switching, token storage, or auth recovery is actually needed.

Use olares-cli knowledge download <verb> --help for syntax.

When to use

  • Create and manage URL, yt-dlp, aria2, torrent, HuggingFace, or Wise download-server tasks.
  • Inspect providers/qualities, synchronize task changes, manage torrent state, or probe/remove downloaded resources.
  • Read or change download preferences and download-server settings.
Not top-level download (installer packages: download component / wizard / check). Not files download (pull a Drive/Sync file) — that lives in `olares-files`.

Version gate

All verbs require Olares 1.12.7+ because the Settings download edge and provider are both required. If the version cannot be established, follow the shared profile/auth gate before deciding that an upgrade is needed.

Fast paths

TaskReadFirst command
Download a URL and know when it landscreating a taskolares-cli knowledge download create <url> -o json, then download wait <id>
See what is downloading nowthis fileolares-cli knowledge download list -o json
Find out which qualities a link offers before taking oneprovider/quality inspectionolares-cli knowledge download inspect <url> -o json
Check whether something is already on diskURL vs resource-path decisionsolares-cli knowledge download file exists <path> -o json

Verb index

FamilyVerbsRead when triggered
start onecreate, info, waitcreate and follow a task
manage the ones that existlist, pause, resume, cancel, removelisting, pausing and retiring tasks
probe + prefsinspect, prefs get, prefs setprovider/quality inspection
syncunfinished, synccursor and drain semantics
torrenttorrent inspect, stats, peers, files, seed stop/resume; torrent createtorrent selection and seeding
file toolsfile exists, file removeURL vs resource-path decisions
settingssettings get, settings setglobal download-server settings

Task and asynchronous semantics

  • Create returns a server-side task id; command success does not mean bytes have finished downloading or moving. Take the id and poll info <id> every few seconds rather than blocking a turn on create --wait, which is there for scripts that want one call. Either way the status is the only terminality input: waiting_to_move / moving are still in progress, and error is a failure even when will_auto_retry says a server sweep may pick the row up again.
  • Create names the task itself, from the URL's inspect title. Leave --name off unless the user asked for a specific filename, and never build one out of a URL path — a name sent on create is pinned to the row for good. Magnet links, --torrent uploads and HuggingFace repos reject the flag outright: those names come from torrent metadata or the repo id.
  • Re-submitting the same URL always creates a new task (no identity dedup). Landing-name collisions are resolved with a (n) suffix; they do not reuse or block an existing row. Create sends Idempotency-Key only to collapse transport retries of one attempt — not URL dedup.
  • Pause only applies while waiting or downloading (otherwise 400). Resume, cancel, and remove return 409 while the task is in the yt-dlp mover phase (waiting_to_move / moving) — wait and retry; do not treat pause the same way.
  • Task ownership follows the active profile. Do not infer another user's task from an id or try alternate identities.
  • inspect is advisory: provider/quality probing may fail while a create still works. Report that uncertainty instead of declaring the URL undownloadable.
  • Sync cursors describe change observation, not task completion. Preserve the cursor when continuing an incremental sync.

Safety and escalation

  • Confirm create, cancel, remove, seed stop/resume, file remove, preference writes, and global setting writes.
  • Before create, confirm destination/app, provider intent, torrent file selection, and whether an existing equivalent task should be reused. Use list / info to check; the CLI does not detect or block duplicates.
  • file remove takes a download-server resource path, not an arbitrary local filesystem path.
  • A URL that fails for a missing login is not a dead end: cookies live in `olares-settings` under settings integration cookie. The hand-off does need the user, though — the cookies.txt is their own browser export, so ask for it rather than hunting for a file. See provider/quality inspection for the signals and the full flow.
  • Stop on ambiguous URL/resource path, task owner, duplicate-task intent, torrent selection, or any credential request the cookie hand-off does not cover.

Correlati per attività

dallo stesso repository

Altri Skills

Tutti gli Skills
beclab
Community

olares-chart

Olares app packaging and chart authoring via olares-cli chart — port a repo, docker-compose, or generic Helm chart; build/push the image; author, lint, package, and deploy an OlaresManifest; wire storage, middleware, entrances, env, and GPU; edit the chart after diagnosis. Runtime failure diagnosis is olares-doctor; public Market submission is olares-publish.

installazioni
2
GitHub Stars
5,3K
Aggiornato
20 ott
beclab
Community

olares-cluster

Olares ControlHub K8s runtime view via olares-cli cluster — inspect pods, containers, workloads, logs, jobs, cronjobs, namespaces, nodes, and middleware; exec, scale, restart, or delete K8s objects. Use for raw runtime objects and logs, not app lifecycle (market), resource metrics (dashboard), or host install.

installazioni
2
GitHub Stars
5,3K
Aggiornato
20 ott
beclab
Community

olares-dashboard

Olares Dashboard via olares-cli dashboard — CPU, memory, disk, network, pod counts, fan, GPU, application/resource rankings, JSON envelopes, and --watch. Use for Dashboard metrics, overview, resource usage, and Olares One fan; not for pod logs or K8s object inspection (olares-cluster).

installazioni
2
GitHub Stars
5,3K
Aggiornato
20 ott
beclab
Community

olares-files

Olares Files via olares-cli files — browse known paths; upload or download file bytes; edit, share, mount SMB/NFS, compress/extract archives, and manage Seafile sync across Drive/cache/external/cloud. Use for Olares Files and LarePass Files operations, not URL/yt-dlp/torrent download tasks (olares-knowledge).

installazioni
2
GitHub Stars
5,3K
Aggiornato
20 ott