CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

keep-qbr

Quarterly Business Review template generator — takes account info (ARR tier, adoption metrics, goals) and produces a complete QBR deck outline and talking points. Use when asked to "prepare a QBR", "build a quarterly review", "write our QBR agenda", or "create QBR talking points for this account".

Quality

80%

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 ./plugins/ai-agency/tonone/bundle/revenue-team/skills/keep-qbr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 body is a well-sequenced, highly actionable instruction skill with a concrete template, tier table, and checklists. Its main weaknesses are structural: the 70-line template is inlined rather than split into a reference file, and it depends on a docs/output-kit.md file (and an unexplained /atlas-report command) that are absent from the bundle.

Suggestions

Include the referenced output-format definition in the bundle (e.g., references/output-kit.md) or inline the actual rules for the 40-line CLI max, box-drawing skeleton, and severity indicators, since 'docs/output-kit.md' does not exist and Claude cannot follow it.

Move the 70-line QBR deck outline template from Step 2 into a reference file (e.g., references/qbr-template.md) and keep a brief section summary in SKILL.md so the main file stays a lean overview.

Explain or remove the '/atlas-report' delegation in the Delivery section — it references an external skill/command that is never defined, leaving the over-40-lines path undefined.

DimensionReasoningScore

Conciseness

Efficient overall: no explanations of concepts Claude already knows, and the 70-line deck outline is the deliverable template rather than padding. Minor trimming opportunities remain (some "Purpose:" lines and repeated section scaffolding), keeping it below the lean-everywhere anchor at 5.

4 / 5

Actionability

Mostly executable guidance: a runnable bash scan command, a tier-to-format table, a complete fill-in-the-blank deck template, and a post-QBR checklist. Not a 5 because the required output format is delegated to "docs/output-kit.md" ("40-line CLI max, box-drawing skeleton, unified severity indicators") which is not in the bundle, and "/atlas-report" is invoked without explanation.

4 / 5

Workflow Clarity

Steps 0-4 are clearly sequenced with conditional branches ("If there are open escalations or health signals below GREEN", "If output exceeds 40 lines, delegate") and a closing checklist. Minor validation gaps — there is no explicit check of the produced output, and the missing output-kit.md leaves the delivery format ambiguous — so it does not reach 5.

4 / 5

Progressive Disclosure

Sections and steps are well organized, but the skill is ~135 lines with the 70-line deck template inlined in Step 2 where it belongs in a separate reference file, and the body references "docs/output-kit.md" which does not exist in the bundle (no references/, scripts/, or assets/ directories). This matches the anchor of some structure with references that are neither clearly signaled nor resolvable.

3 / 5

Total

15

/

20

Passed

Description

83%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 description: it is written in third person, clearly states what the skill consumes and produces, and provides four natural quoted trigger phrases for when to use it. The only weaknesses are minor — a few missing synonyms and slight overlap risk with non-customer "quarterly review" requests.

DimensionReasoningScore

Specificity

Lists several concrete actions — "takes account info (ARR tier, adoption metrics, goals)" and "produces a complete QBR deck outline and talking points" — with precisely named inputs. Not a 5 because coverage has minor gaps (tier-based formatting, post-QBR follow-up actions are unstated); not a 3 because it goes beyond 1-2 generic actions with specific input parameters.

4 / 5

Completeness

Explicitly answers both questions: the "what" (takes account info with named inputs and produces a deck outline and talking points) and the "when" ("Use when asked to..." with four concrete quoted trigger phrases). This directly matches the anchor for clearly and explicitly answering both with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases users would actually say: "prepare a QBR", "build a quarterly review", "write our QBR agenda", "create QBR talking points", plus the spelled-out "Quarterly Business Review". Not a 5 because a few natural synonyms are missing (e.g., "executive business review", "quarterly account review").

4 / 5

Distinctiveness Conflict Risk

The QBR/customer-account niche with ARR-tier triggers is mostly distinct, and account-scoped phrases like "create QBR talking points for this account" are unlikely to misfire. Minor overlap risk remains: "build a quarterly review" without account context could also match an employee performance-review skill, which keeps it below a 5.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

jeremylongshore/tons-of-skills-marketplace

Path

plugins/ai-agency/tonone/bundle/revenue-team/skills/keep-qbr/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.