CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deepline-pre-research

Deprecated alias. This skill was renamed to `deepline-research`. Use when a user or script still invokes `/deepline-pre-research`: immediately load and follow the `deepline-research` skill instead. Triggers: pre-research, source discovery, provider strategy, research data sources, ScrapeCreators, X/Twitter data, Reddit comments, public and private datasets, CRM data, workflow data, custom language, messaging language, pain language.

Quality

77%

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/deepline-pre-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A short, well-structured redirect stub whose core instruction — load and follow `deepline-research`, with an executable fallback search and a one-line user notice — is clear and actionable. Its main flaws are the orphaned npm-install Quick Start block and the undated removal note, which add tokens and ambiguity without serving the redirect task.

Suggestions

Remove the "Quick Start" npm-install block (or move it into the `deepline-research` skill it belongs to); it is dead weight in a file that explicitly contains no instructions of its own.

Replace "It will be removed" with a concrete deprecation date or version milestone, or drop the sentence entirely.

Add a one-line fallback for the case where none of the candidate roots exists (e.g. report to the user that `deepline-research` could not be located) so the executable loop has a defined terminal state.

DimensionReasoningScore

Conciseness

The redirect core is lean, but the "Quick Start" block ("npm install -g deepline" / "deepline -h") serves no stated purpose in a file that says "it contains no instructions of its own", and "It will be removed" is undated time-sensitive information. This is more than a minor trim (not a 4), but the rest of the body is tight and unpadded (not a 2).

3 / 5

Actionability

The fallback bash loop with explicit candidate roots ($PWD/.skills, $HOME/.claude/skills, $HOME/.agents/skills) is executable and copy-paste ready, and "tell the user once, in a single line" is precise. Not a 5 because no guidance covers the case where none of the candidate paths exists, and the loader-based invocation ("If the skill loader supports names, invoke `deepline-research`") is left unspecified.

4 / 5

Workflow Clarity

The redirect sequence is clear and ordered — load `deepline-research` (by name, else try roots "in order and using the first that exists"), notify the user once, then continue with the request. Not a 5 for a simple skill because the unexplained Quick Start block precedes the workflow, leaving ambiguity over whether CLI installation is a prerequisite step; not a 3 because the redirect sequence itself is complete and unambiguous.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files, has well-organized sections, and correctly delegates all actual content to the `deepline-research` skill instead of inlining or duplicating it — exactly the right disclosure behavior for a stub.

5 / 5

Total

16

/

20

Passed

Description

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

A well-formed deprecated-alias description: it is explicit about both what it does (redirect to `deepline-research`) and when to use it (when the old name is invoked, backed by a concrete trigger list). The main weaknesses are a single-action specificity ceiling inherent to a stub, and a trigger tail with broad terms that invite overlap with other data/research skills.

Suggestions

Trim broad trigger terms like "CRM data", "workflow data", and "public and private datasets" (or qualify them with the deepline context, e.g. "deepline research data sources") so the alias does not fire on generic data-analysis requests.

Replace jargon-y trigger phrases such as "custom language, messaging language, pain language" with the natural phrases a user would actually say when they need this skill.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action — "immediately load and follow the `deepline-research` skill instead" — but offers no broader list of actions, matching the 'names domain and 1-2 concrete actions' anchor. It is not a 2 because the redirect action is concrete rather than generic, and not a 4 because there are not several specific actions.

3 / 5

Completeness

It explicitly answers both: what ("Deprecated alias. This skill was renamed to `deepline-research`… immediately load and follow the `deepline-research` skill instead") and when ("Use when a user or script still invokes `/deepline-pre-research`" plus a concrete trigger list). Not a 4 because the 'when' is fully explicit with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

The trigger list ("source discovery", "X/Twitter data", "Reddit comments", "public and private datasets", "CRM data") provides good natural keyword coverage, but includes jargon-y entries ("provider strategy", "pain language") and misses common synonyms. Not a 5 because coverage is not comprehensive with synonyms; not a 3 because the list goes well beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The namespaced trigger "/deepline-pre-research" is highly distinct, but broad tail terms like "public and private datasets", "CRM data", "workflow data", and "custom language, messaging language, pain language" could pull in generic data-gathering or research requests, overlapping with similar skills. Not a 4 because the overlap risk is more than minor; not a 2 because the skill has a clear niche as an alias to one specific named skill.

3 / 5

Total

15

/

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.

Validation — 15 / 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

getaero-io/gtm-eng-skills

Path

skills/deepline-pre-research/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.