Claude Project: Build a Searchable Team Script Library

For Network Administrators

Tools: Claude Pro | Time to build: 1-2 hours | Difficulty: Intermediate-Advanced Prerequisites: Comfortable using Claude for scripting — see Level 3 guide: "Use Claude Pro to Analyze Vendor Documentation"

What This Builds

You'll create a Claude Project loaded with your team's PowerShell and Bash scripts, annotated with descriptions, when to use them, and required permissions. Any team member queries the library in plain English: "Do we have a script that exports all AD group memberships to CSV?" or "What script do we use for monthly disk space reporting?" instead of hunting through shared drives or asking the senior admin. Scripts stop living on individuals' laptops and start being team assets.

Prerequisites

• Claude Pro subscription ({{tool:Claude.price}}) — Claude Projects require Pro
• Existing scripts to catalog (even 5-10 to start)
• 1-2 hours for initial setup; 15 minutes per script added after

The Concept

Normally, each Claude conversation starts fresh. A Project maintains a persistent knowledge base across conversations — you upload files once and query them anytime. For a script library, this means: upload your scripts + their documentation, then query the library in plain English instead of a file explorer.

Think of it as a card catalog for your script collection that can also explain what each script does and help you find the right one for the situation.

Build It Step by Step

Part 1: Catalog and Annotate Your Existing Scripts

Before uploading, create a simple inventory document. Even if you only have 10 scripts, this discipline makes the library useful immediately.

For each script, write a short annotation:

Script: Get-InactiveADUsers.ps1
What it does: Finds all enabled AD users with no logon activity in the last X days. X is configurable via parameter.
When to use: Monthly license cleanup, security audits, offboarding verification
Required permissions: Domain User + read access to AD (no admin rights needed)
Parameters: -DaysInactive (required), -OutputPath (optional, defaults to C:\Reports\), -ExcludeGroup (optional, exclude specific group members)
Output: CSV with Name, SamAccountName, Email, Department, LastLogonDate
Limitations: LastLogonDate has ~14-day replication lag — don't use for real-time accuracy
Last tested: 2026-01-15, Windows Server 2022 domain

Create this annotation for each script you have. Save all annotations in a single document (script-inventory.md or script-catalog.txt).

Part 2: Set Up Your Claude Project

1. Log in to {{tool:Claude.url}}
2. In the left sidebar, click Projects → + New Project
3. Name it: "IT Script Library — [Company/Team Name]"
4. Click Edit project instructions and paste:

You are the script library assistant for [Company] IT team. You have access to our PowerShell and Bash script catalog.

When someone asks about a script:
1. Check if we have an existing script that does what they need
2. If yes: describe what it does, list required parameters, note permissions needed, and flag any limitations
3. If no: say we don't have one yet and suggest what it would need to do (so they can request one)

When asked to help write a new script:
1. Check if something similar exists in our library first
2. If a similar script exists, suggest modifying it rather than starting from scratch
3. Use our existing scripts' style: try/catch error handling, log to C:\Logs\, WhatIf support for destructive operations, timestamps in output

Always remind users to test in a dev/test environment before running against production.

Part 3: Upload Your Script Catalog

1. In the Project, click Add content
2. Upload your script inventory/annotation document first
3. Upload the actual script files (.ps1, .sh, .py)
4. For each upload, Claude will be able to read and reference the content

Tip: If you have many scripts, organize them by category:

• scripts-ad-user-management.md (all AD user scripts + annotations)
• scripts-server-monitoring.md
• scripts-network-tools.md
• scripts-reporting.md

Part 4: Test with Real Queries

Start a new conversation in the Project:

Test 1 — Find an existing script:

Do we have a script that checks disk space on all our servers and sends an email report?

Expected good answer: "Yes — DiskSpaceReport.ps1. It takes a server list as a CSV input file, checks all drives, and sends an HTML email report to the address you specify. Required parameters: -ServerListPath, -ReportEmail. No admin rights needed, just WinRM access."

Test 2 — Find what's missing:

Do we have anything that monitors certificate expiration dates on our servers?

Expected good answer: "We don't have a certificate monitoring script in the library yet. Such a script would need to: connect to each server, check IIS and Windows cert stores, and alert if any cert expires within [X] days. Want me to help write one?"

Test 3 — Style consistency:

I need a new script to check if all servers in a list are responding to WinRM. Write it consistent with our team's scripting style.

Expected good answer: A script that matches your team's patterns — try/catch, C:\Logs\ logging, WhatIf parameter — because Claude learned your style from the uploaded scripts.

Part 5: Share with Your Team

For sharing, create a simple "how to use the script library" page:

# IT Script Library — How to Use

Go to: claude.ai → Projects → IT Script Library

Start a NEW conversation each time you use it.

Good queries:
✓ "Do we have a script that [task]?"
✓ "What parameters does [ScriptName] take?"
✓ "I need a script to [task] — do we have one? If not, help me write one."
✓ "Show me the scripts we have for AD user management"

Always test scripts in dev before running in production.
For new scripts added to the library, update the catalog document and re-upload it.

Real Example: Onboarding a Junior Admin

Scenario: A new junior admin joins your team. They need to run the monthly inactive account report but don't know which script to use or how to run it.

Without the script library: They ask the senior admin, interrupt their work, take 15 minutes to get a walk-through, and probably ask the same question 3 months later.

With the script library:

Junior admin query: "I need to run the monthly inactive AD account report. Which script do I use and what parameters do I need?"

Output: "Use Get-InactiveADUsers.ps1, located at \scripts\ad. Run it with: .\Get-InactiveADUsers.ps1 -DaysInactive 90 -OutputPath C:\Reports\. This exports a CSV of all enabled users with no logins in 90 days. Note: LastLogonDate has up to 14 days of replication lag — don't use the results for real-time decisions. The report lands in C:\Reports\ with today's date in the filename."

Senior admin interruption: 0.

What to Do When It Breaks

• Claude says "I don't have a script for that" when you know you uploaded one → The description in your catalog document may not match the query wording. Improve the annotation: add synonyms for what the script does ("disk space = free disk = storage utilization").
• Claude generates new scripts that don't match your team style → Upload 2-3 of your best-written existing scripts as explicit style examples. Add to your instructions: "Match the style of the scripts in our library."
• Team members get outdated information → The catalog document needs updating when scripts change. Create a simple process: when a script is updated, update its annotation and re-upload the catalog. Date each annotation.
• Shared Claude Pro access isn't available → Use a shared ChatGPT Custom GPT instead (see Level 4 Custom GPT guide) — same concept, different platform, easier team sharing via link.

Variations

• Simpler version: Skip the Project and use a regular Claude conversation. Upload the catalog document at the start of each session. Loses persistence but works without Pro.
• Extended version: Add your ticketing system's common resolutions alongside scripts — so admins can find both the script and the documented resolution procedure in one query.

What to Do Next

• This week: Create your script catalog document with 10+ existing scripts, set up the Project, and run 5 test queries
• This month: Make it a habit to add every new script to the catalog on the day you write it — 10 minutes when the context is fresh vs. 30 minutes trying to remember later
• Advanced: Add change history to your catalog ("Added -ExcludeOU parameter 2026-02-10") so team members know which version of a script to expect

Advanced guide for network administrator professionals. These techniques use more sophisticated AI features that may require paid subscriptions.