pdf-annotate
Collaboratively annotate a PDF — propose markup, review together, iterate
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- pdf-annotate
- description
- Collaboratively annotate a PDF — propose markup, review together, iterate
03 SKILL.md 正文
<!-- Provenance: adapted from anthropics/knowledge-work-plugins (Apache-2.0, (c) Anthropic). Original command (ported as skill): https://github.com/anthropics/knowledge-work-plugins/tree/main/pdf-viewer/commands/annotate.md. Changes for Muse AI: Claude/Cowork product refs -> Muse AI; MCP -> connector; CLAUDE.md -> MUSE.md; ${CLAUDE_PLUGIN_ROOT} -> this skill's directory; /plugin:command refs -> skill refs. -->
annotate
Ported from the /annotate slash command in the original Claude plugin. In Muse AI, run it as a skill: ask Muse AI to "Collaboratively annotate a PDF — propose markup, review toge...".
If you see unfamiliar placeholders like
~~category, they refer to whatever tool is connected in that category.
Annotate PDF
Walk through a document with the user, proposing and applying annotations section by section. The user reviews each batch in the live viewer before you continue.
Workflow (AI-driven default)
- Open —
display_pdf(or use existingviewUUIDif already open) - Understand —
interact→get_texton the first page range (≤20 pages) to read content - Propose — describe to the user what you plan to annotate:
"I'll highlight the termination clause on page 2, add a note 'Review 30-day window' next to it, and stamp page 1 as DRAFT. Sound good?"
- Apply — on approval,
interactwith batched commands:add_annotations+get_screenshotof the affected page - Review — show the screenshot, ask for edits
- Iterate — move to the next section, repeat
- Finish — remind the user they can download the annotated PDF from the viewer toolbar
Manual mode
If the user gives explicit instructions ("highlight paragraph 3", "stamp CONFIDENTIAL on every page"), skip the proposal step and execute directly. Still confirm with a screenshot.
Annotation types available
- Text markup:
highlight_text(auto-finds text — preferred), highlight, underline, strikethrough - Comments: note (sticky), freetext (visible on page)
- Shapes: rectangle, circle, line
- Stamps: any label — APPROVED, DRAFT, CONFIDENTIAL, REVIEWED
- Images: signatures, initials, logos (see
the "sign" skill)
Tips
- Prefer
highlight_textover manualrectsfor text — it finds coordinates automatically - Batch related annotations in one
interactcall - End each batch with
get_screenshotso the user sees the result - Keep proposals small (3–5 annotations per batch) so review is easy
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).