linkedin-url-lookup

Resolve LinkedIn profile URLs from name + company with strict identity validation to avoid false positives.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

The skill is concise and well-sequenced but delegates its core executable workflow and validation steps to an external recipe file that is absent from the bundle, weakening actionability, workflow clarity, and progressive disclosure.

Suggestions

Ensure the referenced recipe file ../deepline-gtm/recipes/linkedin-url-lookup.md exists in the bundle, or inline the minimal lookup workflow so the skill is self-contained and executable.

Add an explicit identity-validation/verification checkpoint in the body (e.g., how to confirm the resolved URL matches the target person before returning it) rather than deferring all validation to the recipe.

If the deepline-gtm meta-skill is a hard dependency, document its presence/availability so the cross-skill reference resolves for users of this skill.

Dimension	Reasoning	Score
Conciseness	The body is a lean ~25 lines with concrete install commands and numbered delegation steps, no padding or re-explanation of concepts Claude knows, matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	Quick Start provides concrete executable shell commands and Execution order is specific, but the actual lookup workflow is delegated to a recipe file (../deepline-gtm/recipes/linkedin-url-lookup.md) that does not exist in the bundle, leaving the task's executable substance missing.	2 / 3
Workflow Clarity	A clear numbered sequence exists, but this identity-validation task has no validation/verification checkpoints or error-recovery feedback loops in the body itself (they are deferred to the missing recipe), which caps workflow clarity at 2 per the fragile-operation guideline.	2 / 3
Progressive Disclosure	The body is organized with a clearly signaled one-level reference to a recipe file, but that referenced file does not exist in the bundle and there are no references/scripts/assets directories, so the signaled navigation does not actually resolve.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 specific and distinct but lacks an explicit use-trigger clause and only partially covers the natural terms a user would say. Completeness is capped at 2 per the missing-'Use when' guideline.

Suggestions

Add an explicit trigger clause, e.g. "Use when you need to find a person's LinkedIn profile from their name and company."

Broaden natural trigger terms to include common phrasings like "find LinkedIn", "look up LinkedIn profile", or "LinkedIn profile from name and company".

Dimension	Reasoning	Score
Specificity	"Resolve LinkedIn profile URLs from name + company with strict identity validation to avoid false positives" names the domain, inputs, and a concrete guarded action, matching the 'lists multiple specific concrete actions' anchor rather than the partial-coverage anchor 2.	3 / 3
Completeness	The description clearly states what the skill does, but there is no "Use when..." clause or equivalent explicit trigger; the 'when' is only implied, which the guidelines say caps completeness at 2.	2 / 3
Trigger Term Quality	"LinkedIn profile URLs" and "name + company" are relevant natural terms, but common phrasings a user would say ("find LinkedIn", "look up LinkedIn", "LinkedIn profile") are missing, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The narrow LinkedIn-URL-from-name-and-company niche with explicit identity-validation framing is a clear, distinct trigger unlikely to overlap with other skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 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: getaero-io/gtm-eng-skills
Commit: 25492ee

Reviewed: 1 day 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.