Explore a Repository
Use this skill when an agent needs a reliable, structured picture of a GitHub
repository.
Workflow
1. Repository identity
- Fetch repo metadata: description, default branch, language, license,
stars/forks (public), last push, archived status.
- Note the default branch name and whether the repo looks maintained.
2. Structure and content
- List the top-level tree: entry points (README, docs, packages), build config,
CI workflows.
- Identify the language stack and package manager from manifests
(package.json, Cargo.toml, pyproject.toml, go.mod, …).
- Read the README for the stated purpose; compare it with what the tree
actually suggests.
3. Health signals
- Open issues vs closed, and the stale/unaddressed ratio.
- Recent activity: commit cadence on the default branch (last few weeks).
- CI: are workflows present, and do recent runs pass?
- Dependencies: any obviously outdated or pinned-forever manifests, vendored
code, or license gaps.
- Governance: CONTRIBUTING, CODE_OF_CONDUCT, SECURITY policy present?
4. Contribution state
- For contribution questions: open PRs, their age, and whether the
contribution workflow (tests, lint, CLA) is documented.
- For adoption questions: license, release cadence (tags/releases), and
maintenance signals.
5. Report
Give a compact review: purpose, stack, structure overview, health bullet list
with evidence (issue counts, activity window, CI state), and any red flags.
Keep it read-only — do not open issues, create branches, or star/fork anything
unless explicitly asked.
1---2name: explore-repository3description: Produce a structured read-only review of a GitHub repository: purpose, structure, health signals, dependencies, and contribution state. Use when onboarding to an unfamiliar repository, evaluating a repo for adoption, or preparing a summary.4---56# Explore a Repository78Use this skill when an agent needs a reliable, structured picture of a GitHub9repository.1011## Workflow1213### 1. Repository identity1415- Fetch repo metadata: description, default branch, language, license,16 stars/forks (public), last push, archived status.17- Note the default branch name and whether the repo looks maintained.1819### 2. Structure and content2021- List the top-level tree: entry points (README, docs, packages), build config,22 CI workflows.23- Identify the language stack and package manager from manifests24 (package.json, Cargo.toml, pyproject.toml, go.mod, …).25- Read the README for the stated purpose; compare it with what the tree26 actually suggests.2728### 3. Health signals2930- Open issues vs closed, and the stale/unaddressed ratio.31- Recent activity: commit cadence on the default branch (last few weeks).32- CI: are workflows present, and do recent runs pass?33- Dependencies: any obviously outdated or pinned-forever manifests, vendored34 code, or license gaps.35- Governance: CONTRIBUTING, CODE_OF_CONDUCT, SECURITY policy present?3637### 4. Contribution state3839- For contribution questions: open PRs, their age, and whether the40 contribution workflow (tests, lint, CLA) is documented.41- For adoption questions: license, release cadence (tags/releases), and42 maintenance signals.4344### 5. Report4546Give a compact review: purpose, stack, structure overview, health bullet list47with evidence (issue counts, activity window, CI state), and any red flags.48Keep it read-only — do not open issues, create branches, or star/fork anything49unless explicitly asked.50
HiAi-gg