push
Push approval protocol and post-push CI watching
75
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
22%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 description is too terse and abstract to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and sufficient detail about what the skill actually does. The technical terms present provide minimal differentiation but don't compensate for the missing specificity and completeness.
Suggestions
Add explicit actions describing what the skill does, e.g., 'Manages push approval workflows, monitors CI pipeline status, and reports build results'
Include a 'Use when...' clause with natural trigger terms like 'Use when pushing code, checking build status, waiting for CI, or needing approval for merges'
Expand trigger terms to include variations users might say: 'CI', 'continuous integration', 'pipeline', 'build', 'GitHub Actions', 'checks'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('protocol', 'watching') without listing concrete actions. It doesn't specify what actions are performed - no verbs like 'approve', 'monitor', 'notify', or 'track'. | 1 / 3 |
Completeness | The description only vaguely hints at 'what' (something about push approval and CI watching) and completely lacks any 'when' guidance. No 'Use when...' clause or equivalent trigger guidance is present. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('push', 'approval', 'CI') that users might mention, but missing common variations like 'continuous integration', 'pipeline', 'build status', 'merge', or 'deploy'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'push approval' and 'CI watching' provides some specificity, but 'protocol' is vague and could overlap with other CI/CD or git-related skills. The scope is unclear. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill that demonstrates excellent token efficiency while providing complete, actionable guidance. The two-flow structure clearly distinguishes approval requirements, the CI watching loop includes proper feedback mechanisms, and all commands are executable. The skill respects Claude's intelligence while adding genuine value through specific workflow constraints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No explanation of what git or CI is, no padding. The skill assumes Claude knows how to use git and gh commands. | 3 / 3 |
Actionability | Provides specific, executable commands (git log, gh pr create, gh run list, gh run view) with exact flags. Clear copy-paste ready examples throughout. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflows with explicit sequences, validation checkpoints (CI watching), and feedback loops (fix -> commit -> push -> poll again). Clear distinction between user-initiated and agent-initiated flows. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Rule, Two flows, After Push, After Draft PR). References the commit skill appropriately. Content is appropriately sized for a single file without needing external references. | 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.
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.