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.

87

1.11x
Quality

82%

Does it follow best practices?

Impact

95%

1.11x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

64%

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

This is a solid reference-style skill with excellent actionability—every section provides real, executable commands. Its main weaknesses are moderate verbosity (duplicate reference descriptions, redundant Quick Reference section, unnecessary 'When to Use' section) and lack of multi-step workflow sequences with validation checkpoints. The progressive disclosure structure is reasonable but cannot be fully validated without bundle files.

Suggestions

Remove the 'When to Use This Skill' section (this duplicates frontmatter/description metadata) and the redundant 'Resources' section at the bottom (references are already linked inline with 📚 markers).

Add at least one end-to-end workflow with validation steps, e.g., 'Create PR → verify creation → wait for checks → merge' with explicit checkpoint commands like `gh pr checks 123 --watch`.

Consolidate the 'Quick Reference' section—it largely duplicates commands already shown in the Core Operations sections above it.

DimensionReasoningScore

Conciseness

The skill includes some unnecessary sections like 'When to Use This Skill' (which repeats the description) and the 'Resources' section that re-describes what each reference file contains after already linking to them inline. The 'Quick Reference' section also largely duplicates commands already shown above. However, the core content is reasonably efficient with executable examples.

2 / 3

Actionability

The skill provides fully executable, copy-paste ready bash commands throughout. Every operation has concrete examples with real flags and arguments. The PR title convention, authentication commands, and output format examples are all specific and immediately usable.

3 / 3

Workflow Clarity

While individual commands are clear, there are no multi-step workflows with validation checkpoints. For example, the PR creation flow doesn't include verifying the PR was created, checking CI status, then merging. Operations are presented as isolated commands rather than sequenced workflows with feedback loops. For bulk operations (mentioned in references), no validation steps are shown.

2 / 3

Progressive Disclosure

The skill references five separate reference files with clear descriptions and loading guidance, which is good structure. However, no bundle files were provided, so the references cannot be verified. Additionally, the 'Resources' section at the bottom redundantly re-describes each reference file after they were already linked inline with 📚 markers, and the main file itself is somewhat long with content that could be pushed to references (e.g., the full Quick Reference table).

2 / 3

Total

9

/

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.

This is a strong skill description that clearly communicates both what the skill does and when it should be activated. It provides specific concrete actions, uses natural trigger terms that users would employ, and is distinctly scoped to GitHub operations. The description is well-structured with an 'Activates when' clause that serves as explicit trigger guidance.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: creating/viewing/merging PRs, managing issues, querying API endpoints, handling GitHub workflows. Also mentions the tools used (gh CLI and GitHub API).

3 / 3

Completeness

Clearly answers both what ('comprehensive GitHub operations using gh CLI and GitHub API' with specific actions listed) and when ('Activates when working with pull requests, issues, repositories, workflows, or GitHub API operations'), providing explicit trigger guidance.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'pull requests', 'PRs', 'issues', 'repositories', 'workflows', 'GitHub API', 'gh CLI', 'merging PRs', 'enterprise', 'public GitHub'. These are terms users would naturally use when needing GitHub operations.

3 / 3

Distinctiveness Conflict Risk

Clearly scoped to GitHub-specific operations with distinct triggers like 'gh CLI', 'GitHub API', 'PRs', 'GitHub workflows'. The mention of both enterprise and public GitHub environments further narrows the niche. Unlikely to conflict with generic code or git 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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
fernandezbaptiste/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.