CtrlK
BlogDocsLog inGet started
Tessl Logo

tearsheet

Quick one-page company overview and snapshot

55

Quality

61%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/daloopa/skills/tearsheet/SKILL.md
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 content is a strong, highly actionable multi-step workflow with concrete tool calls, formulas, and an explicit HTML template and citation format. Its main gaps are mild verbosity in the KPI examples and the absence of an explicit validation checkpoint on the final report.

Suggestions

Add an explicit validation step before saving, e.g. confirm every financial cell has a Daloopa citation and that no financial-statement items leaked into the Operating KPIs table.

Tighten the business-model KPI list and Apple-specific example into a shorter reference or move them to a referenced file to reduce token weight.

Consider a brief checklist at the end of Section 9 confirming all required report sections are present before declaring the report saved.

DimensionReasoningScore

Conciseness

Mostly efficient with every section earning its place via actionable specifics, but stretches like the long business-model KPI list and Apple-specific guidance could be tightened and partially restate knowledge Claude already has.

2 / 3

Actionability

It gives concrete function names (discover_companies, get_stock_prices), exact fields, computation formulas, citation format, HTML structure, and WebSearch query templates, making the guidance directly executable.

3 / 3

Workflow Clarity

The 9-step sequence is clearly ordered with useful conditional guidance (ask for ticker if missing, broaden search on empty), but there is no explicit validation checkpoint on the final HTML deliverable.

2 / 3

Progressive Disclosure

The body is well-organized into numbered sections and points to two clearly-signaled one-level-deep external references (../data-access.md, ../design-system.md) with section anchors, with no nested references.

3 / 3

Total

10

/

12

Passed

Description

50%

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 conveys the deliverable (a one-page company snapshot) but is vague about actions and lacks an explicit use-trigger, which is the main weakness. It is recognizable enough to avoid being generic, but misses the trigger-term and completeness detail of strong descriptions.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for a company tearsheet, one-page snapshot, or quick stock overview."

Name concrete actions: "Generate a one-page tearsheet pulling financials, KPIs, capital return, ratios, recent developments, and news."

Include the natural keyword "tearsheet" so the description matches how an analyst would phrase the request.

DimensionReasoningScore

Specificity

Names a concrete deliverable ("one-page company overview and snapshot") but lists no actions (e.g. generate, extract, pull financials), so it is more specific than "helps with documents" yet stops short of listing concrete actions.

2 / 3

Completeness

It states what the skill produces but has no "Use when..." trigger clause, so per the guidelines completeness is capped at 2 even though the what is clear.

2 / 3

Trigger Term Quality

"overview" and "snapshot" are somewhat natural but the description omits common analyst terms a user would say (tearsheet, company analysis, stock snapshot), giving partial keyword coverage.

2 / 3

Distinctiveness Conflict Risk

The financial-analyst framing is somewhat distinctive but "company overview" could overlap with other analysis/reporting skills, so it is not a fully clear niche.

2 / 3

Total

8

/

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.