CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deploy-qm

Deploy the QM package from an organization-owned repository into Fly.io, AWS, or Render, onboard an administrator, configure connectors, and optionally activate Slack.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/deploy-qm/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 lean, well-intentioned router that gives a few concrete commands and good conditional loading guidance, but it delegates the entire deployment workflow and all substantive detail to files outside the bundle via a two-level chain of pass-through references. The body alone leaves an agent without the executable steps or ordered workflow it needs.

Suggestions

Inline or relocate the actual content: replace the pass-through reference stubs (each pointing to ../../../../cli/templates/deployment/references/*.md) with real content one level deep, or point SKILL.md directly at the final files so references are a single hop.

Include the deployment step sequence in the body (collect model key + sign-in method, choose broker, deploy via the selected provider, run acceptance checks, release gate) so the workflow does not depend solely on an external deployment.md.

State the key acceptance checks and the handoff deliverables concretely (e.g., the exact qm check --live command invocation and what the handoff must contain) instead of referencing them by name only.

DimensionReasoningScore

Conciseness

The body is lean (~150 words), assumes competence, and every sentence gives instruction (e.g., "Do not require or clone the QM source repository"). Not 5: email guidance is split across two paragraphs and "references/email.md" is named twice, a redundancy that could be trimmed into one statement.

4 / 5

Actionability

Concrete commands appear ("npm exec qm -- <command>", "qm admin-login", "qm check --live", "modelProvider"), but the actual deployment procedure is delegated to "../../../deployment.md", which lives outside the bundle — the key executable steps are missing from the body. Not 4: the gap is central, not minor; not 2: several specific, runnable commands are given.

3 / 5

Workflow Clarity

Sequence signals exist but are implicit in prose ("Collect both in the same pass", "Read references/email.md once the operator has chosen the broker") and the authoritative sequence is in the external deployment.md. A validation gate is named ("Treat qm check -- live... as the automated release gate") but the steps connecting the checkpoints are not laid out in-body. Not 4: the ordering is not clearly presented within the skill.

3 / 5

Progressive Disclosure

Top-level signaling is good ("Read only the selected provider reference", "Read references/slack.md only when Slack is requested"), but against the actual bundle every file in references/ is itself a pass-through pointer to "../../../../cli/templates/deployment/references/*.md" — a second indirection level that does not resolve in the bundle — and SKILL.md points to "../../../deployment.md" outside the bundle. Not 1: the top-level navigation is clear; not 3: the real content is buried two reference levels deep, matching the nested-pointer anti-pattern.

2 / 5

Total

12

/

20

Passed

Description

75%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 specific, distinctive description that clearly states what the skill does with concrete actions and named providers. Its only material weakness is the missing "when to use" trigger guidance, which caps completeness.

Suggestions

Append an explicit trigger clause such as "Use when the user asks to deploy or set up QM, onboard a QM administrator, or connect QM to Slack or an email provider."

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Deploy the QM package... into Fly.io, AWS, or Render", "onboard an administrator", "configure connectors", "optionally activate Slack" — with named deployment targets, giving comprehensive coverage of the skill's scope. Not 4: the enumerated actions cover the skill's full scope with no notable gaps.

5 / 5

Completeness

The "what" is clearly stated (deploy, onboard admin, configure connectors, activate Slack), but there is no "Use when..." clause or any equivalent trigger guidance, which caps completeness at 3. Not 4: the "when" is entirely absent rather than merely under-specified.

3 / 5

Trigger Term Quality

"Deploy", "QM", "Fly.io", "AWS", "Render", and "Slack" are natural terms a user would say when requesting this skill. Not 5: common variations and synonyms (e.g., "hosting", "rollout", "onboarding", "production setup") are absent; not 3: coverage of the core natural terms is solid.

4 / 5

Distinctiveness Conflict Risk

The named "QM package" plus specific providers ("Fly.io, AWS, or Render") carves out a clear niche with minimal conflict risk against generic deploy or admin skills. Not 4: the combination of product name and named providers makes mis-triggering very unlikely.

5 / 5

Total

17

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

yc-software/qm

Path

.codex/skills/deploy-qm/SKILL.md

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.