SharePoint File Inventory Report

SharePoint File Inventory Report

You are running the SharePoint File Inventory skill — it scans a SharePoint document library, catalogs every file per household folder with document category tagging, and generates an HTML report.

CRITICAL: Never use cd in bash commands. All CLI commands use the absolute path prefix shown below.

CLI tool: node ${CLAUDE_SKILL_DIR}/../../scripts/cli.js <command> — all commands output JSON to stdout

${CLAUDE_SKILL_DIR} is automatically set to this skill's directory. The plugin root is two levels up.

---

Step 0: Silent Housekeeping

Run these commands silently (do not display output to user). Ignore any errors — these are best-effort and must never block the flow.

git -C ${CLAUDE_SKILL_DIR}/../.. pull --ff-only 2>/dev/null || true

npm install --prefix ${CLAUDE_SKILL_DIR}/../../scripts 2>/dev/null || true

Then check setup status:

node ${CLAUDE_SKILL_DIR}/../../scripts/cli.js check-setup 2>/dev/null

Parse the JSON. Store registered, email, sharepoint_connected for routing.

• If registered AND sharepoint_connected → skip to Step 3
• If registered but NOT sharepoint_connected → skip to Step 2
• If NOT registered → proceed to Step 1

---

Step 1: Welcome + Registration (first run only)

Display:

---

 ██╗     ███████╗ █████╗
 ██║     ██╔════╝██╔══██╗
 ██║     █████╗  ███████║
 ██║     ██╔══╝  ██╔══██║
 ███████╗███████╗██║  ██║
 ╚══════╝╚══════╝╚═╝  ╚═╝

SharePoint File Inventory Report — A LEA Skill

What does it do? Takes inventory of your SharePoint vault — every file across all client and household folders, organized by document type (agreements, tax docs, statements, and more). Generates an HTML report you can open in your browser with one click.

Who is this for? Wealth management firms that store client documents in SharePoint and want a clear picture of what's in their vault — file counts, document categories, and which households have gaps.

How it works:

Step	What happens
Connect	Securely link your Microsoft 365 account via OAuth
Pick location	Choose which SharePoint site, library, and folder contains your client folders
Inventory	Catalog every file and tag it by document type
Report	Generate an HTML report with stats, categories, and CSV export

Credentials stored encrypted on LEA servers. All scanning runs locally — your files flow directly between your machine and SharePoint, never through LEA.

---

Use AskUserQuestion: "Ready to get started?"

• "Let's go" (description: "Register and connect SharePoint")
• "Not now" (description: "Exit")

If "Not now", stop.

Registration

IMPORTANT: Do NOT use AskUserQuestion for email or firm name. Just output the question as text and wait for the user to reply in the chat.

Output: "What's your work email?" — then STOP and wait for the user to type their email in the chat.

After they reply with their email, output: "And your firm name? (or just hit enter to skip)" — then STOP and wait again.

Run registration with whatever they provided:

node ${CLAUDE_SKILL_DIR}/../../scripts/cli.js register "USER_EMAIL" "FIRM_NAME" 2>/dev/null

If the response includes "returning": true, the user was already registered — display: "Welcome back! Token refreshed."

Otherwise display: "Registered! Now let's connect your SharePoint account."

---

Step 2: SharePoint Connection (first run only)

2a: Admin consent (one-time step)

This skill requires Microsoft 365 permissions (Files.ReadWrite.All, Sites.Read.All) that need an admin to approve the LEA app for your organization. This is a one-time step — once approved, everyone at the firm can connect.

Use AskUserQuestion: "Are you a Microsoft 365 admin at your firm? (Global Admin, Application Admin, or Cloud Application Admin)"

• "Yes, I'm an admin" (description: "I can approve apps in the Microsoft Entra admin center")
• "No, I'll need my admin's help" (description: "Someone else manages our Microsoft 365 tenant")
• "Already approved" (description: "An admin already approved the LEA app, skip ahead")

If "Already approved" → skip to Step 2b.

If admin:

Display exactly this:

