inspectlisted

# Inspect — pre-install structured summary of a remote repo Produce a structured capability summary of a remote GitHub repo that hosts skills, agents, or plugins — before committing to the full `/ievo:init` pipeline. Answers "what does this repo contain?" typically in under a minute with zero side effects. ## When to use - User is evaluating a plugin/skill repo and wants a quick overview before running `/ievo:init` - User received a recommendation and wants to understand the permission footprint before granting security scan time - Onboarding a collaborator to an already-installed plugin — they need to understand what it does - User explicitly invokes `/ievo:inspect <owner>/<repo>` - User asks "what does `owner/repo` contain?", "inspect this skill before install", "show me what's in `owner/repo`" ## Inputs - **Required:** `<owner>/<repo>` — a GitHub repository identifier (e.g. `ievo-ai/skills`, `anthropics/claude-skills`, `wshobson/agents`) - **Optional:** `<ref>` — a branch, tag, or commit SHA. Defaults to `HEAD` (the repo's default branch) Parse the input from the user's message. Accept forms like: - `/ievo:inspect owner/repo` - `/ievo:inspect owner/repo@ref` - `inspect owner/repo` - `what does owner/repo contain?` ## Step 1: Resolve the repo and default ref Verify the repo exists and resolve the default branch if no ref was provided: ```bash gh api "repos/<owner>/<repo>" --jq '.default_branch' ``` If the API call fails, report clearly based on the error: - **404