qtpass-github

QtPass GitHub interaction - PRs, issues, branches, merging

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/qtpass-github/SKILL.md

Quality

Content

77%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 highly actionable with concrete, executable commands and well-sequenced workflows that include validation checkpoints and error-recovery troubleshooting. Its main weakness is token efficiency and progressive disclosure: it is a long monolithic file that over-explains familiar concepts and could split reference material into bundle files.

Suggestions

Trim over-explanation of concepts Claude already knows (HEREDOC mechanics, squash-merge rationale, generic communication advice).

Move long reference material (AI-powered bug detection, GraphQL review-thread resolution) into files under references/ and link to them from SKILL.md.

Consolidate overlapping force-push guidance, which currently appears in three separate sections, into one canonical section.

Dimension	Reasoning	Score
Conciseness	The body is command-dense and mostly efficient, but pads with concepts Claude already knows (HEREDOC shell mechanics, squash-merge philosophy, generic 'be clear and concise' advice in Good Practices/Answering User Questions).	3 / 5
Actionability	Provides fully executable, copy-paste-ready gh/git commands with specific examples covering the common cases (PR checks, creation, squash/auto merge, commenting, CI debugging, conflict resolution).	5 / 5
Workflow Clarity	Multi-step processes are clearly sequenced with explicit validation (Pre-PR and Pre-Merge checklists, 'Checking PR Status Before Merging') and feedback loops for error recovery (Resolving Merge Conflicts, Troubleshooting).	5 / 5
Progressive Disclosure	Section headers are well organized, but the ~470-line skill inlines everything (AI findings, GraphQL thread resolution, HEREDOC tutorial) with no references to separate files; the under-50-line simple-skill exception does not apply.	3 / 5
	Total	16 / 20 Passed

Description

61%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 third-person, concise, and names a clear domain with several relevant action areas, but it omits any explicit 'when to use' trigger guidance, which caps its completeness. Adding a 'Use when...' clause with natural trigger phrases would meaningfully raise the score.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when managing QtPass PRs, issues, branches, or merges on GitHub.'

Expand the noun list into concrete actions, e.g. 'create and merge PRs, triage issues, rebase branches, debug CI'.

Add common synonyms such as 'pull requests' and 'CI checks' alongside 'PRs' for broader trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('QtPass GitHub interaction') and several action areas ('PRs, issues, branches, merging'), but these are terse nouns rather than comprehensive concrete actions, fitting the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	Provides a clear 'what' (QtPass GitHub interaction covering PRs/issues/branches/merging) but lacks any 'Use when...' trigger clause, so completeness is capped at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('PRs', 'issues', 'branches', 'merging', 'GitHub'), with only minor synonyms missing (e.g., 'pull requests', 'code review', 'CI').	4 / 5
Distinctiveness Conflict Risk	The 'QtPass' scoping gives it a clear niche distinct from generic skills, though the GitHub PR/issue/branch workflow still has minor overlap risk with general git/github skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: IJHack/QtPass
Path: .opencode/skills/qtpass-github/SKILL.md
Commit: 9972a3c

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.