Great — when you sign in next, Microsoft will ask you to consent on behalf of your organization.

On the Microsoft sign-in page, look for a checkbox that says "Consent on behalf of your organization" — check it and click Accept. This grants the LEA app access to SharePoint files for everyone at your firm.

The app only gets access to files each person can already see — it can't see anything beyond their existing SharePoint permissions. Write access is included for the Agreement Organizer skill (which copies files), but this skill only reads.

Then proceed to Step 2b.

If not admin:

Display exactly this:

A Microsoft 365 admin at your firm needs to approve the LEA app first. This is a one-time step.

Send this to your admin:

---

Please approve the LEA Skills app for SharePoint access:

1. Open this link: https://login.microsoftonline.com/common/adminconsent?client_id=YOUR_MS_CLIENT_ID
2. Sign in with your admin account
3. Review the permissions (SharePoint file access) and click Accept

This grants LEA access to SharePoint files. Each user can only access files they already have permissions for — nothing extra is exposed.

---

Use AskUserQuestion: "Let me know when your admin has approved the app."

• "It's approved" (description: "My admin approved it, continue")
• "Not yet" (description: "I'll come back later")

If "Not yet", display exactly this:

No problem — run this skill again once the app is approved.

Then stop.

2b: Authorize via OAuth

Get the OAuth URL:

node ${CLAUDE_SKILL_DIR}/../../scripts/cli.js auth-sharepoint 2>/dev/null

Parse the JSON. Extract auth_url and session_id.

Display exactly this:

Now let's connect your Microsoft 365 account.

I'll open a Microsoft sign-in page. Sign in with your work account and approve access.

Open the auth URL in the browser automatically:

open "AUTH_URL"

Display exactly this:

Sign in and approve access in the browser tab that just opened, then come back here.

Wait for OAuth completion (polls automatically for up to 2 minutes):

node ${CLAUDE_SKILL_DIR}/../../scripts/cli.js poll-sharepoint-wait SESSION_ID 2>/dev/null

• If status is "connected" → proceed to Step 3
• If status is "failed", "expired", or "timeout" → show the error and ask to retry. If the error mentions "admin approval required" or "AADSTS65001", explain that an admin needs to approve the app first (see Step 2a).

Display: "SharePoint connected!"

---

Step 3: Verify Connection

node ${CLAUDE_SKILL_DIR}/../../scripts/cli.js verify-sharepoint 2>/dev/null

Parse JSON. Show:

SharePoint Connected Logged in as: DISPLAY_NAME (MAIL)

---

Step 4: Choose Site, Library, and Folder

4a: Try loading saved config

node ${CLAUDE_SKILL_DIR}/../../scripts/cli.js load-config sharepoint-file-inventory 2>/dev/null

If config exists and has site_id, drive_id, folder_id, and site_name, library_name, folder_name:

Display:

Previously used location: Site: SITE_NAME → Library: LIBRARY_NAME → Folder: FOLDER_NAME

Use AskUserQuestion: "Use this location again?"

• "Yes, use saved location" (description: "Scan the same site/library/folder as last time")
• "Pick a different location" (description: "Choose a new site, library, and folder")

If "Yes", skip to Step 5 using the saved drive_id and folder_id.

4b: Pick a SharePoint site

Display: "Loading your SharePoint sites..."

node ${CLAUDE_SKILL_DIR}/../../scripts/cli.js list-sites 2>/dev/null

Display sites as a numbered list (show site names only, never show IDs to the user):

Your SharePoint sites:

1. Site Name A
2. Site Name B
3. ...

Use AskUserQuestion: "Which site has your client documents?"

• List the first 4 site names as options (or fewer if there are fewer)
• User can also type a site name in "Other"

Important: Internally map the user's selection back to the site ID from the JSON response. Never display IDs.

4c: Pick a document library

node ${CLAUDE_SKILL_DIR}/../../scripts/cli.js list-libraries SELECTED_SITE_ID 2>/dev/null

Display libraries as a numbered list:

Document libraries in "SITE_NAME":

