CtrlK
BlogDocsLog inGet started
Tessl Logo

update-qm

Update a QM source fork by merging upstream, or upgrade a package deployment dependency, and open a PR. Use when asked to "update qm", "sync from upstream", "pull in the latest qm".

73

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A mature, action-oriented skill body with strong sequencing, real validation checkpoints, and a sharp 'Never do these' guardrail section. It is concise for its complexity and avoids padding, though some rationale prose and a couple of external-doc pointers could be tightened.

DimensionReasoningScore

Conciseness

Dense and largely assumes Claude's competence (no primer on what forks/rebase are), but a few rationale sentences and external-doc pointers ('See the README source deployment procedure', 'per AGENTS.md') could be trimmed without losing the decision guidance.

4 / 5

Actionability

Provides copy-paste-ready commands with placeholders for both paths — `npm install --save-exact @yc-software/qm@<version>`, the full merge block, `node cli/bin/qm.ts check --config ...`, and `gh pr create --repo <source-fork>` — covering the common cases.

5 / 5

Workflow Clarity

Clear sectioned sequence (identify → merge → resolve → verify → open PR) with explicit validation checkpoints (`npm ci`, typecheck/lint, CLI check/doctor/plan) and feedback loops (Already-up-to-date → delete branch; contract-major mismatch → adapt config).

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references, and the external pointers (AGENTS.md, README, upstream-pr skill) are one level deep; however everything is inlined in a ~140-line file with no content split into bundle files.

4 / 5

Total

18

/

20

Passed

Description

92%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.

A strong, third-person description that crisply separates the two update paths and pairs them with concrete natural trigger phrases. Minor room to broaden trigger synonyms, but it answers both 'what' and 'when' unambiguously.

DimensionReasoningScore

Specificity

Names multiple concrete actions across two distinct paths — 'merging upstream', 'upgrade a package deployment dependency', and 'open a PR' — giving comprehensive coverage rather than generic verbs.

5 / 5

Completeness

Explicitly states what the skill does ('Update a QM source fork... or upgrade a package deployment dependency, and open a PR') and when to use it ('Use when asked to...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Quotes three natural user phrases ('update qm', 'sync from upstream', 'pull in the latest qm'), but coverage stops there without synonyms or version/extension-style variants a user might also say.

4 / 5

Distinctiveness Conflict Risk

Occupies a narrow, well-defined niche (QM fork sync vs package-deployment upgrade) with distinctive triggers unlikely to collide with unrelated skills.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
yc-software/qm
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.