orbit-local

Index and query a LOCAL checkout of a repository offline with the Orbit local CLI (the `orbit` binary, run directly or via `glab orbit local`). It builds a DuckDB property graph from the working tree and you query it with read-only SQL. Use when the request targets the current checkout, working tree, or a branch that is not pushed/indexed remotely, or is explicitly offline/local: index this repo locally, who calls X in my checkout, list definitions in a file, generate a repo map of a local checkout, run SQL over the local code graph, or serve the local graph over MCP. For queries against already-indexed production data in GitLab (a project such as gitlab-org/gitlab, cross-project blast radius, contributor or merge-request aggregation) use the `orbit` skill; for single-entity GitLab lookups or write operations use `glab`.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable skill body that splits detail into three real reference files and leads with gotchas that prevent the most common mistakes. Minor conciseness trimming and an explicit validation step in the quick start would push it to the top band.

Suggestions

Trim the Orbit-Remote comparison in the intro and the restated description phrasing to tighten conciseness.

Add an explicit validation checkpoint to the quick start (e.g. "run `orbit list` / check `--stats` output to confirm the index succeeded before querying").

Consider moving the dense gl_edge/per-commit gotcha detail into references/sql.md, keeping only the highest-impact gotchas inline.

Dimension	Reasoning	Score
Conciseness	Mostly lean — command-surface table, code blocks, and gotchas each earn their place — with minor over-explanation such as the Orbit-Remote comparison and restated intro phrasing that could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready commands covering common cases: `orbit index .`, `orbit schema gl_definition gl_edge`, `orbit sql "SELECT …"`, `orbit repo-map overview`, plus concrete table/column names.	5 / 5
Workflow Clarity	A clear quick-start sequence (index → schema → sql) with verification guidance in the gotchas (check printed graph stats, run `orbit schema` to confirm columns, re-run `index` after a checkout change), though the main workflow lacks an explicit single validation checkpoint.	4 / 5
Progressive Disclosure	Clear overview with well-signaled, one-level-deep references to three real bundle files (cli.md, sql.md, repo_map.md) and a consolidated References table; content is appropriately split and easy to navigate.	5 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: third-person voice, concrete capabilities, natural trigger phrases, and explicit disambiguation from sibling skills. It answers what, when, and which-skill-not without padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Index and query a LOCAL checkout", "builds a DuckDB property graph", "query it with read-only SQL", "serve the local graph over MCP" — with comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both what (index/query a local checkout into a DuckDB property graph via read-only SQL) and when, with a concrete "Use when…" clause listing offline/local trigger conditions.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases users would actually say: "index this repo locally", "who calls X in my checkout", "list definitions in a file", "generate a repo map of a local checkout", "run SQL over the local code graph".	5 / 5
Distinctiveness Conflict Risk	Clear niche (local offline checkout) with explicit boundary guidance distinguishing it from the `orbit` skill (remote production data) and `glab` (single-entity lookups/writes), minimizing conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: gitlabhq/orbit-knowledge-graph
Path: skills/orbit-local/SKILL.md
Commit: 0fe19ac

Reviewed: 14 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.