CtrlK
BlogDocsLog inGet started
Tessl Logo

nav-tieout

Tie an LP statement to the fund's NAV pack — recompute the LP's capital account from the NAV components and flag any line that doesn't agree. Use before LP statements are distributed.

70

Quality

85%

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

85%

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

A concise, well-structured verification workflow with explicit validation checkpoints appropriate to a read-only reconciliation skill. The main gap is actionability: the computation is fully specified but the actual NAV data retrieval is left abstract without naming the MCP tools or calls to use.

Suggestions

Name the specific nav MCP tools/calls (or the exact pack fields) used to retrieve LP commitment %, fund-level P&L components, fee/expense totals, and waterfall outputs so the retrieval step is executable.

Add one concrete worked example showing a recomputed line alongside the statement value and the resulting flag (e.g., the 12.40% vs 12.38% ownership case) to make the compare-and-flag step copy-paste ready.

DimensionReasoningScore

Conciseness

Lean body with no padding or explanation of concepts Claude already knows; the recompute formula, tolerance, checks, and output spec each earn their place.

3 / 3

Actionability

The recomputation formula, 0.01 tolerance, and per-line comparison instructions are concrete, but the data-retrieval mechanism is underspecified — 'via the nav MCP' and 'Pull each input from the NAV pack' name no specific MCP tools or calls, leaving the execution path incomplete.

2 / 3

Workflow Clarity

A clear Recompute → Compare → Additional checks → Output sequence with explicit validation checkpoints (per-line comparison at 0.01 tolerance plus the cross-footing checks); the skill is read-only by design so no fix-retry loop is required.

3 / 3

Progressive Disclosure

Under 50 lines, single-purpose, with no need for external references; the well-organized sections satisfy the simple-skill exception for the top level.

3 / 3

Total

11

/

12

Passed

Description

85%

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, well-scoped description that clearly states both capability and when to use it, with a distinct niche. Its only weakness is trigger-term coverage: it relies on a single phrasing of each domain term and a timing clause instead of enumerating the natural variations a user might say.

Suggestions

Add a 'Use when reconciling LP statements to the NAV pack, tying out LP capital accounts, or investigating NAV vs. statement discrepancies' clause to broaden natural trigger coverage.

Include common user phrasings such as 'reconcile', 'tie out', or 'LP capital account reconciliation' alongside 'LP statement' and 'NAV pack'.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'recompute the LP's capital account from the NAV components and flag any line that doesn't agree' — matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

Clearly answers what ('recompute the LP's capital account... and flag any line that doesn't agree') and when ('Use before LP statements are distributed'), satisfying the explicit-trigger requirement for the top level.

3 / 3

Trigger Term Quality

Relevant niche keywords ('LP statement', 'NAV pack', 'capital account') appear, but only one phrasing of each and the 'Use before LP statements are distributed' clause is a timing instruction rather than coverage of natural trigger variations a user would say.

2 / 3

Distinctiveness Conflict Risk

A narrow LP-statement-to-NAV-pack tie-out niche with distinct domain triggers, very unlikely to fire for an unrelated skill.

3 / 3

Total

11

/

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.