CtrlK
BlogDocsLog inGet started
Tessl Logo

github

Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.

68

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

A concise, highly actionable command reference that respects Claude's competence, though it stops short of sequencing multi-step CI triage workflows with validation checkpoints.

Suggestions

Add a short ordered workflow for diagnosing a failed CI run (e.g. list runs -> view failed run -> read --log-failed -> fix -> re-run), with a re-check step as a validation checkpoint.

Note the `--repo owner/repo` requirement once up front rather than repeating it in every example, to tighten the token budget further.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — every line is a concrete command or a one-line orientation note, with no padding or explanation of concepts Claude already knows.

3 / 3

Actionability

Provides fully executable `gh` commands with concrete flags (`--repo owner/repo`, `--log-failed`, `--jq`, `--json`) that are copy-paste ready.

3 / 3

Workflow Clarity

Commands are grouped by topic but there is no sequenced multi-step workflow or validation checkpoints; for operations like CI checks there is no feedback loop (e.g. re-check after a fix), capping clarity at 2.

2 / 3

Progressive Disclosure

A short (~40 line), single-purpose reference with clear section headers and no need for external bundle files, matching the simple-skills allowance for a top score.

3 / 3

Total

11

/

12

Passed

Description

82%

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 specific, well-scoped description with strong trigger terms and clear distinctiveness, but it omits an explicit 'Use when...' clause, capping completeness at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to interact with GitHub — issues, pull requests, CI runs, or advanced API queries.'

Consider listing a few more natural variations users might say (e.g. 'GitHub Actions', 'workflows', 'check PR status') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the tool (`gh` CLI) and four specific subcommands (`gh issue`, `gh pr`, `gh run`, `gh api`) mapped to concrete purposes (issues, PRs, CI runs, advanced queries), listing multiple concrete actions.

3 / 3

Completeness

Strongly answers 'what' but lacks any 'Use when...' clause or equivalent explicit trigger guidance, so completeness caps at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Includes natural terms users would say — `gh issue`, `gh pr`, `gh run`, `gh api`, issues, PRs, CI runs — giving good coverage of likely trigger phrases.

3 / 3

Distinctiveness Conflict Risk

The narrow `gh` CLI niche with distinct subcommand triggers makes it clearly distinguishable and unlikely to fire for the wrong skill.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
volcengine/OpenViking
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.