CtrlK
BlogDocsLog inGet started
Tessl Logo

portfolio-monitoring

Track and analyze portfolio company performance against plan. Ingests monthly/quarterly financial packages (Excel, PDF), extracts KPIs, flags variances to budget, and produces summary dashboards. Use when reviewing portfolio company financials, preparing board materials, or monitoring covenant compliance. Triggers on "review portfolio company", "monthly financials", "how is [company] performing", "covenant check", or "portfolio update".

70

Quality

86%

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

72%

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 concrete variance thresholds and an output template, but it stops short of full actionability by leaving the ingestion/extraction method unspecified and lacks validation checkpoints in its workflow. Adding a concrete extraction approach and a verification step would round it out.

Suggestions

In Step 1, specify how to extract financials from Excel/PDF/CSV (e.g., named library, sheet/range to read, or how to ask the user to paste structured data) so the ingestion step is executable rather than descriptive.

Add an explicit validation checkpoint before Step 3 — e.g., 'Confirm extracted figures tie out (Revenue - COGS ≈ Gross Profit; ending cash reconciles to prior period + FCF)' — and a re-check loop if they don't, to satisfy the workflow_clarity feedback-loop expectation for batch ingestion.

For covenant compliance, require confirming the credit agreement's defined terms (leverage, interest coverage, default thresholds) before flagging a breach, rather than flagging against assumed levels.

DimensionReasoningScore

Conciseness

The body is lean and list-driven, assuming Claude's competence (it never explains what EBITDA, covenants, or leverage ratios are), and every section earns its place; it does not pad with concepts Claude already knows (score 1) or carry removable filler (score 2).

3 / 3

Actionability

Concrete elements exist — variance thresholds (5%, 5-15%, >15%) and a 5-item output template — but Step 1 ('Extract key financials: Revenue, EBITDA...') gives no method for parsing Excel/PDF/CSV, leaving a key detail unspecified, matching the score-2 anchor rather than fully copy-paste-ready guidance.

2 / 3

Workflow Clarity

Four steps are clearly sequenced, but there are no validation or verification checkpoints (no 'confirm figures tie out', no re-check loop) for an ingestion-and-flagging workflow; per the feedback_loops note this caps the score at 2 rather than reaching the explicit-checkpoint level of 3.

2 / 3

Progressive Disclosure

The skill is self-contained and under the simple-skill threshold with no bundle files, and its content is well-organized into a numbered Workflow and an Important Notes section, qualifying for the score-3 simple-skill exception rather than the poorly-organized or nested-reference patterns.

3 / 3

Total

10

/

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 strong across the board: it names concrete capabilities, includes natural trigger phrases, explicitly states both what and when, and occupies a distinct niche. It reads as a model 'Use when...' description with no padding or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Ingests monthly/quarterly financial packages (Excel, PDF)', 'extracts KPIs', 'flags variances to budget', 'produces summary dashboards'), matching the score-3 anchor for multiple specific concrete actions rather than the partial domain-only coverage of a 2.

3 / 3

Completeness

Explicitly answers both what it does (ingest, extract KPIs, flag variances, produce dashboards) and when to use it via an explicit 'Use when...' clause plus a 'Triggers on...' list, matching the score-3 anchor rather than the what-only 2.

3 / 3

Trigger Term Quality

Provides natural phrases users would say — 'review portfolio company', 'monthly financials', 'how is [company] performing', 'covenant check', 'portfolio update' — giving good coverage of natural terms rather than only a few relevant keywords (score 2).

3 / 3

Distinctiveness Conflict Risk

Occupies a clear portfolio-company monitoring niche with distinct triggers (covenant check, board materials, portfolio update), making it unlikely to fire for the wrong skill rather than being merely somewhat specific (score 2).

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.