CtrlK
BlogDocsLog inGet started
Tessl Logo

people-company-search-fiber

People, company, investor, and job search with LinkedIn data enrichment

50

Quality

55%

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 ./skills/lead-generation/capabilities/people-company-search-fiber/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 a well-structured, actionable API reference with runnable curls and a cost table, but it duplicates endpoint summaries, ships a few malformed JSON examples, omits pagination/validation feedback loops for a paid batch API, and inlines the full reference rather than splitting it into bundled files.

Suggestions

Fix the broken JSON in the investor, people, company, and job search curl examples so 'searchParams' is inside the -d payload.

Remove the duplicate 'Capabilities' bullet list (or trim it) since every endpoint is already documented under 'Usage'.

Add a pagination/validation workflow with a checkpoint (e.g., fetch a page, check the returned cursor, fetch the next page) and a note to verify result counts before spending on enrichment.

Move the bulk per-endpoint reference into a bundled reference file and keep SKILL.md as an overview with one-level-deep links.

DimensionReasoningScore

Conciseness

Largely efficient with terse parameter lists and a cost table, but the 'Capabilities' bullet list duplicates every endpoint that is then re-described in full under 'Usage', and line 37 restates the description.

3 / 5

Actionability

Provides copy-paste-ready curl commands with real auth headers and example bodies for all 17 endpoints, but ~4 examples (investor/people/company/job search) have malformed JSON where 'searchParams' falls outside the -d string and would not execute.

4 / 5

Workflow Clarity

A paid, paginated batch API has no explicit pagination feedback loop (fetch -> check cursor -> fetch next) and no validation of search results before enrichment; the rubric caps batch operations without validation at 3.

3 / 5

Progressive Disclosure

No bundle files exist; the entire ~360-line API reference is inlined in SKILL.md with section headers and a 'Discover More' pointer, but bulk reference content that belongs in a separate file is not split out.

3 / 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 clearly names the skill's domain and niche but stops short of listing concrete actions or providing any explicit 'Use when' trigger guidance. It is moderately specific and distinct but lacks the completeness needed for top marks.

Suggestions

Add a concrete 'Use when...' clause naming natural triggers (e.g., 'Use when finding candidates, enriching LinkedIn profiles, validating emails, or researching investors/companies').

Replace generic nouns with concrete actions (e.g., 'Search, enrich, and validate people, companies, investors, and jobs using LinkedIn data').

Include common synonyms and file/identifier triggers users actually say (e.g., 'LinkedIn URL', 'email lookup', 'sales leads').

DimensionReasoningScore

Specificity

Names several domain entities ('People, company, investor, and job search') plus one concrete action ('LinkedIn data enrichment'), but lists nouns rather than multiple specific concrete actions.

3 / 5

Completeness

Has a clear 'what' (search and enrichment across people/company/investor/job) but no 'Use when...' clause; per guidelines a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural keywords a user would say ('people search', 'investor', 'job search', 'LinkedIn') but misses common synonyms and concrete triggers like 'email validation' or 'sales leads'.

3 / 5

Distinctiveness Conflict Risk

Targets a specific niche (LinkedIn data enrichment for people/company/investor/job search) with minor overlap risk against other recruiting/sales/LinkedIn skills.

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.