CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

show-github-search-result

Summarizes the results of a GitHub search query in a human friendly markdown table that is easy to read and understand. ALWAYS use this skill when displaying the results of a GitHub search query.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./src/lm/skills/show-github-search-result/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 compact, well-structured single-purpose skill with genuinely actionable rendering rules and no bundle bloat. Its main weakness is redundancy between the Purpose and Usage sections, plus a missing example of the final table that would make the guidance fully copy-paste ready.

Suggestions

Merge the Purpose and Usage sections into one short statement — they restate the same idea twice.

Add a small example of a rendered markdown table for a typical search result to make the guidance fully concrete.

Replace the vague 'any other relevant details' with a specific list of candidate fields (title, author, labels, state, updated date) or an explicit rule for choosing them.

DimensionReasoningScore

Conciseness

The Purpose and Usage sections largely repeat each other ('easy to read and understand', restating that the skill builds a markdown table), and phrases like 'without having to parse through raw data' pad what Claude can infer. Mostly efficient but could be tightened by merging the two sections.

3 / 5

Actionability

Concrete, executable rules are given: the exact link format '[#123](https://github.com/owner/repo/issues/123)', dropping columns implied by the query, and 'is:pr' mapping to review/merge status. Minor gaps keep it below 5: 'any other relevant details' is loose and no example table is shown.

4 / 5

Workflow Clarity

The single task is unambiguous and the column-selection rules form a clear decision procedure, with no risky operations requiring validation. Minor gaps (no rendered example, no guidance for edge cases like empty results or very long lists) hold it below 5.

4 / 5

Progressive Disclosure

The body is under 50 lines, uses clean section headers (Purpose, Usage, How to Render), and needs no external references — none exist in the bundle — satisfying the simple-skill criterion for full marks.

5 / 5

Total

16

/

20

Passed

Description

66%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 clear, third-person description with an explicit trigger clause and a well-defined niche. Its main weaknesses are a single concrete action and a thin set of trigger terms that repeat one phrase instead of covering natural variations like issues, pull requests, or gh search.

Suggestions

Add a few concrete actions or details (e.g., which fields are extracted: title, author, state, labels) to raise specificity beyond a single summarize-into-table action.

Broaden trigger terms to include natural variations such as 'GitHub search results', 'issues or pull requests from a search', and 'gh search' output.

State the when-clause with distinct trigger scenarios rather than repeating the same 'GitHub search query' phrase used for the what.

DimensionReasoningScore

Specificity

The description names the domain ("GitHub search query") and one concrete action ("Summarizes... in a human friendly markdown table"), but stops short of listing several specific actions, matching the 1-2-concrete-actions anchor rather than the broader coverage of level 4.

3 / 5

Completeness

Both what ("Summarizes the results of a GitHub search query in a human friendly markdown table") and an explicit when ("ALWAYS use this skill when displaying the results of a GitHub search query") are present. It is not a 5 because the trigger clause is narrow and circular, reusing the same single phrase instead of multiple concrete trigger variations.

4 / 5

Trigger Term Quality

"GitHub search query" and "displaying the results of a GitHub search query" are relevant natural terms, but common variations users would actually say — "issues", "pull requests", "gh search", "search results" as standalone triggers — are missing, matching the some-keywords-but-missing-synonyms anchor.

3 / 5

Distinctiveness Conflict Risk

Rendering GitHub search results as a markdown table is a clear niche with a distinct, unambiguous trigger; there is minimal risk of it firing for unrelated skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

microsoft/vscode-pull-request-github

Path

src/lm/skills/show-github-search-result/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.