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.
Install with Tessl CLI
npx tessl i github:fernandezbaptiste/claude-code-skills --skill github-ops89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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 capabilities and activation triggers. It uses third person voice correctly, lists specific actions, includes natural trigger terms users would say, and has an explicit 'Activates when' clause. The description effectively distinguishes itself from generic git or code skills by focusing on GitHub-specific operations.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'creating/viewing/merging PRs, managing issues, querying API endpoints, and handling GitHub workflows'. Also specifies tools used (gh CLI and GitHub API) and environments (enterprise or public). | 3 / 3 |
Completeness | Clearly answers both what ('comprehensive GitHub operations using gh CLI and GitHub API') and when ('Activates when working with pull requests, issues, repositories, workflows, or GitHub API operations'). The 'Activates when' clause serves as explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'pull requests', 'PRs', 'issues', 'repositories', 'workflows', 'GitHub API', 'merging PRs'. These are terms users naturally use when working with GitHub. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on GitHub operations with distinct triggers (gh CLI, GitHub API, PRs, GitHub workflows). Unlikely to conflict with generic code or git skills due to explicit GitHub-specific terminology. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent actionability and progressive disclosure. The code examples are concrete and executable, and the reference structure is clear. However, it could be more concise by removing redundant sections, and workflow clarity would benefit from explicit validation steps and error handling patterns for multi-step operations.
Suggestions
Remove the 'When to Use This Skill' section as it duplicates the skill description and wastes tokens
Consolidate the 'Resources' section at the end - the inline 📚 references are sufficient and the detailed descriptions are redundant
Add validation checkpoints to workflows, e.g., after 'gh pr create' show how to verify the PR was created successfully with 'gh pr view'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary sections like 'When to Use This Skill' that restates the description, and the 'Resources' section at the end duplicates information already provided inline with the 📚 references. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready bash commands throughout. Every operation has concrete examples with actual command syntax, flags, and placeholders that Claude can immediately use. | 3 / 3 |
Workflow Clarity | Individual commands are clear but multi-step workflows lack explicit sequencing and validation checkpoints. For example, PR creation doesn't include verification steps (checking if PR was created, viewing the result), and there's no error handling guidance for failed operations. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview and well-signaled one-level-deep references to detailed documentation. Each reference file is clearly described with its purpose and when to load it, making navigation easy. | 3 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.