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.

64

Quality

78%

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 ./bot/workspace/skills/github/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is an excellent, lean reference of executable `gh` commands with clear section organization and no over-explanation. The only gap is the absence of validation/checkpoint guidance for verifying command outputs.

Suggestions

Add brief verification guidance for actions whose output drives follow-up steps, e.g. checking `gh pr checks` exit status or confirming a run is complete before acting on its results.

DimensionReasoningScore

Conciseness

The body is lean and efficient, jumping straight into executable `gh` commands without explaining what GitHub is or how the CLI works; every token earns its place.

5 / 5

Actionability

Provides copy-paste-ready, fully executable `gh` commands covering common cases (PR checks, run listing/viewing, failed logs, API fields, JSON+jq filtering).

5 / 5

Workflow Clarity

Commands are clearly grouped by task and each snippet has an explicit purpose, but there is no validation/checkpoint guidance for verifying command results before acting on them.

4 / 5

Progressive Disclosure

As a short single-purpose skill with no bundle files, the body is well-organized into clear sections (Pull Requests, API, JSON Output) matching the simple-skill exception for a 5.

5 / 5

Total

19

/

20

Passed

Description

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

The description is specific and well-scoped to the `gh` CLI with concrete subcommands, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness score. It is otherwise strong on specificity and distinctiveness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks about GitHub issues, PRs, CI runs, or needs to query the GitHub API.'

Include common synonyms and file/task triggers such as 'pull requests', 'GitHub Actions', and 'workflows' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the `gh` CLI and several concrete subcommands (`gh issue`, `gh pr`, `gh run`, `gh api`) tied to issues, PRs, CI runs, and advanced queries, with only minor coverage gaps.

4 / 5

Completeness

The 'what' is clearly stated (interact with GitHub via gh subcommands) but there is no explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes natural terms like 'issues', 'PRs', 'CI runs', and 'advanced queries' that users would say, though it omits common synonyms such as 'pull request', 'workflows', or 'GitHub Actions'.

4 / 5

Distinctiveness Conflict Risk

Scoped specifically to the `gh` CLI for GitHub with distinct subcommand triggers, giving it a clear niche and minimal conflict risk with other skills.

5 / 5

Total

16

/

20

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.