CtrlK
BlogDocsLog inGet started
Tessl Logo

github-ops

Provides comprehensive GitHub operations using gh CLI and GitHub API. Activates when working with pull requests, issues, repositories, workflows, or GitHub API operations including creating/viewing/merging PRs, managing issues, querying API endpoints, and handling GitHub workflows in enterprise or public GitHub environments.

89

1.11x
Quality

Does it follow best practices?

Impact

95%

1.11x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is a well-structured, highly actionable GitHub operations reference with excellent progressive disclosure. Its main weaknesses are redundancy between the Core Operations and Quick Reference sections and the absence of validation/verification checkpoints for destructive and batch operations.

Suggestions

Remove or trim the 'Quick Reference' section, since its commands already appear verbatim in the Core Operations sections, to reduce redundancy.

Add explicit verification steps before destructive operations, e.g. 'gh pr checks 123' before 'gh pr merge', and confirm state with 'gh pr view' / 'gh issue view' after closing.

Shorten the 'Resources' section to one-line pointers (what + when to load) instead of full bullet summaries that duplicate the reference files' own contents.

DimensionReasoningScore

Conciseness

Content is mostly lean executable commands with no explanatory fluff, but the 'Quick Reference' repeats commands already shown and the 'Resources' section re-summarizes each reference file, which could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready gh commands with concrete flags throughout every operation section.

3 / 3

Workflow Clarity

Operations are organized by category but destructive/batch actions (merge, close) lack validation or verification checkpoints, capping workflow clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

Body is a clear overview with five well-signaled one-level-deep references that all exist as real files, each accompanied by 'Load this reference when...' guidance and no nested references.

3 / 3

Total

10

/

12

Passed

Description

100%

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 concise, uses correct third-person voice, and explicitly covers both capabilities and activation triggers with natural keyword coverage. The only minor weakness is the slightly fluffy word 'comprehensive', but it does not undermine the concrete, well-triggered framing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions such as 'creating/viewing/merging PRs, managing issues, querying API endpoints', matching the anchor for specific concrete actions rather than the level-2 partial coverage.

3 / 3

Completeness

Explicitly answers both what ('Provides comprehensive GitHub operations using gh CLI and GitHub API') and when ('Activates when working with pull requests, issues...'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes natural terms users would say ('pull requests, issues, repositories, workflows') in an 'Activates when working with...' clause, giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

GitHub operations via gh CLI/API is a clear niche with distinct triggers (PRs, issues, workflows, gh API) unlikely to conflict with unrelated skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
daymade/claude-code-skills
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.