The client is readable

Read and customize the entire sharing skill

InstaShare’s documented client workflow is a Markdown skill containing the actual PowerShell and Bash commands. It is designed to be read before installation and adapted when a team needs stricter sharing rules.

No hidden resident client

The skill runs when invoked in a Claude Code session; it does not install a daemon or background watcher.

Inspect the exact upload behavior

Session discovery, credential patterns, request headers, endpoints, and written files are visible in one document.

Apply local policy

Add patterns, confirmation prompts, project blocks, content removal, or a different API endpoint without waiting for a new client binary.

Transparency is part of the installation model

The recommended manual installation is to save the published SKILL.md into the local Claude skills directory. The homepage displays the file so a user can inspect it before giving Claude permission to execute its commands.

Convenience installers are also available, but piping a remote script directly into a shell trades away that moment of review. The site explicitly presents manual installation as the more transparent path.

Common policy customizations

Because the behavior is ordinary shell code and instructions, individuals and teams can make the workflow more conservative. Customizations stay local unless you intentionally distribute the modified skill.

  • Require a yes/no confirmation immediately before upload.
  • Block sharing from named repositories or directory prefixes.
  • Add proprietary token formats to the redaction list.
  • Remove all tool results or image blocks before transmission.
  • Point development copies at a local or self-managed endpoint.

Readable does not automatically mean safe

A skill can execute shell commands with the permissions available to Claude Code. Read the installed copy, review updates before replacing it, and understand any local changes. Transparency makes inspection possible; the user still has to exercise that control.

How it works

01

Read the published file

Inspect session paths, redaction rules, network endpoint, and local writes.

02

Save it locally

Install the reviewed text in the Claude Code skills directory.

03

Adapt the policy

Make any repository-specific or organization-specific safeguards explicit.

04

Review before updates

Compare a new published version with the copy you already trust.

Important limits

  • Remote one-line installers execute whatever the endpoint serves at that moment; manual inspection provides stronger change awareness.
  • Custom changes can diverge from the published skill and become your responsibility to test and maintain.

Try it in a Claude Code session.

Install the readable skill, then say “share this chat” when the conversation is ready.