CtrlK
BlogDocsLog inGet started
Tessl Logo

chronograph-portfolio-company-one-pager

GP platform one-pager and investor report generator for private equity portfolio companies. Use this skill whenever a user asks to generate a company tearsheet, one-pager, investor report, portfolio overview, or company deep-dive — especially when they name a company or ask to "build a report", "create a one-pager", or "show me a tearsheet". Also trigger when the user asks to include commentary, quarterly updates, investment narratives, or any Investment Overview in the report output. This skill handles live data fetching via a connected MCP data source OR from an uploaded Excel model, metric formatting, AI-generated or model-sourced commentary, and rendering a fully styled HTML one-pager. Also trigger for LP quarterly updates, valuation summaries, and portco performance pages — any output that combines financials, valuation, and return data for a single portfolio company.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is highly actionable with a clear, validated multi-step workflow and tight formatting/error guidance, but it is monolithic — a large single file with some redundancy and no progressive disclosure into bundle files. Splitting the brand-token schema and panel specs into reference files and de-duplicating the metric-selection guidance would lift both weak dimensions.

Suggestions

Move the Brand Token Schema (0C), full panel specifications (Step 4), and the CSS-variable/formatter blocks into reference files (e.g. BRAND_TOKENS.md, PANEL_SPEC.md) referenced one level deep from SKILL.md to improve progressive disclosure.

De-duplicate the metric-selection guidance: keep either the prose 'Metric selection rule' or the numbered Priority list, not both, and remove the inline `←` annotations from the defaults block to tighten conciseness.

Consolidate the per-situation guidance that currently appears in both Step 2 'If something is missing' and the 'Error Handling' matrix into a single source to reduce repetition.

DimensionReasoningScore

Conciseness

Mostly efficient with no basic-concept padding, but carries redundancy — the metric-type selection philosophy is stated in prose and then re-stated as a numbered priority list, and inline `←` annotations inflate the defaults block — so it sits at 'mostly efficient but could be tightened' rather than the lean 'every token earns its place' level.

2 / 3

Actionability

Provides concrete, copy-paste-ready guidance throughout — a populated CSS-variable block, an inline-SVG chart spec with an auto-scale formula, a formatting table ('$43.5m', '1.41x', '▲ +X%'), a file-name pattern with examples, and a pandas `data_only=True` call; the substitution placeholders are the intended mechanism, not pseudocode, and the rubric exempts actionable instruction-only skills for lacking full runnable code.

3 / 3

Workflow Clarity

Clear numbered Step 0–8 sequence with explicit decision trees, a numbered fetch sequence, 'If something is missing' recovery branches, a discovery/help checkpoint before metric queries, an error-handling matrix, and a 'verify before rendering' checklist — explicit validation checkpoints, not implicit ones.

3 / 3

Progressive Disclosure

A single ~470-line SKILL.md with no references/scripts/assets bundle (verified absent) holds the full brand-token schema, panel specs, formatting rules, CSS block, error matrix, and checklist inline; it is well-organized into sections but material that should be split into reference files is inline, so it does not reach the 'overview pointing to one-level-deep references' level.

2 / 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 specific, third-person, and provides excellent natural trigger coverage plus explicit what-and-when guidance within a distinct niche. No first/second-person voice is used, so no specificity penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'handles live data fetching via a connected MCP data source OR from an uploaded Excel model, metric formatting, AI-generated or model-sourced commentary, and rendering a fully styled HTML one-pager' — which matches the 'lists multiple specific concrete actions' anchor rather than the partial 'names domain and some actions' level below.

3 / 3

Completeness

Explicitly answers both what (one-pager/investor report generator: fetching, formatting, commentary, HTML rendering) and when ('Use this skill whenever a user asks…', 'Also trigger when…'), satisfying the explicit-triggers anchor; not a 2 because the 'when' is stated, not merely implied.

3 / 3

Trigger Term Quality

Covers natural user phrasing broadly — 'tearsheet, one-pager, investor report, portfolio overview, company deep-dive', 'build a report', 'create a one-pager', 'show me a tearsheet', 'LP quarterly updates, valuation summaries' — well beyond the 'some relevant keywords' level.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear PE portco-reporting niche (Chronograph MCP / Excel one-pagers) with domain-specific triggers unlikely to collide with generic skills, matching the 'clear niche with distinct triggers' anchor.

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
openai/plugins
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.