share
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.
What this skill does
# 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. ```bash command -v p11 p11 --help ``` Install or upgrade only when the command is missing or prints an update warning: ```bash npm install -g @p11-core/cli@latest ``` The p11 CLI is authoritative for current commands, flags, validation, docs, and examples: ```bash 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.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.