CtrlK
BlogDocsLog inGet started
Tessl Logo

person-lookup

Look up information about a person - work history, social profiles, contact info

54

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 ./skills/lead-generation/capabilities/person-lookup/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 highly actionable with copy-paste-ready curl examples and good section organization for a simple skill. The main weaknesses are a redundant description line and an async polling workflow that lacks an explicit sequenced checklist with validation checkpoints.

Suggestions

Remove the standalone "Find detailed information about a person..." line on line 33, which duplicates the frontmatter description and wastes tokens.

Turn the async search flow into a short numbered sequence with an explicit completion check (e.g. 1. POST to get request_id; 2. Poll GET /person/search?request_id until status=complete; 3. Only then read the results).

Consider collapsing the <details> curl-equivalent block since it duplicates the primary proxy example without adding new capability.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable curl, but the standalone "Find detailed information about a person including work history, education, social profiles, and contact information" line duplicates the frontmatter description, and the curl-equivalent details pad the token budget.

2 / 3

Actionability

Copy-paste-ready curl commands with concrete example queries, real parameters, response fields, and HTTP error codes give fully executable, specific guidance.

3 / 3

Workflow Clarity

The async POST-to-poll-GET flow is described ("Poll with GET ... until status is complete") but is not laid out as a sequenced checklist with explicit completion/validation checkpoints.

2 / 3

Progressive Disclosure

This is a simple, single-purpose skill with no bundle files; the body is organized into clear, well-signaled sections (Cost Warning, Setup, Usage, Parameters, Response, Error Handling, Tips) so progressive disclosure is satisfied.

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 skill's purpose and data types clearly but omits any explicit "Use when" trigger guidance, leaving the what/when pairing incomplete. Adding concrete trigger phrasing would lift completeness and distinctiveness.

Suggestions

Append an explicit "Use when the user asks who someone is, wants their background, or needs contact info" clause to satisfy the when/trigger requirement.

Add natural trigger terms users would actually say, such as "who is [name]", "background", or "find contact info", to improve trigger coverage.

Tighten distinctiveness by framing it around single-individual lookups (e.g. "Use only for a specific individual by name + company") rather than generic person info.

DimensionReasoningScore

Specificity

"Look up information about a person - work history, social profiles, contact info" names the action and lists concrete data types, but stops short of the multiple distinct concrete actions seen in the top anchor.

2 / 3

Completeness

It clearly states what the skill does but has no "Use when..." or equivalent explicit trigger clause, so completeness is capped at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Terms like "work history, social profiles, contact info" are relevant but omit common natural phrasings a user would say (e.g. "who is X", "find someone's background", "get contact details").

2 / 3

Distinctiveness Conflict Risk

The person-lookup niche is fairly specific, but the description lacks distinctive trigger phrasing that would prevent overlap with other research/contact skills.

2 / 3

Total

8

/

12

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.