Skip to content

Latest commit

 

History

1 Commit

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 

Repository files navigation

InspectDoc — Claude Code Skill

Adds an /inspectdoc skill to Claude Code so your customers can analyze documents for authenticity directly from their terminal.

What it does

Once installed, customers type /inspectdoc in any Claude Code conversation. The skill has two modes:

Analyze mode — authenticate specific documents:

  1. Ask for the document file path(s)
  2. Call the InspectDoc API automatically
  3. Return a formatted authenticity report with risk levels

Test & Report mode — run a diagnostic suite:

  1. Health-check the API
  2. Run a set of test documents through the API
  3. Produce a pass/fail test report (and optionally save it to a file)

Supports single documents, receipts, batch analysis (up to 20 files), and test suite runs.

Requirements

Installation

Option 1 — Script (recommended)

# Clone or download this repo, then:
bash claude-skill/install.sh

Option 2 — Manual

Copy inspectdoc.md to your Claude Code skills directory:

mkdir -p ~/.claude/skills
cp inspectdoc.md ~/.claude/skills/inspectdoc.md

Setup

Add your API key to your shell profile (~/.zshrc, ~/.bashrc, etc.):

export INSPECTDOC_API_KEY=your_api_key_here

Then reload your shell:

source ~/.zshrc

Usage

In any Claude Code conversation:

/inspectdoc

Claude will ask what you want to do. You can also be direct:

/inspectdoc check if this invoice is real: ~/Downloads/invoice.pdf
/inspectdoc run tests on my documents folder ~/test-docs/
/inspectdoc check API health and run diagnostics

Example: Analysis Output

File: invoice.jpg
Verdict: SUSPICIOUS
Authenticity Score: 0.52 / 1.0

| Check           | Risk Level | Score |
|-----------------|-----------|-------|
| Tampering       | MEDIUM    | 0.48  |
| AI Generated    | LOW       | 0.12  |
| Digital Editing | HIGH      | 0.71  |
| Metadata        | MEDIUM    | 0.44  |

Summary: The document shows notable signs of digital editing with
medium-confidence tampering indicators. Manual review is recommended.

Example: Test Report Output

================================================
  InspectDoc Test Report
  2026-03-05_14-22-01
  API: https://api.inspectdoc.com
================================================

  SUMMARY
  -------
  API Health:    PASSED
  Total Tests:   4
  Passed:        3   (75%)
  Failed:        1

  TEST RESULTS
  ------------
  [PASSED] invoice_sample.jpg     score: 0.87  risk: LOW
  [PASSED] receipt_real.png       score: 0.91  risk: LOW
  [FAILED] tampered_id.jpg        HTTP 500 — server error
  [PASSED] passport_scan.jpg      score: 0.74  risk: LOW

  FAILED TESTS
  ------------
  tampered_id.jpg
    Error: Internal server error
    Suggestion: Check file format or contact support@inspectdoc.com

================================================
  Result: 1 FAILURE DETECTED
================================================

Support

About

Claude Code skill for document authentication using the InspectDoc API

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages