CtrlK
BlogDocsLog inGet started
Tessl Logo

client-review

Prepare for client review meetings with portfolio performance summary, allocation analysis, talking points, and action items. Pulls together account data into a concise meeting-ready format. Use before quarterly reviews, annual checkups, or ad-hoc client meetings. Triggers on "client review", "meeting prep for [client]", "quarterly review", "prep for [client name]", or "client meeting".

68

Quality

82%

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

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-structured with useful table templates and a logical six-step flow, but it stops at scaffolding rather than executable detail and omits validation checkpoints for compliance-sensitive outputs.

Suggestions

Add an explicit validation/review checkpoint in Step 6 (e.g., 'Verify all figures reconcile to source statements and that materials pass compliance review before sending').

Fill in at least one row of a table with a worked example so the guidance becomes copy-paste concrete rather than a blank template.

Add concrete tactical detail for Step 5 recommendations, such as threshold values or example trade logic, to lift actionability toward copy-paste ready.

DimensionReasoningScore

Conciseness

Lean, table-driven body with no padding of concepts Claude already knows; every section earns its place and assumes competence.

3 / 3

Actionability

Provides structured table templates and specific metrics to fill, but the guidance is templated rather than copy-paste executable — there are no concrete commands or completed examples, only blank scaffolds.

2 / 3

Workflow Clarity

Six sequenced steps with timing are clear, but the workflow lacks validation/verification checkpoints (e.g., confirming data accuracy or IPS compliance before output), which caps clarity at 2 per the batch/risky-operations guideline.

2 / 3

Progressive Disclosure

A single self-contained document with well-organized sections and no bundle files; it stays appropriately shallow but contains no signaled references that would push it to the clear-overview-with-navigation anchor.

2 / 3

Total

9

/

12

Passed

Description

100%

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 concise, specific, and complete, naming concrete deliverables and explicit trigger phrases in third person. It cleanly answers both what the skill does and when to use it.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'portfolio performance summary, allocation analysis, talking points, and action items' — matching the anchor for listing several specific actions.

3 / 3

Completeness

Clearly answers both what (the prep deliverables) and when via an explicit 'Use before quarterly reviews, annual checkups, or ad-hoc client meetings' clause.

3 / 3

Trigger Term Quality

Includes natural phrases a user would actually say: 'client review', 'quarterly review', 'meeting prep for [client]', and 'client meeting', giving good coverage.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (client review meeting prep) with distinct financial-advisor triggers unlikely to conflict with other skills.

3 / 3

Total

12

/

12

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
anthropics/financial-services
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.