precedent-transactions

Precedent M&A transactions analysis with deal multiples and acquisition history

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/daloopa/skills/precedent-transactions/SKILL.md

Quality

Content

85%Weight 40%Scale 1-3

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

The body is a well-sequenced, highly actionable workflow with strong validation checkpoints and good progressive disclosure via externalized data-access and design-system references. The only meaningful weakness is mild verbosity in the inline HTML report template and repeated cross-references.

Suggestions

Move the full HTML report structure template into a reference file (e.g. references/report-template.html) and keep only the section list and citation rules inline, to tighten the body.

Consolidate the scattered 'see ../data-access.md Section X' callouts into a single up-front pointer plus inline notes only where the section is load-bearing for a step.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence (no basic-concept padding), but the inline HTML report template and repeated 'see ../data-access.md Section X' callouts add length that could be tightened or delegated, placing it at 'mostly efficient but could be tightened.'	2 / 3
Actionability	It provides fully executable guidance: named tool calls (discover_companies, discover_company_series, get_company_fundamentals), exact search-query strings, output path, citation format, and explicit multiple formulas — copy-paste ready.	3 / 3
Workflow Clarity	A clearly numbered 9-step sequence with explicit validation checkpoints (N/A-when-unsourced rule, '<3 data points is not meaningful', Daloopa fallback logic, and the 'ask for a ticker before proceeding' guard) gives strong feedback loops for the batch deal-sourcing operation.	3 / 3
Progressive Disclosure	Data access and formatting conventions are externalized to well-signaled, one-level-deep sibling files ('Before starting, read ../data-access.md ... and ../design-system.md'), and the body is organized into clearly numbered sections, giving easy navigation.	3 / 3
	Total	11 / 12 Passed

Description

57%Weight 40%Scale 1-3

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 concise and identifies a distinct valuation niche with a couple of concrete deliverables, but it lacks an explicit 'Use when' trigger clause and only partially covers natural trigger-term variations. It is solid but leaves the model to infer when to invoke it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when valuing a company via precedent M&A transactions, deal comps, or acquisition multiples.'

Broaden trigger-term coverage to include common phrasings users say: 'precedent transactions', 'transaction comps', 'deal comps', and 'M&A valuation'.

Enumerate the concrete outputs more fully (e.g. '...builds a comparable deals table with EV/Revenue and EV/EBITDA multiples, and the company's own acquisition history') to lift specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('Precedent M&A transactions analysis') and two concrete outputs ('deal multiples and acquisition history'), but the action verb 'analysis' is generic and the deliverables are not enumerated comprehensively, so it stops at 'names domain and some actions.'	2 / 3
Completeness	It states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2 even though the 'what' is present.	2 / 3
Trigger Term Quality	It includes relevant domain keywords ('Precedent M&A transactions', 'deal multiples', 'acquisition history') a finance user might say, but omits common variations like 'comps', 'transaction comps', or 'M&A valuation', so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	'Precedent M&A transactions analysis with deal multiples and acquisition history' carves a clear niche (closed M&A deals) that is distinguishable from trading comps or DCF skills, making unintended triggering unlikely.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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: openai/plugins
Path: plugins/daloopa/skills/precedent-transactions/SKILL.md
Commit: 11c74d6

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.