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.

71

Quality

89%

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

86%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 concise, well-structured single-purpose skill body with a clear workflow and validation checkpoint; the only meaningful gap is the lack of concrete nav MCP tool invocations, which caps actionability at 4.

Suggestions

Name the specific nav MCP tools (and their key parameters) to call when pulling commitment %, P&L components, fee/expense totals, and waterfall outputs, so the recompute step is copy-paste executable.

Add an explicit re-run/escalation loop for flagged mismatches (e.g., re-pull the disputed input and re-compare before promoting a flag) to strengthen the workflow's feedback loop.

Optionally state what to do when a 'next period's draft' is unavailable so the ending/beginning-capital rollover check has a defined fallback.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: a formula block, a tolerance value, and brief directives with no padding or explanation of concepts Claude already knows, so every token earns its place per the 5 anchor.

5 / 5

Actionability

Gives a concrete recomputation formula, an explicit 0.01 tolerance, and a worked flag example, but stops short of naming the actual nav MCP tool calls to invoke, leaving a minor execution gap versus the copy-paste-ready 5 anchor.

4 / 5

Workflow Clarity

Clear sequence (Recompute → Compare → Additional checks → Output) with an explicit comparison/tolerance checkpoint; the operation is non-destructive ('Do not edit the statement') so the destructive-cap does not apply, but there is no explicit re-run/escalation loop on flagged mismatches, keeping it at 4.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files and no need for external references, yet organized into clear, well-labeled sections, qualifying for the simple-skill exception at the 5 anchor.

5 / 5

Total

18

/

20

Passed

Description

87%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 tightly scoped, well-triggered description that clearly states both capability and timing, with only minor keyword-coverage and action-coverage gaps keeping specificity and trigger quality at 4.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'recompute the LP's capital account from the NAV components and flag any line that doesn't agree' — but coverage stops at recompute/flag/tie rather than enumerating the full set of tie-out operations, so it falls just below the comprehensive 5 anchor.

4 / 5

Completeness

Explicitly answers both what ('recompute the LP's capital account ... and flag any line that doesn't agree') and when ('Use before LP statements are distributed') with concrete trigger phrasing, matching the 5 anchor.

5 / 5

Trigger Term Quality

Strong natural domain terms a fund-accounting user would say ('LP statement', 'NAV pack', 'capital account', 'fund'), but a few common synonyms/variants (e.g. 'NAV tie-out', 'tie-out', 'capital call') are absent, leaving it just short of the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (LP statement vs. NAV pack tie-out) with distinct triggers and minimal realistic overlap with other skills.

5 / 5

Total

18

/

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.

Validation — 16 / 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.