probe-droid

Name: probe-droid
Availability: InStock
Author: Endor Labs

Compare GitHub repository inventory with Endor project details to identify monitored-branch coverage gaps.

10|2|Updated May 4, 2026

Search Tags:#GitHub #Endor Labs #repository onboarding #coverage assessment #setup actions

Ready to run

npx skills add https://github.com/endorlabs/endor-labs-agent-kit --skill probe-droid

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: probe-droid
Source: https://github.com/endorlabs/endor-labs-agent-kit/tree/main/gemini/probe-droid
Command: npx skills add https://github.com/endorlabs/endor-labs-agent-kit --skill probe-droid

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies the gaps in GitHub repository onboarding for Endor Labs monitored-branch coverage, providing setup actions without modifying source, GitHub, or Endor state.

Core Features & Use Cases

GitHub Onboarding Gap Assessment: Compares GitHub repository inventory with Endor project, GitHub App, package, scan, scan profile, package manager integration, and reachability evidence.
Human-readable Setup Actions: Returns setup actions required for optimal onboarding without source or GitHub mutation.
Use Case: When you need to evaluate the readiness of GitHub repositories for Endor Labs monitoring and ensure the necessary setup actions are in place.

Quick Start

Use @probe-droid to probe GitHub org <org> for Endor monitored-branch onboarding gaps and setup prescriptions.

Frequently Asked Questions about probe-droid

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

FAQPage Schema

How do I assess GitHub repository onboarding gaps for Endor Labs monitored-branch coverage?▼

To assess GitHub repository onboarding gaps for Endor Labs monitored-branch coverage, compare your GitHub repository inventory against Endor project details, GitHub App coverage, package evidence, and scan setup evidence to identify missing configurations.

What is Endor Labs monitored-branch coverage and when do I need to evaluate it?▼

Endor Labs monitored-branch coverage is the tracking of repository branches for security and dependency analysis. You need to evaluate it when onboarding GitHub repositories to ensure package manager integration, scan profiles, and reachability evidence are properly configured.

Do I need GitHub and Endor API access to check repository onboarding readiness?▼

Yes, you need both GitHub and Endor API access to check repository onboarding readiness. This access allows the assessment tool to retrieve GitHub inventory and Endor project details to compare package, scan, and reachability evidence.

Can I identify missing GitHub App coverage and package manager evidence without modifying source code?▼

Yes, you can identify missing GitHub App coverage and package manager evidence without modifying source code. The assessment returns human-readable setup actions required for optimal onboarding without mutating source, GitHub, or Endor state.

What's the best way to find setup actions for Endor Labs scan profiles on GitHub repositories?▼

The best way to find setup actions for Endor Labs scan profiles is to probe your GitHub organization for onboarding gaps. This comparison returns specific setup prescriptions for scan profiles, package managers, and reachability evidence.

Why does my Endor Labs coverage assessment show missing reachability evidence for some GitHub projects?▼

Your Endor Labs coverage assessment shows missing reachability evidence when GitHub repositories lack the necessary scan setup configurations. Comparing GitHub inventory with Endor project details identifies these gaps and returns the required setup actions.