Agent Skills
› fanfan-de/anybox
› google-drive-comments
google-drive-comments
GitHub用于在Google Drive文件（Docs/Sheets/Slides等）上撰写、回复和解决评论。强调需先定位文件，读取上下文，并在新评论中附带精确证据（如引用文本、单元格范围或幻灯片编号），以弥补API创建评论可能缺乏原生锚点的问题。
Trigger Scenarios
用户要求留下评论
审查带有评论的文件
回复评论线程
解决Drive评论
Install
npx skills add fanfan-de/anybox --skill google-drive-comments -g -y
SKILL.md
Frontmatter
{
"name": "google-drive-comments",
"description": "Write, reply to, and resolve Google Drive comments on Docs, Sheets, Slides, and Drive files with evidence-backed location context. Use when the user asks to leave comments, review a file with comments, respond to comment threads, or resolve Drive comments."
}
Google Drive Comments
Use this skill for comment workflows in the unified Google Drive plugin. Drive comments can apply to Docs, Sheets, Slides, and generic Drive files, but API-created comments may appear unanchored in the Google editor UI. Every new top-level comment must therefore include enough surface-specific evidence for the reader to find the target without relying on native UI anchoring.
Workflow
- Ground the target file first.
- If the user did not provide an exact file URL or ID, search Drive, list recent files, list folders, or read metadata until the target file is unambiguous.
- Identify whether the file is a Google Doc, Sheet, Slides deck, or generic Drive file before drafting comments.
- Read the surface that will be commented on.
- For Docs or text-like files, read the document text around each likely target.
- For Sheets, read spreadsheet metadata first, then read the specific sheet tabs and ranges that may receive comments.
- For Slides, read the presentation outline or text first, then read specific slides or thumbnails when visual context is needed.
- Do not guess a target quote, slide number, sheet name, or cell range from memory or search snippets.
- Draft all intended comment updates before writing.
- Prefer one
bulk_update_file_commentscall for all creates, replies, and resolves in the same user request. - Keep the batch to the action limit exposed by the tool. If the request needs more comments than the limit, ask before splitting into another batch.
- For replies and resolves, use existing comment IDs from the live comment thread data.
- Attach surface-specific evidence to every new top-level comment.
- The comment body must explicitly name or quote the target evidence, because the Google editor UI may not show API-created anchors.
- Docs or text-like files: include
quoted_textwith the exact sentence, phrase, heading, or nearby text the comment refers to. Also quote that same text in the comment body when the critique would otherwise say "this sentence" or "this paragraph." - Sheets: include
sheet_cell_rangewith the sheet name and A1 cell or range, such asBudget!C12orPipeline!A2:D10. Also name that sheet and range in the comment body, and includequoted_textwhen a displayed value, header, formula, or label would make the target clearer. - Slides: include
slide_number. Also name that slide number in the comment body, and includequoted_textwhen commenting on a title, bullet, label, chart text, or other visible slide text. - Generic Drive files: if no structured surface exists, make the comment content explicitly name the file-level, page-level, timestamp-level, or section-level evidence it refers to.
- Reject vague comments before sending them.
- Do not create comments that say only "this sentence," "this paragraph," "this slide," "this cell," or similar without the matching evidence field.
- If the model has a useful critique but cannot identify the exact evidence target, either turn it into an explicitly file-level summary comment or omit it and say the target was not specific enough.
- Do not rely on tool fields alone for location context. If the comment body would feel hand-wavy after removing the hidden tool fields, rewrite it before sending.
- Verify the result.
- After writing, summarize how many comments were created, replied to, or resolved.
- Mention the evidence used for the highest-risk comments, especially any file-level comments that intentionally do not target a specific quote, slide, or cell.
Limitations
- Do not rely on Drive comment
anchordata for Google Docs, Sheets, or Slides unless the connector explicitly documents a provider-supported shape for that surface. Drive API-created comments may still display as unanchored in the Google editor UI. - The evidence fields are the durable location contract for this workflow: exact quoted text for Docs and text-like files, sheet/cell range for Sheets, and slide number plus visible text for Slides.
Version History
- 08dc189 Current 2026-07-05 19:00
