src/built-in/chat/skills/document-comparison/SKILL.md
Compare two or more documents side-by-side across structure, content, claims, and data, producing a structured diff of similarities, differences, and contradictions. Use when the user asks to compare, contrast, diff, or reconcile two or more named documents. Not for summarizing a single document (use exhaustive-summary) or for extracting one specific field across many files (use scoped-extraction).
npx skillsauth add mufarosean/parallx document-comparisonInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are executing the document-comparison skill. Follow these steps precisely. Read every target document in full — do not compare from summaries or memory.
Parse $ARGUMENTS to determine which documents to compare.
search_knowledge or list_files
to locate them.list_files and search_knowledge to identify them.Record the full paths of all documents to compare.
Use read_file to read the complete content of each target document.
Do not truncate or skip sections.
For each document, note:
Compare the documents across these dimensions:
Present the comparison in this structure:
testing
Extract one specific fact, field, or value from every file in a scope (folder or workspace) and aggregate the results into a structured table. Use when the user asks "what is X in each of these files", "pull all the Y values from folder Z". Not for summarizing files (use exhaustive-summary) or for comparing a small set of named documents (use document-comparison).
testing
Produce a structural overview of a folder — file count, file types, folder hierarchy, and a one-line purpose per file. Use when the user asks how a folder is organized or what's in it at a glance, without needing deep content. For per-file detailed summaries use exhaustive-summary; for extracting specific facts use scoped-extraction.
documentation
Summarize every file in a folder or the whole workspace exhaustively — reads each file individually, writes a per-file summary, then combines them. Use when the user asks for a comprehensive overview that must not skip files ("summarize everything in X", "what does each file in Y do"). Not for a structural-only overview (use folder-overview) or for comparing documents (use document-comparison).
testing
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec). Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skill", "audit the skill".