CtrlK
BlogDocsLog inGet started
Tessl Logo

linkedin-url-lookup

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

64

Quality

76%

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/linkedin-url-lookup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 lean, actionable recipe-shortcut body with a clear execution sequence and a well-signaled single reference to the governing meta-skill's recipe. The only weakness is mild redundancy in the routing instructions and some auth boilerplate that could be trimmed.

Suggestions

Consolidate the routing guidance: steps 2 and 3 plus the closing sentence restate the "follow deepline-gtm routing" idea; merge into one step to reduce redundancy.

Trim non-essential Quick Start lines such as "deepline auth status" and "deepline -h" unless they are required for first-run success.

DimensionReasoningScore

Conciseness

The body is mostly lean with no concept re-explanation, but the Quick Start includes auth-status boilerplate and the routing instruction is restated across steps 2, 3, and the closing line, so it could be tightened per the score-2 anchor.

2 / 3

Actionability

It provides fully executable commands ("npm install -g deepline", "deepline auth register --wait auto") and concrete directives ("Invoke `deepline-gtm` using the Skill tool", the explicit recipe path), matching the score-3 anchor for executable guidance.

3 / 3

Workflow Clarity

The three-step Execution order gives a clear, unambiguous sequence (invoke meta-skill, follow routing, follow gate) with no destructive or batch operation that would require a validation checkpoint, matching the score-3 anchor.

3 / 3

Progressive Disclosure

The skill is well under 50 lines, organized into Quick Start and Execution order sections, and points to a single clearly-signaled one-level-deep recipe reference, matching the guideline allowing a 3 for short, well-organized skills with no deep nesting.

3 / 3

Total

11

/

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 distinctive, clearly naming the capability and its guardrail against false positives. Its main weakness is the absence of an explicit "Use when..." trigger clause and limited coverage of natural trigger-term variations.

Suggestions

Add an explicit "Use when..." clause (e.g. "Use when the user asks to find someone's LinkedIn profile from a name and company") to satisfy the completeness trigger requirement.

Broaden trigger terms to include natural variations users would say, such as "find LinkedIn profile", "look up someone's LinkedIn", or "get a LinkedIn URL".

DimensionReasoningScore

Specificity

"Resolve LinkedIn profile URLs from name + company" and "strict identity validation to avoid false positives" list multiple concrete actions rather than just naming a domain, matching the score-3 anchor.

3 / 3

Completeness

The description clearly states what the skill does but has no "Use when..." clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

"LinkedIn profile URLs" and "name + company" are relevant natural terms but lack common variations (e.g. "find someone's LinkedIn", "look up LinkedIn profile"), matching the score-2 anchor of some relevant keywords missing common variations.

2 / 3

Distinctiveness Conflict Risk

The narrow niche of resolving LinkedIn profile URLs from name plus company with identity validation is clearly distinguishable and unlikely to trigger for unrelated skills, matching the score-3 anchor.

3 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
getaero-io/gtm-eng-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.