[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ERGVR80451KSNC4SH3F19P":3,"skill-same:01M7ERGVR80451KSNC4SH3F19P":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7ERGVR80451KSNC4SH3F19P","pdf-annotate",null,"Collaboratively annotate a PDF — propose markup, review together, iterate","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-kw-pdf-annotate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pdf-annotate\ndescription: Collaboratively annotate a PDF — propose markup, review together, iterate\n---\n\n\u003C!-- Provenance: adapted from anthropics\u002Fknowledge-work-plugins (Apache-2.0, (c) Anthropic).\nOriginal command (ported as skill): https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Ftree\u002Fmain\u002Fpdf-viewer\u002Fcommands\u002Fannotate.md. Changes for Muse AI: Claude\u002FCowork product refs -> Muse AI; MCP -> connector; CLAUDE.md -> MUSE.md; ${CLAUDE_PLUGIN_ROOT} -> this skill's directory; \u002Fplugin:command refs -> skill refs. -->\n\n# annotate\n\n*Ported from the `\u002Fannotate` 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...\".*\n\n> If you see unfamiliar placeholders like `~~category`, they refer to whatever tool is connected in that category.\n\n# Annotate PDF\n\nWalk through a document with the user, proposing and applying\nannotations section by section. The user reviews each batch in the\nlive viewer before you continue.\n\n## Workflow (AI-driven default)\n\n1. **Open** — `display_pdf` (or use existing `viewUUID` if already open)\n2. **Understand** — `interact` → `get_text` on the first page range\n   (≤20 pages) to read content\n3. **Propose** — describe to the user what you plan to annotate:\n   > \"I'll highlight the termination clause on page 2, add a note\n   > 'Review 30-day window' next to it, and stamp page 1 as DRAFT.\n   > Sound good?\"\n4. **Apply** — on approval, `interact` with batched commands:\n   `add_annotations` + `get_screenshot` of the affected page\n5. **Review** — show the screenshot, ask for edits\n6. **Iterate** — move to the next section, repeat\n7. **Finish** — remind the user they can download the annotated PDF\n   from the viewer toolbar\n\n## Manual mode\n\nIf the user gives explicit instructions (\"highlight paragraph 3\",\n\"stamp CONFIDENTIAL on every page\"), skip the proposal step and\nexecute directly. Still confirm with a screenshot.\n\n## Annotation types available\n\n- **Text markup:** `highlight_text` (auto-finds text — preferred),\n  highlight, underline, strikethrough\n- **Comments:** note (sticky), freetext (visible on page)\n- **Shapes:** rectangle, circle, line\n- **Stamps:** any label — APPROVED, DRAFT, CONFIDENTIAL, REVIEWED\n- **Images:** signatures, initials, logos (see `the \"sign\" skill`)\n\n## Tips\n\n- Prefer `highlight_text` over manual `rects` for text — it finds\n  coordinates automatically\n- Batch related annotations in one `interact` call\n- End each batch with `get_screenshot` so the user sees the result\n- Keep proposals small (3–5 annotations per batch) so review is easy\n","\u003C!-- Provenance: adapted from anthropics\u002Fknowledge-work-plugins (Apache-2.0, (c) Anthropic).\nOriginal command (ported as skill): https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Ftree\u002Fmain\u002Fpdf-viewer\u002Fcommands\u002Fannotate.md. Changes for Muse AI: Claude\u002FCowork product refs -> Muse AI; MCP -> connector; CLAUDE.md -> MUSE.md; ${CLAUDE_PLUGIN_ROOT} -> this skill's directory; \u002Fplugin:command refs -> skill refs. -->\n\n# annotate\n\n*Ported from the `\u002Fannotate` 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...\".*\n\n> If you see unfamiliar placeholders like `~~category`, they refer to whatever tool is connected in that category.\n\n# Annotate PDF\n\nWalk through a document with the user, proposing and applying\nannotations section by section. The user reviews each batch in the\nlive viewer before you continue.\n\n## Workflow (AI-driven default)\n\n1. **Open** — `display_pdf` (or use existing `viewUUID` if already open)\n2. **Understand** — `interact` → `get_text` on the first page range\n   (≤20 pages) to read content\n3. **Propose** — describe to the user what you plan to annotate:\n   > \"I'll highlight the termination clause on page 2, add a note\n   > 'Review 30-day window' next to it, and stamp page 1 as DRAFT.\n   > Sound good?\"\n4. **Apply** — on approval, `interact` with batched commands:\n   `add_annotations` + `get_screenshot` of the affected page\n5. **Review** — show the screenshot, ask for edits\n6. **Iterate** — move to the next section, repeat\n7. **Finish** — remind the user they can download the annotated PDF\n   from the viewer toolbar\n\n## Manual mode\n\nIf the user gives explicit instructions (\"highlight paragraph 3\",\n\"stamp CONFIDENTIAL on every page\"), skip the proposal step and\nexecute directly. Still confirm with a screenshot.\n\n## Annotation types available\n\n- **Text markup:** `highlight_text` (auto-finds text — preferred),\n  highlight, underline, strikethrough\n- **Comments:** note (sticky), freetext (visible on page)\n- **Shapes:** rectangle, circle, line\n- **Stamps:** any label — APPROVED, DRAFT, CONFIDENTIAL, REVIEWED\n- **Images:** signatures, initials, logos (see `the \"sign\" skill`)\n\n## Tips\n\n- Prefer `highlight_text` over manual `rects` for text — it finds\n  coordinates automatically\n- Batch related annotations in one `interact` call\n- End each batch with `get_screenshot` so the user sees the result\n- Keep proposals small (3–5 annotations per batch) so review is easy\n",{"name":5,"description":7},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-kw-pdf-annotate",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill pdf-annotate",{"tool":38,"command":39},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill pdf-annotate",{"tool":41,"command":42},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill pdf-annotate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-kw-pdf-annotate\u002FSKILL.md",true,[],[47,54,62,69,76,83],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":58,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","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\u002FCSS, 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.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","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).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]