CtrlK
BlogDocsLog inGet started
Tessl Logo

qtpass-github

QtPass GitHub interaction - PRs, issues, branches, merging

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

77%

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 executable commands and well-structured checklists, but it is a long monolith that repeats patterns and includes some generic explanation. Splitting reference material into bundle files and trimming redundancy would improve both conciseness and progressive disclosure.

Suggestions

Split large topical sections (e.g. merge strategies, CI debugging, AI findings, troubleshooting) into reference files under ./references/ and link to them from SKILL.md.

De-duplicate the repeated update-with-main and --force-with-lease patterns by consolidating them into a single canonical snippet and referencing it.

Remove generic guidance Claude already knows (HEREDOC mechanics, communication best-practices lists) to tighten the token budget.

DimensionReasoningScore

Conciseness

The body is mostly efficient command reference, but it repeats the update-with-main and force-with-lease patterns multiple times and includes generic guidance Claude already knows (HEREDOC mechanics, communication 'Good Practices').

2 / 3

Actionability

It provides fully executable, copy-paste-ready `gh` and `git` commands with concrete flags and placeholders, matching the score-3 anchor for executable guidance.

3 / 3

Workflow Clarity

Multi-step workflows include explicit checklists (Pre-PR, Pre-Merge) and verification before destructive operations (mergeable/CI/approval checks, --force-with-lease), satisfying the score-3 anchor.

3 / 3

Progressive Disclosure

The ~470-line body is well-sectioned but monolithic with no external reference files, matching the score-2 anchor of substantial inline content that could be split out.

2 / 3

Total

10

/

12

Passed

Description

67%

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 specific and clearly niched to QtPass GitHub workflows, but it lacks an explicit 'when to use' trigger clause and broader natural term variations. Adding usage triggers would raise its completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when working with PRs, issues, or branches on the QtPass repository, merging changes, or debugging CI.'

Add common trigger-term variations such as 'pull requests', 'code review', and 'CI checks' so the description matches language users actually say.

DimensionReasoningScore

Specificity

The description names multiple concrete actions — 'PRs, issues, branches, merging' — which is comparable to the score-3 anchor that lists several specific operations.

3 / 3

Completeness

It states what the skill does but provides no 'Use when...' clause or equivalent trigger guidance, which the guidelines cap at 2.

2 / 3

Trigger Term Quality

It includes relevant natural keywords ('PRs', 'issues', 'branches', 'merging') but misses common variations a user might say such as 'pull request', 'code review', or 'CI', matching the score-2 anchor.

2 / 3

Distinctiveness Conflict Risk

The 'QtPass GitHub interaction' framing establishes a clear, repo-specific niche with distinct triggers that is unlikely to conflict with other skills.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
IJHack/QtPass
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.