Token导航 LogoToken导航

Agent Skill · 研究检索

tabular-document-review(表格文件审查)

tabular-document-review 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

tabular-document-review 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 55,093。

总安装 490周安装 20GitHub Stars 103下载 157核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:tabular-document-review(表格文件审查)
来源仓库:https://github.com/borghei/claude-skills
仓库路径:skills/tabular-document-review
安装命令:
npx skills add https://github.com/borghei/claude-skills --skill tabular-document-review
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/borghei/claude-skills --skill tabular-document-review

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

tabular-document-review 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于根据关键词或任务场景从来源线索中提取表格类文档信息。通过 npx skills add 命令从指定 GitHub 仓库安装并使用。

建议确认权限范围和维护状态,避免触发联网或文件读写操作。可结合原始 README 进一步核验具体功能和调用方式。

来源仓库内路径:skills/tabular-document-review

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/borghei/claude-skills --skill tabular-document…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

tabular-document-review 怎么安装?

在终端执行 npx skills add https://github.com/borghei/claude-skills --skill tabular-document-review。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

tabular-document-review 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

tabular-document-review 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

tabular-document-review 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

tabular-document-review 用的人多吗?

公开数据是累计安装 490 次,近一周安装 20 次,下载 157 次,GitHub 103 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

tabular-document-review 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
tabular-document-review

表格文件审查 · 本页

490103只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

⚠️ EXPERIMENTAL — This skill is provided for educational and informational purposes only. It does NOT constitute legal advice. All responsibility for usage rests with the user. Consult qualified legal professionals before acting on any output.

Tabular Document Review Skill

Overview

Production-ready toolkit for extracting structured data from multiple legal documents into a comparison matrix with citations. Supports user-defined extraction columns, parallel processing with up to 10 agents, confidence scoring, and output in markdown table or structured JSON. Designed for legal teams performing bulk contract review, NDA comparison, employment agreement analysis, and lease review.

Table of Contents

Tools

1. Document Discovery (scripts/document_discovery.py)

Scan a directory for legal documents and generate an inventory manifest.

python scripts/document_discovery.py /path/to/contracts

python scripts/document_discovery.py /path/to/ndas --types pdf,docx --json

python scripts/document_discovery.py /path/to/leases --types pdf,docx,txt,md --min-size 1024

2. Extraction Aggregator (scripts/extraction_aggregator.py)

Aggregate multiple extraction result JSONs into a unified comparison matrix.

python scripts/extraction_aggregator.py \
  --results extraction_1.json extraction_2.json extraction_3.json

python scripts/extraction_aggregator.py \
  --results-dir ./extraction_results/ --json

python scripts/extraction_aggregator.py \
  --results-dir ./extraction_results/ \
  --format markdown \
  --output review_matrix.md

python scripts/extraction_aggregator.py \
  --results extraction_1.json extraction_2.json \
  --columns "Parties,Effective Date,Term,Governing Law"

Reference Guides

ReferencePurpose
references/extraction_methodology.mdDocument extraction best practices, JSON schema, agent prompts
references/common_extraction_columns.mdPre-defined column sets for contracts, NDAs, employment, leases

Workflows

5-Step Document Review Pipeline

StepActionToolOutput
1. Gather RequirementsDefine document folder, output filename, columns to extractManualColumn list, file path
2. Discover DocumentsScan directory for target documentsdocument_discovery.pyDocument manifest JSON
3. Process DocumentsExtract values per column with citations (parallel agents)AI agents (external)Per-document extraction JSONs
4. Collect ResultsAggregate extraction JSONs into unified matrixextraction_aggregator.pyConsolidated matrix
5. Generate OutputExport as markdown table or structured JSONextraction_aggregator.pyFinal deliverable

Parallel Processing Strategy

AgentsDocuments per AgentUse When
1All1-5 documents
2-3ceil(N/agents)6-15 documents
4-6ceil(N/agents)16-40 documents
7-10ceil(N/agents)41-100 documents
10 (max)ceil(N/10)100+ documents

Agent Prompt Template

Each agent receives a prompt structured as:

You are reviewing {count} legal documents. For each document, extract the
following columns:

{column_definitions}

For each value extracted:
1. Provide the exact value found
2. Include the page number (PDF) or section/paragraph (DOCX/MD)
3. Rate your confidence: HIGH (exact match), MEDIUM (inferred), LOW (uncertain)
4. If not found, record "NOT FOUND" with confidence LOW

Output as JSON per the extraction schema.

Confidence Scoring

LevelColor CodeDefinition
HIGHGreenExact value found with clear citation
MEDIUMYellowValue inferred from context; multiple possible interpretations
LOWRed / Not FoundValue uncertain or not found in document

Output Format

Sheet 1: Document Review

DocumentPartiesEffective DateTermGoverning Law...
contract_a.pdfAcme / Beta [p.1]2026-01-15 [p.2]3 years [p.3]Delaware [p.12]...
contract_b.pdfGamma / Delta [p.1]NOT FOUND2 years [p.4]New York [p.10]...

Sheet 2: Summary