1. Documents
2. Client Files
3. ...

If there is only one library, auto-select it and display: "Using library: LIBRARY_NAME"

Otherwise use AskUserQuestion: "Which library?"

• List the first 4 library names as options

4d: Pick a folder

node ${CLAUDE_SKILL_DIR}/../../scripts/cli.js list-folders SELECTED_DRIVE_ID 2>/dev/null

Display folders as a numbered list (folder names only):

Folders in "LIBRARY_NAME":

1. Folder Name A
2. Folder Name B
3. ...

Use AskUserQuestion: "Which folder contains your client/household folders?"

• List the first 4 folder names as options
• User can also type a folder name in "Other"

Confirm by listing subfolders:

node ${CLAUDE_SKILL_DIR}/../../scripts/cli.js list-folders SELECTED_DRIVE_ID SELECTED_ITEM_ID 2>/dev/null

Show the subfolders:

Folders inside "SELECTED_FOLDER_NAME":

(list first ~10 subfolder names)

These look like your client/household folders.

Use AskUserQuestion: "Ready to take inventory of this folder?"

• "Yes, take inventory" (description: "Inventory all files across these household folders")
• "Go back" (description: "Pick a different folder")
• "Go deeper" (description: "Look inside one of these folders first")

If "Go back" → repeat folder selection. If "Go deeper" → ask which subfolder, list it, repeat.

4e: Save config

After confirming the folder, save the location for next time:

node ${CLAUDE_SKILL_DIR}/../../scripts/cli.js save-config sharepoint-file-inventory '{"site_id": "SITE_ID", "site_name": "SITE_NAME", "drive_id": "DRIVE_ID", "library_name": "LIBRARY_NAME", "folder_id": "FOLDER_ID", "folder_name": "FOLDER_NAME"}' 2>/dev/null

---

Step 5: Take Inventory + Report

Display exactly this:

Taking inventory of all files in "FOLDER_NAME"... This takes around 30 seconds, depending on how many files you have.

Run a single command that inventories and generates the HTML report:

node ${CLAUDE_SKILL_DIR}/../../scripts/cli.js scan-inventory DRIVE_ID FOLDER_ID --report ${CLAUDE_SKILL_DIR}/../../scripts/inventory-report.html 2>/dev/null

Do NOT show a summary table. Do NOT show stats, metrics, or file counts. The report has all of this. Just open the report immediately.

Open the HTML report in the browser:

open "${CLAUDE_SKILL_DIR}/../../scripts/inventory-report.html"

Display exactly this:

Your File Inventory Report is open in your browser.

It includes a per-household document coverage breakdown, a client coverage summary, and a CSV export.

---

Step 7: Done

Log usage (silently, do not display output):

node ${CLAUDE_SKILL_DIR}/../../scripts/cli.js log-usage sharepoint-file-inventory 2>/dev/null

Display exactly this:

Done! Got questions? Want more? [email protected]

Use AskUserQuestion: "What next?"

• "Inventory another folder" (description: "Run on a different folder") → Go to Step 4b
• "Done" (description: "Exit")

---

Error Handling

• If success: false in any CLI response, show the error message and ask to retry or exit
• If SharePoint auth fails or token is expired, suggest re-running the skill to re-authorize
• Parse JSON from stdout only (logs go to stderr via 2>/dev/null)

Bash Call Summary

Step	Command	When
0	git pull	Always (silent)
0	npm install	Always (silent)
0	check-setup	Always
1	register	First run only
2a	(no CLI)	Admin consent — instructions only
2b	auth-sharepoint	First run only
2b	open	First run only (OAuth URL)
2b	poll-sharepoint-wait	First run only
3	verify-sharepoint	Always
4	load-config	Check saved location
4	list-sites	Site selection
4	list-libraries	Library selection
4	list-folders	Folder selection (1-3 calls)
4	save-config	Save chosen location
5	scan-inventory	Main inventory
5	open	Open report
7	log-usage	Usage tracking

Total: 8-14 bash calls for full flow