cli-detector

Detect external SaaS services in code repositories and verify CLI availability.

13|1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/danchamorro/pi-agent-toolkit --skill cli-detector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-detector
Source: https://github.com/danchamorro/pi-agent-toolkit/tree/main/dotfiles/global-skills/cli-detector
Command: npx skills add https://github.com/danchamorro/pi-agent-toolkit --skill cli-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discovering which external SaaS platforms a codebase depends on and whether those platforms provide official CLI tools is time-consuming and error-prone when done manually; this Skill automates detection, verification, and reporting so developers can quickly understand external surface area and automation options.

Core Features & Use Cases

  • Multi-vector detection: Scans package manifests, environment variable patterns, configuration files, source imports, implicit signals, and CI/CD pipelines to find external services.
  • Authoritative CLI verification: Uses Exa queries to confirm whether each detected service offers an official CLI, capturing install commands and documentation links.
  • Actionable reporting: Produces a clear table of services with usage context and CLI status, plus an exclusions table for noise such as generic DB clients.
  • Use case: Auditing a repository before automating deployments to know which vendor CLIs to install and script against.

Quick Start

Run the CLI Detector on the repository and return a table listing each detected external service, how it was found, and the verified official CLI installation instructions.

Frequently Asked Questions about cli-detector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect external SaaS services and integrations in a code repository?

To detect external SaaS services in a repository, scan package manifests, environment variables, config files, source imports, and CI/CD pipelines to identify SDKs and integration references. This multi-vector scanning reveals the external platforms your codebase depends on.

How can I check if external services detected in my codebase have official CLI tools?

You can verify CLI availability for detected services by running Exa queries against each external platform found in the repository. This queries the web to confirm whether an official CLI exists and collects the installation commands and documentation links.

Does dependency scanning work with Node, Python, Go, Ruby, Rust, and Java projects?

Yes, dependency scanning works with Node, Python, Go, Ruby, Rust, and Java projects, as well as CI manifests. It locates SDKs, environment variables, config files, imports, and pipeline references across these languages to find external integrations.

What is the best way to audit a repository for vendor CLIs before automating deployments?

The best way to audit a repository for vendor CLIs is to run an automated detector that maps discovered services to their official CLI tools. It produces a table listing each integration, how it was found, and the verified CLI installation instructions.

How do I filter out noise like generic database clients when scanning for external services?

To filter out noise like generic database clients when scanning for external services, generate an exclusions table alongside the main service report. This separates generic clients from authoritative SaaS integrations, leaving a clean list of verified vendor CLIs.