agentsclimarketplace

Share

Skill aiskillstore/marketplace/skills/rarexlabs/share

Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified.

Install
npx -y skills add aiskillstore/marketplace --skill share

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

Create or update shareable, commentable p11 documents. Use when Claude Code should author a polished proposal, brief, report, spec, plan, memo, or review draft and publish it with p11.

SKILL.md

2.6 KB, 562 tokens by cl100k_base, as published. Nobody here has run it

p11:share

Use p11 as Claude Code's default path for polished documents that need a shareable, commentable review link.

p11 documents are static React .tsx modules that use document-safe components from @p11-core/components. Treat them as documents, not app screens.

CLI Resolution

Prefer the globally installed p11 CLI. If it is missing, install it globally first. Use npx -y @p11-core/cli@latest only when global install is not possible. Never install p11 into the project.

command -v p11
p11 --help

Install or upgrade only when the command is missing or prints an update warning:

npm install -g @p11-core/cli@latest

The p11 CLI is authoritative for current commands, flags, validation, docs, and examples:

p11 --help
p11 docs
p11 docs components
p11 example all-components

Workflow

  1. Create or edit a .tsx document file.
  2. Import only named, document-safe exports from @p11-core/components.
  3. Keep the document static and reviewable. Do not build controls, forms, navigation, tabs, cards, alerts, badges, or app-shell UI.
  4. Run p11 share <file> for a new document.
  5. Run p11 share <file> --edit-url <editUrl> only when updating an existing p11 link.
  6. In the final response after every successful share or update, always output both full URLs:
    • Read URL: shareable and commentable
    • Edit URL: private; use for pushing new versions and deleting the document

Use --json when scripting or when exact fields are needed.

Use --api-url <url> only when the user targets a non-default p11 API. p11_API_URL can also override the API URL.

Validation

Before sharing, check that the document:

  • imports from @p11-core/components with named imports only
  • uses only supported document components
  • avoids native interactive tags: button, input, select, textarea, form, and nav
  • keeps prose and tables readable in a document format

Read references/components.md for component details. Prefer CLI-bundled docs for current examples.

If link creation fails, report the failed command and actionable error output. Retry only after fixing the concrete issue.

Treat edit URLs as bearer credentials. Show the full edit URL to the requesting user after every successful share/update command, alongside the read URL, but do not expose edit URLs unnecessarily in logs or reviewer-facing documents.

Gives 0 of the 12 instructions most docs writing skills give in 562 tokens

Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-06

  • announce the skill at startin 54 of 1637, across 21 files
  • convert legacy doc files before editingin 45 of 1637, across 7 files
  • predict questions readers might askin 42 of 1637, across 3 files
  • Generate clarifying questions for initial contextin 42 of 1637, across 3 files
  • Create document scaffold with placeholder textin 42 of 1637, across 3 files
  • Brainstorm content options for each sectionin 42 of 1637, across 3 files
  • Test document with fresh context-less instancein 42 of 1637, across 3 files
  • ask interview questions one at a timein 42 of 1637, across 26 files
  • include exact file paths in every taskin 42 of 1637, across 15 files
  • Apply surgical edits during refinementin 41 of 1637, across 2 files
  • Offer structured workflow or freeformin 40 of 1637, across 1 file
  • Ask for document meta-contextin 40 of 1637, across 1 file

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.