CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

linkedin-url-lookup

Retired. LinkedIn URL lookup is part of `deepline-gtm`. Kept only so installed CLIs that still list this skill keep syncing.

Quality

74%

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

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

For a retired tombstone skill, the body is close to ideal: lean, honest about its status, and actionable in pointing readers to the successor. The main weakness is the unexplained duality between installing the deepline CLI and loading the deepline-gtm skill.

Suggestions

Clarify the relationship between the two pointers — e.g. 'The `deepline-gtm` skill uses the deepline CLI; install it with `npm install -g deepline`' — so the reader knows whether to run the CLI or load the skill.

Replace the 'Quick Start' heading with something reflecting the skill's actual state (e.g. '## Status' or '## Redirect'), since a retired skill has no quick start.

DimensionReasoningScore

Conciseness

The body is 18 lines with zero concept explanations or padding: a two-command bash block and a two-sentence status/redirect note, where every token earns its place. It is leaner than the anchor-4 example, which still allows minor trims — nothing here is trimmable without losing function.

5 / 5

Actionability

The bash block ('npm install -g deepline', 'deepline -h') is copy-paste ready and 'Load and follow the `deepline-gtm` skill instead' is a concrete next step. Falls short of 5 because the two redirect targets (the deepline npm CLI and the deepline-gtm skill) are presented without any stated relationship, leaving the reader unsure which path to take.

4 / 5

Workflow Clarity

As a single-purpose redirect stub, the single action is mostly unambiguous ('Load and follow the `deepline-gtm` skill instead'), which under the simple-skill exception could reach 5; the unexplained dual CLI/skill pointers introduce slight ambiguity, dropping it to 4. No destructive or batch operations, so no validation cap applies.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no content that warrants separate references; the cross-reference to `deepline-gtm` is clear and one level deep. Falls short of 5 because the sole heading 'Quick Start' is a slight misnomer for a retired stub, leaving the organization adequate but not exemplary.

4 / 5

Total

17

/

20

Passed

Description

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

This is a retirement/tombstone description, and it does that job cleanly: honest, specific, and unambiguous about the skill's status and its successor. Judged as a normal skill description it is inherently limited — no capabilities, no trigger guidance, no 'use when' routing to the successor.

Suggestions

Add explicit trigger routing, e.g. 'If the user asks for LinkedIn URL lookup, load the `deepline-gtm` skill instead' — this would lift completeness and trigger-term quality while keeping the retired status.

Briefly state what the retired functionality did (e.g. 'looked up LinkedIn profile URLs') so readers who never saw the original skill understand what moved to `deepline-gtm`.

Include a few natural trigger phrases ('LinkedIn profile URL', 'find someone on LinkedIn') so the retirement notice still matches what users actually say.

DimensionReasoningScore

Specificity

The description names the domain ('LinkedIn URL lookup') and its successor ('deepline-gtm') but lists no capability actions whatsoever, matching the anchor 'names the domain but actions are minimal or generic'. It is not score 1 because nothing is vague — the retirement status and relocation are stated precisely.

2 / 5

Completeness

It clearly answers 'what' — 'Retired', 'Kept only so installed CLIs that still list this skill keep syncing' — but contains no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'LinkedIn URL lookup' is the natural phrase a user would say, but coverage stops there — no synonyms, variations, or related phrasing, fitting 'some relevant keywords but missing common variations'. Not 4 because keyword coverage is a single phrase.

3 / 5

Distinctiveness Conflict Risk

'LinkedIn URL lookup is part of `deepline-gtm`' carves out a clear niche with a named successor and an explicit do-not-use signal, giving minimal conflict risk with other skills. Not 4 because there is no realistic overlap scenario with another skill.

5 / 5

Total

13

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

getaero-io/gtm-eng-skills

Path

skills/linkedin-url-lookup/SKILL.md

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.