agentspace
See what your AI agent is doing, from anywhere. The agent keeps writing — logs, code, generated outputs, screenshots, artifacts. One command turns the folder into a live URL you (or a teammate) open in any browser to watch files evolve, edit in place, or comment — no sync, no zip, no account. Workspaces stay live 24 hours anonymously; one email claim keeps them permanent. Hosted on Cloudflare. Triggers on "show me what the agent is doing", "open the agent's folder", "share this folder", "give me a link", "hand off this workspace", or any ask to make an agent's local file state visible from another device or to another person.
What this skill does
# 🪢 Agentspace **See what your agent is doing — from anywhere.** Your agent keeps writing — logs, code, generated outputs. You open a URL and watch the folder evolve in the browser. No sync, no zip, no account. 1. Tell the agent to share any local folder or file. 2. The agent returns a URL — anyone opens it in the browser, no signup. [agentspace.so](https://agentspace.so/?utm_source=skills.sh&utm_medium=skill&utm_campaign=agentspace) · [GitHub](https://github.com/agentspace-so/skills) · [npm @agentspace-so/ascli](https://www.npmjs.com/package/@agentspace-so/ascli) ## What you can share Folders, single files, generated code, test output, build logs, screenshots, PDFs, reports, dashboards, prototypes — any local artifact. ## How it works - One command (`ascli share <path>`) creates an anonymous workspace and returns a link. - Anyone opens the link — reads, comments, or edits directly in the browser. - Anonymous workspaces live 24 hours. One email claim makes them permanent. - Hosted on Cloudflare's edge network — links load fast worldwide. ## Data handling - Only the path the user explicitly names is uploaded. Do not default to the current working directory unless the user clearly says so. - All network traffic goes to `agentspace.so` only. - The skill does not read environment variables, shell history, or files outside the path the user specifies. ## Choose the CLI path 1. If `ascli` is already on `PATH`, use it directly. 2. Else if `npm` is available, install once with `npm install -g @agentspace-so/ascli@latest`, or run without installing via `npx @agentspace-so/ascli@latest <command>`. 3. If neither `ascli` nor `npm` is available, stop and tell the user to install Node.js from nodejs.org first. Do not pipe a remote script into a shell to install. ## Share a path - Ask the user which folder or file to share if they have not named one explicitly. Do not assume `.`. - Run `ascli share <path> --permission edit` with the user-specified path. - If the user asks for view-only access, use `--permission view`. - `share` handles an unbound folder by creating a temporary workspace, syncing once, and returning a link — no separate `sync` step is needed. - Return the share URL directly to the user exactly as the CLI prints it. ## Guardrails - Do not invent claim URLs, workspace URLs, or share URLs. Only return what the CLI prints. - Do not require a global install if `npx` already works. - Do not move the user into a different project just to use agentspace.so. - If the user asks to "share this folder" and the target is ambiguous, confirm the exact path before running. - If you need exact command variants, read [references/commands.md](references/commands.md).
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.