right now, skweb performs a number of operations directly through its handle to the sako repository.

that's unfortunate (but we wanted to have something working, fast.)

we should probably expand the skcli API to allow to perform all the operations we want. or, as this would (probably) mean going through a network roundtrip, have a "local" sans-HTTP calls skcli-like client.