agentleFS
Sign inStart free
TheKontextCoTheKontextCo/kontext-claude-plugin/skills/kontext-sharing/SKILL.md

kontext-sharing

Skill1 starsChanged 3 months agoMITView on GitHub

Work correctly with records shared to or by the user in Kontext. Trigger when the user mentions shared access, a collaborator's project, a readOnly record, or asks what they can edit in someone else's Space. Do not trigger for ordinary owned records.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Treat readOnly: true records as reference material only.

    line 16
  2. Distinctive:

    Never move, import, archive, delete, re-share, or administer access on shared records, even when edit permission is present.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Kontext shared records

Records shared with the user arrive in normal MCP context, list, and read tools with explicit capability metadata. Nothing is copied: shared content stays in the owner's live Space.

Reading

  • Shared entities carry access.scope, readOnly, permission, and sharedBy provenance and use opaque recipient references.
  • Treat readOnly: true records as reference material only.
  • Shared records are read-only at the graph boundary: they cannot be relationship endpoints. Do not attempt manage_context_relationship or manage_task_relationship on them.

Editing

  • Edit a shared record only when its returned permission explicitly allows edit. Use the ordinary management tools with the opaque shared ID the tools returned — never a guessed owner-side ID.
  • For an editable shared project, creating new tasks and documents inside it is allowed; those new items are owned by the current user, not the project owner.
  • Never move, import, archive, delete, re-share, or administer access on shared records, even when edit permission is present.

Invitations

  • Sharing invitations and revocation are managed in the Kontext Library web UI, not via MCP. If the user wants to share or unshare something, point them at https://thekontextco.ai/library.
  • Incoming invitations resolve through the native sharing API to a pending state or an accepted opaque reference; the API never exposes item metadata before acceptance. Do not speculate about an invitation's contents.

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.

Check your setup, free