MetricValue
Documents processed25
Columns extracted8
Average confidence87%
Not found rate12%

Extraction Scenarios

Contract Review

ColumnWhat to Extract
PartiesAll contracting parties with full legal names
Effective DateContract effective or execution date
TermDuration of the agreement
RenewalAuto-renewal terms and notice period
Governing LawJurisdiction governing the agreement
Liability CapMaximum liability amount or formula
IndemnificationIndemnification obligations and scope
IP OwnershipIntellectual property ownership provisions
Termination RightsTermination triggers and notice requirements
Data ProtectionData protection or privacy obligations

NDA Review

ColumnWhat to Extract
PartiesDisclosing and receiving parties
TypeMutual or one-way
Definition ScopeHow "confidential information" is defined
ExceptionsStandard exceptions to confidentiality
TermDuration of confidentiality obligations
SurvivalSurvival period after termination
Return/DestructionObligations on termination
RemediesAvailable remedies for breach

Troubleshooting

ProblemCauseSolution
Discovery finds 0 documentsWrong path or file typesVerify path exists; check --types matches actual file extensions
Extraction JSONs have wrong schemaAgent prompt incompleteUse the extraction schema from extraction_methodology.md
Aggregator shows conflictsMultiple values for same cellReview source documents; aggregator marks conflicts for manual review
High "NOT FOUND" rateColumns too specific for document typeUse column definitions from common_extraction_columns.md; broaden definitions
Confidence all LOWAgent unable to locate valuesCheck column definitions are specific enough; verify document is readable
Aggregator crashes on large setToo many result files loaded at onceProcess in batches of 50 results; use --columns to limit output width
Markdown table misalignedLong values or special charactersUse --format json for machine processing; truncate long values
Missing citationsAgent did not include page/section referencesReinforce citation requirement in agent prompt; check extraction schema

Success Criteria

  • Extraction Coverage: 90%+ of defined columns populated across all documents
  • Confidence Distribution: 70%+ of extractions rated HIGH confidence
  • Citation Accuracy: Every extracted value includes verifiable page/section citation
  • Processing Speed: 50+ documents processed within 30 minutes using parallel agents
  • Matrix Completeness: Final matrix includes all documents and all columns with no orphan rows

Scope & Limitations

This skill covers:

  • Document inventory and discovery across PDF, DOCX, TXT, and MD formats
  • Aggregation of extraction results from parallel agent processing into unified matrix
  • Pre-defined column sets for contracts, NDAs, employment agreements, and leases
  • Confidence scoring and conflict detection for extracted values
  • Markdown and JSON output formats

This skill does NOT cover:

  • Actual document parsing or text extraction (requires external libraries or AI agents)
  • OCR processing for scanned documents
  • Excel/XLSX output generation (use JSON output and convert externally)
  • Automated legal analysis or risk assessment of extracted values
  • Document comparison or redlining between versions

Anti-Patterns

Anti-PatternWhy It FailsBetter Approach
Vague column definitions"Date" could match dozens of dates in a contractUse specific definitions: "Effective Date" with guidance on where to look
Skipping document discoveryUnknown document count leads to wrong agent allocationAlways run discovery first; use manifest for pipeline planning
Ignoring LOW confidence resultsMissing or uncertain data treated as factReview all LOW confidence cells manually; flag in final report
Processing 100+ docs with 1 agentSlow, context window overflow, quality degradationUse parallel processing: ceil(N/10) documents per agent, max 10 agents
No citation requirementCannot verify extracted values against sourceRequire page/section citation for every extraction; reject uncited values

Tool Reference

scripts/document_discovery.py

Scan directory for legal documents and generate inventory manifest.

usage: document_discovery.py [-h] [--json]
                              [--types TYPES]
                              [--min-size MIN_SIZE]
                              [--max-size MAX_SIZE]
                              directory

positional arguments:
  directory             Path to directory containing documents

options:
  -h, --help            Show help message and exit
  --json                Output in JSON format
  --types TYPES         Comma-separated file extensions to include
                        (default: pdf,docx,doc,txt,md,rtf)
  --min-size MIN_SIZE   Minimum file size in bytes (default: 0)
  --max-size MAX_SIZE   Maximum file size in bytes (default: no limit)

scripts/extraction_aggregator.py

Aggregate extraction results into unified comparison matrix.

usage: extraction_aggregator.py [-h] [--json]
                                 [--results RESULTS [RESULTS ...]]
                                 [--results-dir RESULTS_DIR]
                                 [--format {markdown,json}]
                                 [--columns COLUMNS]
                                 [--output OUTPUT]

options:
  -h, --help            Show help message and exit
  --json                Output in JSON format (alias for --format json)
  --results             One or more extraction result JSON files
  --results-dir         Directory containing extraction result JSON files
  --format              Output format: markdown table or JSON (default: markdown)
  --columns             Comma-separated column names to include (default: all)
  --output              Write output to file instead of stdout

平台分布

Codex

37.77%
按下载量换算59

Claude

29.4%
按下载量换算46

Cursor

17.31%
按下载量换算27

Gemini CLI

8.76%
按下载量换算14

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills