Skills

agentspace: share local folders and artifacts with a link

For turning local folders, files, or artifacts on the agent side into a shareable link. Default permission is edit; read-only requires --permission view.

Official source · agentspace skills

Install

npx skills add agentspace-so/skills --skill agentspace -g

Who it's for

Install the agentspace Skill when you need to hand someone a link to a local folder, file, or generated artifact in the agent workspace. The official line is: Share local folders, files, and generated artifacts from your agent via a link.

It uses agentspace.so to sync a local folder to cloud storage and return a shareable URL. It fits people who already have a directory to share and know the default permission is edit. If you only want to look at files on this machine and do not want an outbound link, this Skill does not match.

Page:

https://github.com/agentspace-so/skills

Sync service:

https://agentspace.so/?utm_source=github&utm_medium=readme&utm_campaign=skills

First try in 3 minutes

Take only this Skill's official install command:

npx skills add agentspace-so/skills --skill agentspace -g

Prerequisite: you understand sharing will sync a local folder to cloud storage; the default permission is edit. The official text does not write a Skill destination directory; do not invent a path.

The first time, do not sync a real directory. After install, have the agent check three things: what the default share permission is; which argument to add for read-only; and whether basic sync needs credentials. Success: the agent says Default share permission is edit, read-only uses --permission view, and No credentials or API keys are required for basic sync. If the agent immediately wants to pick a folder and upload, stop first, because the default link can be edited.

Use cases

Case 1: Turn a local folder or artifact into a shareable link. The Skill uses agentspace.so to sync and return a shareable URL. This is outbound sync. Before running, confirm the directory is correct, and say aloud that you accept default edit. Success: you get a URL, not only a local file copy. The page does not write a concrete subcommand or directory example; do not invent them.

Case 2: Read-only access only. The body writes use --permission view for read-only access. Before a real sync, have the agent restate what will happen with the read-only argument: sync to cloud storage, return a link, permission is view, and basic sync needs no credentials or API key. Execute only after that confirmation. The install-probe order used for sync is ascli → npx → curl; that is automatic choice of the sync tool, not a second Skill-install main path.

Boundaries

Default permission is edit. When you do not need a writable outbound link, you must add --permission view explicitly.

Basic sync needs no credentials or API key. The page does not describe a more complex account system; do not invent a secret step.

The same page also has another command: npx skills add agentspace-so/skills --skill find-skills -g. The body does not say what find-skills does, so do not invent its purpose, and on the first try do not put it beside agentspace as two main paths.

There is no client list and no uninstall command. Do not read ascli / npx / curl as permission to swap in an installer that was never written. Do not fill in unwritten file scope, retention time, or access lists.