CtrlK
BlogDocsLog inGet started
Tessl Logo

company-funding-search

Find company funding history, investors, and investment details

49

Quality

53%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/lead-generation/capabilities/company-funding-search/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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.

The content is well-structured and provides concrete, example-driven commands, but it is held back by redundant sections, a non-executable primary Nyne Step 1 body (empty api/path), and a polling workflow missing an explicit completion check. Fixing the Step 1 payload and adding a poll-until-complete loop would meaningfully improve actionability and workflow clarity.

Suggestions

Fill in the real api/path values in the primary Nyne Step 1 POST body (currently empty 'api':''/'path':'') so the command is executable as written rather than only in the collapsible equivalent.

Consolidate the duplicated Nyne-async and 'company_name > company_domain' guidance so it appears in one place rather than in both Error Handling and Tips.

Add an explicit poll-until-complete loop for Nyne (e.g. 'poll until status is complete or results are populated, typically 5-20 seconds') with a 429 retry-with-backoff step to make the workflow's checkpoints explicit.

DimensionReasoningScore

Conciseness

The body is mostly efficient but repeats the same guidance across 'When to Use', 'Error Handling', and 'Tips' (e.g. Nyne-async polling and 'company_name > company_domain' appear twice), which could be consolidated.

3 / 5

Actionability

Concrete curl commands with example payloads are provided, but the primary Nyne Step 1 POST uses empty 'api'/'path' placeholders so it is not executable as written; the real endpoint only appears in the collapsible equivalent.

3 / 5

Workflow Clarity

The async Nyne flow has a clear POST→request_id→poll sequence, but the polling step lacks an explicit completion/status check and 404/429 handling is a bare list without a retry loop.

3 / 5

Progressive Disclosure

Content is well-organized into clear headed sections with a comparison table and collapsible secondary curl equivalents; no bundle files exist so no external references are needed, with only minor redundancy-based organization gaps.

4 / 5

Total

13

/

20

Passed

Description

53%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.

The description is concise and names a clear, specific niche but omits any 'Use when...' trigger guidance, which caps completeness at 3 and limits trigger-term coverage. Adding explicit trigger phrases and synonyms would raise it across multiple dimensions.

Suggestions

Append a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user asks how much funding a company raised, who invested in a company, or to find companies by funding stage.'

Add natural synonyms users actually say such as 'funding rounds', 'venture capital', 'VCs', and 'Series A/B' to broaden trigger-term coverage.

Use a more specific verb than the generic 'Find' (e.g., 'Look up company funding history and investors, and search companies by funding stage') to increase action specificity.

DimensionReasoningScore

Specificity

The description names the funding domain and one concrete action ('Find') applied to three targets (funding history, investors, investment details), matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

It has a clear 'what' (find funding history, investors, investment details) but no 'Use when...' trigger clause, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

It includes some natural terms ('funding history', 'investors', 'investment details') but misses common variations users would say like 'funding rounds', 'who funded', 'VCs', or 'Series A/B'.

3 / 5

Distinctiveness Conflict Risk

The company-funding/investor niche is mostly distinct from other skills with only minor overlap risk against general company-research skills; not a 5 because the absence of explicit triggers slightly weakens distinctiveness.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
gooseworks-ai/goose-skills
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.