CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

private-github-search

Full-text search across all of the user's GitHub repos (including private ones) using a local mirror and ripgrep. Use for "where did I put X", "which repo has X", or any search spanning the user's repos - gh search code / the REST API cannot reliably search private repos.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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 tight, actionable skill body: the one non-obvious fact is stated up front, commands are nearly all executable, and edge cases (first-time setup, history/branch caveats, private-data warning) are covered concisely. The only weaknesses are the placeholder in the sync command and the missing wait-for-initial-sync checkpoint.

Suggestions

Make the sync step fully executable, e.g. `bash "$(find ~/.claude ~/.codex -name private-github-search-sync.sh 2>/dev/null | sort -V | tail -1)"`, so no manual substitution is needed.

In First-time setup, state that the initial search must wait until the background sync finishes (e.g. check for completion or poll owners count) so the mirror isn't searched while partially cloned.

Note what the mirror contains (code and files on the default branch) so searches over issues or non-code content are correctly redirected.

DimensionReasoningScore

Conciseness

About 30 lean lines where every token earns its place; the single explanatory sentence (why gh search code fails on private repos) is non-obvious justification rather than padding, and no concepts Claude already knows are re-explained.

5 / 5

Actionability

The find command and both rg invocations are copy-paste ready, but `bash <script-path>` requires manual substitution — a minor gap versus the fully-executable anchor 5, though the preceding find step does locate the path.

4 / 5

Workflow Clarity

Clear sequence (locate script, refresh, search) with a cold-start check (owners.txt existence) and documented sync idempotence, but it never says to wait for the background initial clone before searching — a minor checkpoint gap versus anchor 5.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references, and content is well-organized into Searching, First-time setup, and Caveats sections, which per the rubric's simple-skill guideline merits a 5.

5 / 5

Total

18

/

20

Passed

Description

95%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.

A strong description: concrete mechanism, explicit trigger phrases a user would naturally say, and deliberate differentiation from gh/REST alternatives. Third-person voice is used throughout. Only minor gap is that the searchable content types are implied rather than stated.

DimensionReasoningScore

Specificity

"Full-text search across all of the user's GitHub repos (including private ones) using a local mirror and ripgrep" names the action, mechanism, and scope concretely, but stops short of anchor 5 because it doesn't enumerate what content is searched (code, files, issues).

4 / 5

Completeness

Explicitly answers both: a clear "what" (full-text search via local mirror + ripgrep) and an explicit "Use for..." clause with concrete trigger phrases, exactly matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

"where did I put X", "which repo has X", "any search spanning the user's repos" are natural phrases users would actually say, with synonym coverage matching the comprehensive anchor.

5 / 5

Distinctiveness Conflict Risk

The explicit contrast "gh search code / the REST API cannot reliably search private repos" carves out a clear niche with distinct triggers and minimal conflict risk with general search or GitHub skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ykdojo/claude-code-tips

Path

skills/private-github-search/SKILL.md

Reviewed

Table of Contents

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.