agentleFS
filecoin-projectfilecoin-project/filecoin-skills/skills/private-share/SKILL.md

private-share

Skill4 starsChanged 27 days agoApache-2.0View on GitHub

Use when the user wants to share a file or folder privately with one person or agent, or says "share this privately", "encrypt and share this", "send this encrypted", "private link", "share this with <name> privately", "only <name> should read this", "make a share link for <CID>". Also use when the user has a Filecoin Share link and Access key to open, or says "open this share", "download this share link", "I got a share link and a key", "decrypt this share", or wants back their own earlier encrypted upload ("restore my encrypted upload", "get my encrypted file back"). Encrypts with the filecoin-pin CLI on Filecoin (mainnet by default) and hands back a Share link and a separate Access key.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read only the file the request needs:

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

private-share

Encrypt a file or folder, store it on Filecoin (mainnet by default) with the filecoin-pin CLI, and hand back a Share link and an Access key for one recipient. Or open a share someone sent. Drive the CLI directly, with no wrapper scripts.

Route the request

Read only the file the request needs:

  • Sharing something (encrypt, send, make a link): references/send.md.
  • Opening a share (the user has a link with #v1/ and a fak1_… key): references/receive.md.
  • Restoring your own earlier encrypted upload (a CID, no link): get in references/filecoin-pin-cli.md.

references/filecoin-pin-cli.md holds the commands, credentials and errors; read that and filecoin-pin --help, never the web. send.md and receive.md point to it. Suite terms (Share link, Access key, Grant, Encrypted root CID) are defined in ../CONTEXT.md.

Red lines

Hard rules; the owning section carries the full rule. Skim before every share.

  • Mainnet by default. Calibration only when the user asks for it, for testing, with --network calibration on every command (references/filecoin-pin-cli.md, Network).
  • Share exactly the paths the user named, and only when the user asks. A folder with anything that looks unintended in it stops for an explicit yes (references/send.md, step 2).
  • With the owner wallet, run add --dry-run first and show the user the cost before the real upload (references/send.md, step 3).
  • Make restricted links by default (--restricted, --get-share-link-restricted), so the link and the Access key stay apart. Make an open link, with the key inside it, only when the user explicitly asks for one and confirms the warning (references/filecoin-pin-cli.md, Open links).
  • Wallet keys, session keys and Grants never enter the conversation, command output you show, logs, or files you write. Check secrets files with boolean tests only (test -f, grep -q) (references/filecoin-pin-cli.md, Credentials).
  • Show the Access key once, labeled, apart from the link. Tell the user to send the two by different channels, and that this conversation's history now holds the key. Never write the key you hand over to a file or a log, and never repeat it later. (Receiving is different: the user may write a key they received to a short-lived key file, as in references/filecoin-pin-cli.md, The Access key.)
  • Run add --encrypt once for each upload (each named path is its own upload). Never run it again after a failure, an interrupted or a stuck run, and never stop a running one: every run uploads and pays again under a new CID. What to do instead, and the one exception (the funding stop), are in "Reading the add result" in references/filecoin-pin-cli.md. A --dry-run uploads nothing.
  • Single-quote every Share link in a shell: it contains # and & (references/receive.md, step 3).
  • "Not altered" means integrity: every block matched the CID and the envelope rejected changes. Never claim it proves who made the content (references/receive.md, step 4).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.