company-research

Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.

Quality

67%

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 ./skills/company-research/SKILL.md

Quality

Content

56%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 thorough, well-sequenced research skill with concrete templates and worked examples, but it is noticeably verbose and inlines the bulk template content that its own references point to as separate (and currently missing) files. Tightening the body and actually providing template.md would meaningfully improve it.

Suggestions

Move the nine step template blocks into the referenced template.md (and provide examples/sample.md), keeping only a concise overview and one-line pointers in SKILL.md to reduce length and fix the missing bundle files.

Trim padding sections such as 'Why This Works' and 'When to Use This' (which duplicates the frontmatter description's triggers) and consolidate the repeated per-step 'Sources to check' lists into a single shared source-checklist reference.

Add an explicit final verification step (e.g., a completeness/source-citation checklist applied to the drafted brief) to close the workflow with a clear validation checkpoint.

Dimension	Reasoning	Score
Conciseness	The ~388-line body is noticeably verbose: nine near-identical fill-in template blocks, repeated 'Sources to check' lists per step, and padding sections like 'Why This Works' and 'When to Use This' (which duplicates the description's triggers) restate obvious points and could be trimmed.	2 / 5
Actionability	Concrete step templates with specific fields, per-step 'Sources to check' lists, and worked Stripe examples give mostly executable guidance; it is not a 5 because some sections are conditional/high-level ('If applicable, capture PLG strategies') and the deliverable is templates rather than copy-paste code.	4 / 5
Workflow Clarity	A clear nine-step sequence with partial checkpoints (Step 3 'Quality checks' and the 'Common Pitfalls' section), but no consolidated final verification or feedback loop, leaving minor validation gaps; the destructive-cap-at-3 rule does not apply to this research skill.	4 / 5
Progressive Disclosure	Section structure is good and references to template.md and examples/sample.md are clearly signaled, but the nine inlined template blocks are exactly the content the skill says belongs in template.md — and that file does not exist in the bundle — so content that should be separate is inline.	3 / 5
	Total	13 / 20 Passed

Description

78%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 well-constructed description that explicitly answers both what the skill does and when to use it with concrete, natural trigger phrases in third-person voice. Its main limitation is that it frames one composite action rather than enumerating several discrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain and the composite action ('Create a company research brief with executive quotes, product strategy, and org context') but offers effectively one action with sub-elements rather than several discrete concrete actions, so it falls short of the 'several specific actions' anchor.	3 / 5
Completeness	It clearly states what the skill does and follows with an explicit 'Use when…' clause listing concrete triggers, mirroring the anchor-5 example structure; the 'when' is already explicit and specific, so it is not the 4 anchor.	5 / 5
Trigger Term Quality	'Use when preparing for interviews, competitive analysis, partnerships, or market-entry work' supplies natural user phrases with good coverage, but misses common synonyms such as 'company profile', 'competitor brief', or 'due diligence'.	4 / 5
Distinctiveness Conflict Risk	'Company research brief' carves a clear niche with distinct triggers, but the body's related-skills list (positioning-statement, pestel-analysis, proto-persona) signals adjacent market-intelligence skills, indicating minor overlap risk.	4 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/company-research/SKILL.md
Commit: 1b5a524

Reviewed: 4 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.