revise
Revise the most recent or provided p11 shareable document based on comments/replies and publish a new version. Use when Claude Code should apply clear reviewer decisions to a p11 document.
What this skill does
# p11:revise Use this skill to revise an existing p11 document from reviewer comments and share a new version. ## Target Resolution Resolve the p11 document target in this order: 1. Use the p11 read URL, edit URL, read ID, edit ID, or source `.tsx` file provided by the user. 2. If none is provided, use the most recent p11 document mentioned or created in the current chat conversation. 3. Only if the current chat has no usable p11 target, run `p11 history` and use the most recent relevant entry. Do not use `p11 history` when the current chat already contains a usable p11 target. To publish a new version, locate both: - the source `.tsx` document file - the existing p11 edit URL If either cannot be determined from the chat, local files, or p11 history, ask the user for the missing target. ## CLI Resolution Prefer the global `p11` CLI. If missing, install `@p11-core/cli` globally. Use `npx -y @p11-core/cli@latest` only when global install is not possible. Never install p11 into the project. Check availability with `command -v p11` and `p11 --help`. Install or upgrade with `npm install -g @p11-core/cli@latest` when the command is missing or any `p11` command prints an update warning. ## Comment Review Fetch all comments/replies before editing: ```bash p11 comments <target> ``` Use `--json` when structured fields are useful. Use `--version <number>` only when the user asks to revise from a historical version. Only consider comments/replies that are visible to reviewers. Ignore resolved or hidden comments; reviewers will not see replies to them in the UI. Classify every visible thread by its content, not by an unresolved status field alone: - Clear decision: a settled, actionable instruction such as "change this to...", "remove this...", "use this wording", or an accepted alternative. - Needs clarification: a question, request for clarification, disagreement, undecided thread, conflicting replies, or anything Claude Code cannot confidently apply. If any visible threads need clarification, ask the user before editing or publishing whether to: - use `p11:reply` first to ask clarifying questions on those threads, or - ignore those threads for this revision and publish only the clear changes. If the user chooses `p11:reply`, post clarifying replies and do not publish a revision until reviewers answer or the user asks to proceed anyway. If the user chooses to ignore those threads, apply only clear decisions. If all threads are clear, apply clear decisions directly to the source `.tsx` document. Do not silently ignore visible threads that need clarification. ## Revising The Document Keep the document static and reviewable. Do not add controls, forms, navigation, tabs, cards, alerts, badges, or app-shell UI. Read `references/components.md` when editing component structure. Prefer CLI-bundled docs for current examples: ```bash p11 docs p11 docs components p11 example all-components ``` Before sharing, verify the document still: - 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 ## Share The New Version Publish the revision to the existing p11 document: ```bash p11 share <page.tsx> --edit-url <editUrl> ``` Return the updated Read URL and Edit URL when available. Treat edit URLs as bearer credentials and avoid exposing them unnecessarily.
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.