[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72YA0AZ5FS611J75ZSW12FE":3,"skill-same:01M72YA0AZ5FS611J75ZSW12FE":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":27,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M72YA0AZ5FS611J75ZSW12FE","doc-coauthoring",null,"Collaborative document editing workflows for merging changes, resolving comments, managing versions, and coordinating review cycles. Use when the user asks to coauthor, merge edits, handle tracked changes, resolve review comments, or run a multi-author doc review process. Trigger phrases include \"coauthor\", \"document collaboration\", \"merge edits\", \"track changes\", \"document review\", and \"resolve comments\".","dawsonblock\u002Fagent_eval_skills_merged_clean","dawsonblock","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F56236740?v=4","01M72Y87EG0A5JP9CKS7EYX8VM","01M72Y87FAP3N0D86AHKBJN53E",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002Fagent_eval_skills_merged_clean\u002Fblob\u002Fmain\u002Fagent-skills-curated\u002Fskills\u002Fpdf-and-documents\u002Fdoc-coauthoring\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: doc-coauthoring\ndescription: Collaborative document editing workflows for merging changes, resolving comments, managing versions, and coordinating review cycles. Use when the user asks to coauthor, merge edits, handle tracked changes, resolve review comments, or run a multi-author doc review process. Trigger phrases include \"coauthor\", \"document collaboration\", \"merge edits\", \"track changes\", \"document review\", and \"resolve comments\".\n---\n\n# Doc Coauthoring\n\nCollaborative document editing — merging changes, resolving reviews, and version management.\n\n## Coauthoring Workflow\n\n### Phases\n\n```\nDraft → Review → Revise → Approve → Publish\n```\n\n| Phase | Owner | Duration | Deliverable |\n|-------|-------|----------|-------------|\n| Draft | Author | Varies | First draft |\n| Review | Reviewers | 2–3 days | Comments\u002Ftracked changes |\n| Revise | Author | 1–2 days | Revised draft |\n| Approve | Approver | 1 day | Signed-off final |\n| Publish | Author\u002FPublisher | — | Published doc |\n\n## Version Naming\n\nUse semantic versioning for formal documents:\n\n```\nv0.1  — initial draft\nv0.2  — after author self-edit\nv1.0  — first version sent for review\nv1.1  — after first round of revisions\nv2.0  — major structural rework\n```\n\nStore versions as: `document-name-v1.0-YYYY-MM-DD.docx`\n\n## Comment Resolution\n\nWhen resolving reviewer comments, categorize each:\n\n| Category | Action |\n|----------|--------|\n| **Accept** | Make the change as suggested |\n| **Accept-Modified** | Incorporate the intent, adjusted |\n| **Reject-Explained** | Decline with a clear reason in the reply |\n| **Discuss** | Flag for synchronous conversation |\n\nReply to every comment before resolving. Unresolved comments = open decisions.\n\n## Merge Strategies\n\n### Google Docs \u002F Office 365 (simultaneous editing)\n\n- Turn on **Suggesting mode** (Google) or **Track Changes** (Word) before editing\n- Use `@mentions` to route questions to specific collaborators\n- Resolve all suggestions before marking review complete\n- Use document outline headings to assign sections per author\n\n### Markdown \u002F Git-based Docs\n\n```bash\n# Author A branches\ngit checkout -b docs\u002Fsection-3-update\n\n# Author B branches from same base\ngit checkout -b docs\u002Fsection-5-update\n\n# After review: merge A first, then B rebases\ngit checkout main\ngit merge --no-ff docs\u002Fsection-3-update\n\ngit checkout docs\u002Fsection-5-update\ngit rebase main   # resolve any conflicts\ngit checkout main\ngit merge --no-ff docs\u002Fsection-5-update\n```\n\n**Conflict resolution for prose** — when Git marks a conflict in a text block:\n1. Read both versions in context\n2. Identify the best version or blend the intent of both\n3. Never auto-accept without reading; prose merges require judgment\n\n## Review Request Template\n\n```\nSubject: Review request: [Document Title] — due [Date]\n\nHi [Reviewers],\n\nPlease review the attached document by [Date].\n\nFocus areas:\n- [Section A]: Is the logic sound?\n- [Section B]: Does the tone match our audience?\n- Any errors of fact in section C?\n\nPlease use Suggesting mode (or add comments) rather than direct edits.\n\nThanks\n```\n\n## Document Handoff Checklist\n\nBefore marking a document final:\n\n- [ ] All comments resolved or explicitly deferred\n- [ ] Track changes accepted or rejected — no open markups\n- [ ] Version number updated in filename and header\n- [ ] Changelog entry added (date, author, summary of changes)\n- [ ] Approved by designated approver\n- [ ] Stored in canonical location (Drive folder, Confluence page, etc.)\n- [ ] Stakeholders notified\n\n## Changelog Format\n\nAt the top of long-lived documents:\n\n```markdown\n## Changelog\n\n| Version | Date | Author | Summary |\n|---------|------|--------|---------|\n| v1.2 | 2024-06-01 | Jane | Added security section |\n| v1.1 | 2024-05-15 | John | Revised scope per feedback |\n| v1.0 | 2024-05-01 | Jane | Initial release |\n```\n","# Doc Coauthoring\n\nCollaborative document editing — merging changes, resolving reviews, and version management.\n\n## Coauthoring Workflow\n\n### Phases\n\n```\nDraft → Review → Revise → Approve → Publish\n```\n\n| Phase | Owner | Duration | Deliverable |\n|-------|-------|----------|-------------|\n| Draft | Author | Varies | First draft |\n| Review | Reviewers | 2–3 days | Comments\u002Ftracked changes |\n| Revise | Author | 1–2 days | Revised draft |\n| Approve | Approver | 1 day | Signed-off final |\n| Publish | Author\u002FPublisher | — | Published doc |\n\n## Version Naming\n\nUse semantic versioning for formal documents:\n\n```\nv0.1  — initial draft\nv0.2  — after author self-edit\nv1.0  — first version sent for review\nv1.1  — after first round of revisions\nv2.0  — major structural rework\n```\n\nStore versions as: `document-name-v1.0-YYYY-MM-DD.docx`\n\n## Comment Resolution\n\nWhen resolving reviewer comments, categorize each:\n\n| Category | Action |\n|----------|--------|\n| **Accept** | Make the change as suggested |\n| **Accept-Modified** | Incorporate the intent, adjusted |\n| **Reject-Explained** | Decline with a clear reason in the reply |\n| **Discuss** | Flag for synchronous conversation |\n\nReply to every comment before resolving. Unresolved comments = open decisions.\n\n## Merge Strategies\n\n### Google Docs \u002F Office 365 (simultaneous editing)\n\n- Turn on **Suggesting mode** (Google) or **Track Changes** (Word) before editing\n- Use `@mentions` to route questions to specific collaborators\n- Resolve all suggestions before marking review complete\n- Use document outline headings to assign sections per author\n\n### Markdown \u002F Git-based Docs\n\n```bash\n# Author A branches\ngit checkout -b docs\u002Fsection-3-update\n\n# Author B branches from same base\ngit checkout -b docs\u002Fsection-5-update\n\n# After review: merge A first, then B rebases\ngit checkout main\ngit merge --no-ff docs\u002Fsection-3-update\n\ngit checkout docs\u002Fsection-5-update\ngit rebase main   # resolve any conflicts\ngit checkout main\ngit merge --no-ff docs\u002Fsection-5-update\n```\n\n**Conflict resolution for prose** — when Git marks a conflict in a text block:\n1. Read both versions in context\n2. Identify the best version or blend the intent of both\n3. Never auto-accept without reading; prose merges require judgment\n\n## Review Request Template\n\n```\nSubject: Review request: [Document Title] — due [Date]\n\nHi [Reviewers],\n\nPlease review the attached document by [Date].\n\nFocus areas:\n- [Section A]: Is the logic sound?\n- [Section B]: Does the tone match our audience?\n- Any errors of fact in section C?\n\nPlease use Suggesting mode (or add comments) rather than direct edits.\n\nThanks\n```\n\n## Document Handoff Checklist\n\nBefore marking a document final:\n\n- [ ] All comments resolved or explicitly deferred\n- [ ] Track changes accepted or rejected — no open markups\n- [ ] Version number updated in filename and header\n- [ ] Changelog entry added (date, author, summary of changes)\n- [ ] Approved by designated approver\n- [ ] Stored in canonical location (Drive folder, Confluence page, etc.)\n- [ ] Stakeholders notified\n\n## Changelog Format\n\nAt the top of long-lived documents:\n\n```markdown\n## Changelog\n\n| Version | Date | Author | Summary |\n|---------|------|--------|---------|\n| v1.2 | 2024-06-01 | Jane | Added security section |\n| v1.1 | 2024-05-15 | John | Revised scope per feedback |\n| v1.0 | 2024-05-01 | Jane | Initial release |\n```\n",{"name":5,"description":7},"main","2385bbed214700617eee89482bfc974eaa0b1e22","agent-skills-curated\u002Fskills\u002Fpdf-and-documents\u002Fdoc-coauthoring","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002Fagent_eval_skills_merged_clean","https:\u002F\u002Fagent-eval-skills-merged-clean.vercel.app","https:\u002F\u002Fgithub.com\u002Fdawsonblock","2026-06-02 06:52:16",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add dawsonblock\u002Fagent_eval_skills_merged_clean --skill doc-coauthoring",{"tool":36,"command":37},"bunx","bunx skills add dawsonblock\u002Fagent_eval_skills_merged_clean --skill doc-coauthoring",{"tool":39,"command":40},"pnpm","pnpm dlx skills add dawsonblock\u002Fagent_eval_skills_merged_clean --skill doc-coauthoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002Fagent_eval_skills_merged_clean\u002Fblob\u002Fmain\u002Fagent-skills-curated\u002Fskills\u002Fpdf-and-documents\u002Fdoc-coauthoring\u002FSKILL.md",true,[],[45,53,60,68,75,82],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":49,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M72YB6PHRV534EGB17CY7DSF","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use when the user asks to build a complex web artifact, scaffold a React artifact project, bundle a single-file artifact, or generate shadcn\u002Fui-based interactive UI components.","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002Fagent_eval_skills_merged_clean\u002Fblob\u002Fmain\u002Fagent-skills-curated\u002Fskills\u002Fweb-and-frontend-development\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002Fagent_eval_skills_merged_clean\u002Fblob\u002Fmain\u002Fagent-skills-curated\u002Fskills\u002Fweb-and-frontend-development\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M72YB2VKJB4WVSNMJNTCT192","theme-factory","Generate production-ready UI themes and token systems for CSS, Tailwind, and shadcn\u002Fui. Use when users ask to apply a theme, theme an existing app, change colors and fonts, map dark\u002Flight mode tokens, or turn a palette into semantic variables. Trigger phrases include \"apply a theme\", \"theme this app\", \"change the colors\", and \"re-theme this UI\". Do not use for brand identity extraction, logo work, or full UI redesigns; use brand-guidelines or frontend-design instead.","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002Fagent_eval_skills_merged_clean\u002Fblob\u002Fmain\u002Fagent-skills-curated\u002Fskills\u002Fweb-and-frontend-development\u002Ftheme-factory\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":64,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M72YAZTJTCSHY4P1C0ZYYF2Q","frontend-design","Design and implement distinctive, production-grade frontend interfaces for web pages, components, and apps. Use when users ask for UI design, layout polish, landing pages, dashboards, React components, HTML\u002FCSS styling, or visual redesign. Trigger phrases include \"design this UI\", \"build a landing page\", \"make this look better\", \"frontend component\", \"dashboard UI\", and \"polish the interface\".","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002Fagent_eval_skills_merged_clean\u002Fblob\u002Fmain\u002Fagent-skills-curated\u002Fskills\u002Fweb-and-frontend-development\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002Fagent_eval_skills_merged_clean\u002Fblob\u002Fmain\u002Fagent-skills-curated\u002Fskills\u002Fweb-and-frontend-development\u002Ffrontend-design\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M72YAWR35KDJ299KNS3B06CX","excalidraw","Generate architecture diagrams as .excalidraw files from codebase analysis. Use when the user asks to create architecture diagrams, system diagrams, visualize codebase structure, or generate excalidraw files.","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002Fagent_eval_skills_merged_clean\u002Fblob\u002Fmain\u002Fagent-skills-curated\u002Fskills\u002Fweb-and-frontend-development\u002Fexcalidraw\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M72YASWZE58JSK3JBBX3ZB79","brand-guidelines","Extract, normalize, and apply a brand system across UI, docs, and assets. Use when users ask for a brand kit, style guide, design tokens, tone rules, or brand-consistent output. Trigger phrases include \"brand guidelines\", \"brand identity\", \"brand kit\", \"style guide\", \"brand colors\", \"brand fonts\", \"design tokens\", and \"make this on-brand\".","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002Fagent_eval_skills_merged_clean\u002Fblob\u002Fmain\u002Fagent-skills-curated\u002Fskills\u002Fweb-and-frontend-development\u002Fbrand-guidelines\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M72YAPHJY35RHFZRY7D7Z1M3","pm-skills","Project management workflows — planning, tracking, and coordination for software and product teams. Use when the user wants to create a project plan, write a PRD, create tickets, define sprint goals, write a RACI matrix, run a retrospective, or manage project scope. Trigger phrases include \"project plan\", \"project management\", \"sprint planning\", \"PRD\", \"product requirements\", \"roadmap\", \"milestone\", \"retro\", \"standup\", \"RACI\", \"risk register\", \"project timeline\".","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002Fagent_eval_skills_merged_clean\u002Fblob\u002Fmain\u002Fagent-skills-curated\u002Fskills\u002Fproductivity-and-tasks\u002Fpm-skills\u002FSKILL.md",[],[]]