Gc Review
alirezarezvani/claude-skills
/cs:gc-review <plan — General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface.
Assess IT vendors and third-party partners with multi-factor risk scoring and regulatory compliance checklists.
$ npx skills add borghei/Claude-Skills --skill vendor-due-diligence -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills vendor-due-diligence --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/legal/vendor-due-diligence .claude/skills/vendor-due-diligence && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vendor-due-diligence" agent skill from https://github.com/borghei/Claude-Skills/tree/main/legal/vendor-due-diligence into .claude/skills/vendor-due-diligence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-due-diligence", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/legal/vendor-due-diligenceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill vendor-due-diligence -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills vendor-due-diligence --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/legal/vendor-due-diligence .agents/skills/vendor-due-diligence && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vendor-due-diligence" agent skill from https://github.com/borghei/Claude-Skills/tree/main/legal/vendor-due-diligence into .agents/skills/vendor-due-diligence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-due-diligence", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill vendor-due-diligence -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills vendor-due-diligence --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/legal/vendor-due-diligence .cursor/skills/vendor-due-diligence && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vendor-due-diligence" agent skill from https://github.com/borghei/Claude-Skills/tree/main/legal/vendor-due-diligence into .cursor/skills/vendor-due-diligence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-due-diligence", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path legal/vendor-due-diligence--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill vendor-due-diligence -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills vendor-due-diligence --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/legal/vendor-due-diligence .gemini/skills/vendor-due-diligence && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vendor-due-diligence" agent skill from https://github.com/borghei/Claude-Skills/tree/main/legal/vendor-due-diligence into .gemini/skills/vendor-due-diligence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-due-diligence", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills vendor-due-diligenceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill vendor-due-diligence -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/legal/vendor-due-diligence .github/skills/vendor-due-diligence && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vendor-due-diligence" agent skill from https://github.com/borghei/Claude-Skills/tree/main/legal/vendor-due-diligence into .github/skills/vendor-due-diligence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-due-diligence", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill vendor-due-diligence -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills vendor-due-diligence --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/legal/vendor-due-diligence .opencode/skills/vendor-due-diligence && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vendor-due-diligence" agent skill from https://github.com/borghei/Claude-Skills/tree/main/legal/vendor-due-diligence into .opencode/skills/vendor-due-diligence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-due-diligence", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
vendor-due-diligenceAssess IT vendors and third-party partners with multi-factor risk scoring and regulatory compliance checklists.
Vendor Due Diligence is an agent skill from borghei/Claude-Skills. Assess IT vendors and third-party partners with multi-factor risk scoring and regulatory compliance checklists. Use when evaluating technology vendors.
Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/monitoring_framework.md`, `references/regulatory_checklists.md` and `references/risk_assessment_framework.md`).
It sits in Legal & Compliance, covering Fundraising and pitch decks, Regulatory compliance and Vendor and procurement management. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
2 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Vendor Due Diligence loads about 3.2k tokens when it runs, and up to ~16k if it reads all its reference files. Until then it costs about 43 tokens; SKILL.md has 1,249 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 1,249 words, ~3,171 tokens.
.claude/skills/vendor-due-diligence/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.⚠️ 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.
Production-ready framework for assessing IT service providers, technology vendors, and third-party partners. Provides a Three-Phase Assessment (Initial Screening, Detailed Assessment, Final Evaluation), Multi-Factor Risk Scoring across 6 dimensions with critical-service weighting, regulatory compliance checklists for 8 frameworks, vendor comparison matrices, and ongoing monitoring with Early Warning Indicators. Designed for procurement teams, legal counsel, IT security, and compliance officers evaluating technology vendors.
Before scoring the vendor, confirm these inputs. If any is unknown or vague, ASK — do not assume:
--critical flag applies a 2x weight to security and compliance, which can flip the composite score and the Approve/Reject recommendationStop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the assessment.
scripts/vendor_risk_scorer.py)Scores a vendor across 6 risk dimensions based on questionnaire responses. Calculates weighted composite score with 2x multiplier for critical services. Generates risk heat map and overall recommendation.
# Score a vendor from questionnaire responses
python scripts/vendor_risk_scorer.py vendor_responses.json
# JSON output for dashboards
python scripts/vendor_risk_scorer.py vendor_responses.json --json
# Flag as critical service (2x weight on security + compliance)
python scripts/vendor_risk_scorer.py vendor_responses.json --criticalscripts/vendor_comparison.py)Takes multiple vendor risk assessment JSONs and generates a side-by-side comparison matrix. Ranks vendors by composite score and recommends preferred vendor with rationale.
# Compare two vendors
python scripts/vendor_comparison.py vendor_a.json vendor_b.json
# Compare multiple vendors with JSON output
python scripts/vendor_comparison.py vendor_a.json vendor_b.json vendor_c.json --json
# Compare with critical service weighting
python scripts/vendor_comparison.py vendor_a.json vendor_b.json --critical| Reference | Purpose |
|---|---|
references/risk_assessment_framework.md | 6-dimension scoring system, weighting methodology, composite score interpretation |
references/regulatory_checklists.md | Pre-built compliance checklists for GDPR, DORA, NIS2, SOX, PCI DSS, ISO 27001/SOC 2, HIPAA, FedRAMP |
references/monitoring_framework.md | Quarterly reviews, Early Warning Indicators, KPI metrics, risk mitigation strategies, onboarding checklists |
Phase 1: Initial Screening (Days 1-5)
vendor_risk_scorer.py with preliminary data for initial risk classificationregulatory_checklists.mdPhase 2: Detailed Assessment (Days 5-15)
vendor_risk_scorer.py with complete questionnaire responsesPhase 3: Final Evaluation (Days 15-20)
vendor_comparison.py if evaluating multiple vendorsrisk_assessment_framework.mdmonitoring_framework.mdvendor_comparison.py on finalist assessmentstech-contract-negotiation skill)monitoring_framework.mdmonitoring_framework.md; escalate per defined paths| Problem | Cause | Solution |
|---|---|---|
| All dimensions score 1 (Low Risk) | Vendor self-reported optimistically on questionnaire | Cross-reference with SOC 2 reports, pen test results, and financial filings; adjust scores based on evidence |
| Composite score doesn't reflect known security issues | Security dimension not weighted for critical service | Re-run with --critical flag to apply 2x multiplier on security and compliance dimensions |
| Comparison matrix shows all vendors tied | Scoring inputs are too similar or too coarse | Request more granular data; use the 5-level scoring criteria from the risk framework to differentiate |
| Regulatory checklist seems incomplete for your industry | Only 8 frameworks are pre-built | Customize checklists by adding industry-specific requirements as additional items |
| Vendor refuses to complete questionnaire | Vendor sees assessment as overly burdensome | Share only the dimensions relevant to their service scope; offer to accept SOC 2/ISO 27001 reports as partial substitutes |
| Risk score changed dramatically between quarters | Major event occurred (breach, M&A, leadership change) | This is expected behavior; document the trigger event and follow the event-triggered review process |
This skill covers:
This skill does NOT cover:
finance/financial-analyst skill)legal/tech-contract-negotiation skill)| Anti-Pattern | Why It Fails | Better Approach |
|---|---|---|
| Relying solely on vendor self-assessment questionnaires | Vendors underreport risks; no independent verification | Cross-reference questionnaire responses with SOC 2/ISO 27001 reports, pen test results, and public records |
| Applying the same weight to all dimensions regardless of service type | A payroll vendor and a marketing tool have different risk profiles | Use --critical flag for critical services; adjust dimension weights based on service classification |
| Completing due diligence once and never revisiting | Vendor risk changes over time due to M&A, breaches, market shifts | Implement quarterly monitoring with annual re-assessment per the monitoring framework |
| Rejecting vendors for a single high-risk dimension without considering mitigations | Eliminates potentially strong vendors with addressable gaps | Use the gap analysis severity classification; require remediation plans for major concerns before final decision |
| Skipping the comparison matrix for sole-source procurements | Misses opportunity to benchmark the vendor against market standards | Run comparison against industry benchmarks or previous vendor assessments to establish a risk baseline |
scripts/vendor_risk_scorer.pyScore a vendor across 6 risk dimensions and generate an overall recommendation.
usage: vendor_risk_scorer.py [-h] [--json] [--critical]
input_file
positional arguments:
input_file Path to JSON file with vendor questionnaire responses
options:
-h, --help Show help message and exit
--json Output results as JSON
--critical Apply 2x weight to security and compliance
dimensions (for critical/essential services)Outputs: 6-dimension risk scores (1-5 each), weighted composite score, risk level classification (Low/Moderate/High/Critical), overall recommendation (Approve/Approve with Conditions/Reject), dimension-level findings, and gap analysis.
scripts/vendor_comparison.pyCompare multiple vendors side-by-side and recommend preferred vendor.
usage: vendor_comparison.py [-h] [--json] [--critical]
input_files [input_files ...]
positional arguments:
input_files Paths to vendor assessment JSON files (minimum 2)
options:
-h, --help Show help message and exit
--json Output results as JSON
--critical Apply 2x weight to security and compliance
dimensions (for critical/essential services)Outputs: Side-by-side comparison matrix, composite score ranking, per-dimension strength/weakness analysis, preferred vendor recommendation with rationale, and risk delta highlights.
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 5 other files (scripts, references) in legal/vendor-due-diligence of borghei/Claude-Skills.
Open the folder on GitHubat commit 4a698e8
Vendor Due Diligence next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vendor Due Diligence this skillborghei/Claude-Skills | 891 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Gc Reviewalirezarezvani/claude-skills | 28k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Sec Analyst MasterOctagonAI/skills | 127 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Contract Legal Researchinfometa/workbuddyskills | 348 | — | ~2.1k | Automated safety check: Pass | None | |
| Officecli Word FormFerroxLabs/wayland | 608 | 3 repos | ~14k | Automated safety check: Pass | AGPL-3.0 | |
| Meeting Briefing Anthropiclawve-ai/awesome-legal-skills | 847 | 1 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 |
alirezarezvani/claude-skills
/cs:gc-review <plan — General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface.
OctagonAI/skills
Comprehensive SEC filing analyst skill that orchestrates all Octagon SEC analysis skills.
infometa/workbuddyskills
Retrieve the legal basis and due-diligence facts that contract work depends on — supporting statutes and their effectiveness status, regulatory requirements, mandatory provisions for the contract…
FerroxLabs/wayland
A skill your agent uses to create fillable Word forms (.docx) with real Content Controls (SDT) + legacy FormField checkboxes + MERGEFIELD mail-merge placeholders + document protection.
lawve-ai/awesome-legal-skills
Prepare structured briefings for meetings with legal relevance and track resulting action items.
JoelLewis/finance_skills
Guide BSA/AML compliance program design, ongoing transaction monitoring, and FinCEN reporting for broker-dealers, banks, and investment advisers.
borghei/Claude-Skills
Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets.
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Categories
Assess IT vendors and third-party partners with multi-factor risk scoring and regulatory compliance checklists. Vendor Due Diligence is an agent skill from borghei/Claude-Skills. Assess IT vendors and third-party partners with multi-factor risk scoring and regulatory compliance checklists.
Vendor Due Diligence fits situations like: evaluating technology vendors; tasks that involve Fundraising and pitch decks; tasks that involve Regulatory compliance.
Run `npx skills add borghei/Claude-Skills --skill vendor-due-diligence -a claude-code`. Or copy the skill folder (legal/vendor-due-diligence in borghei/Claude-Skills) into .claude/skills/vendor-due-diligence in your project. Claude Code loads it when a task matches its description.
Run `npx skills add borghei/Claude-Skills --skill vendor-due-diligence -a codex`. Or copy the skill folder (legal/vendor-due-diligence in borghei/Claude-Skills) into .agents/skills/vendor-due-diligence in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill vendor-due-diligence -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vendor-due-diligence, .gemini/skills/vendor-due-diligence, .github/skills/vendor-due-diligence and .opencode/skills/vendor-due-diligence in your project.
Going by SKILL.md and its folder, Vendor Due Diligence needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Vendor Due Diligence is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 12k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Vendor Due Diligence: Gc Review (alirezarezvani/claude-skills, 28k stars), Sec Analyst Master (OctagonAI/skills, 127 stars), Contract Legal Research (infometa/workbuddyskills, 348 stars) and Officecli Word Form (FerroxLabs/wayland, 608 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 891 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.