find-qualified-titles

Use when finding real role-holders at known company domains from an ICP, especially prompts like 'find all job titles at these companies', 'find qualified titles', 'find RevOps or marketing-ops buyers', or when exact title discovery should precede paid people search.

Quality

58%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/find-qualified-titles/SKILL.md

Quality

Content

27%

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

This skill is essentially a thin routing layer that delegates all actual work to a meta-skill and a recipe file, providing no standalone actionable content. Without the referenced files available in the bundle, the skill is nearly useless on its own. It lacks concrete guidance, executable examples, and validation steps for what should be a multi-step discovery workflow.

Suggestions

Include at minimum a summary of the find-qualified-titles workflow steps inline so the skill has standalone value even without the referenced files.

Add concrete, actionable guidance: what tools to use, what inputs are expected (e.g., company domains, ICP criteria), and what outputs to produce.

Provide the referenced bundle files (deepline-gtm skill, recipe file) or inline the critical content so the skill is self-contained enough to be useful.

Add validation checkpoints for the title discovery workflow (e.g., verify domain validity, confirm title matches against ICP before proceeding to paid people search).

Dimension	Reasoning	Score
Conciseness	The content is relatively short but includes some unnecessary explanation (e.g., 'This is a recipe shortcut' and the final sentence restating what was already clear). The repeated emphasis on the meta-skill governing the session is slightly redundant.	2 / 3
Actionability	The skill provides no concrete code, commands, or executable guidance. It is entirely a delegation/routing instruction that tells Claude to invoke another skill and read another file, with no actual steps for accomplishing the task of finding qualified titles.	1 / 3
Workflow Clarity	There is a numbered sequence of three steps, but they are essentially 'go read other documents' rather than substantive workflow steps. There are no validation checkpoints, no error handling, and no concrete actions within this skill itself.	2 / 3
Progressive Disclosure	The skill is almost entirely a pointer to other files (deepline-gtm meta-skill and a recipe file), but no bundle files are provided, making it impossible to verify the references. The skill itself contains virtually no standalone content, functioning as a redirect with no clear navigation structure.	1 / 3
	Total	6 / 12 Passed

Description

89%

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 excels at trigger term coverage and completeness, with a clear 'Use when' clause and multiple natural phrasings users would employ. Its main weakness is that it focuses heavily on when to use the skill without explicitly listing the concrete actions/capabilities the skill performs (e.g., scraping, querying, outputting formatted lists). The niche is well-defined and distinctive.

Suggestions

Add explicit capability statements before the 'Use when' clause, e.g., 'Discovers and lists real job titles and role-holders at specified company domains by analyzing public sources. Outputs qualified title matches from an ICP.'

Dimension	Reasoning	Score
Specificity	The description mentions 'finding real role-holders at known company domains from an ICP' and references 'exact title discovery' preceding 'paid people search', but it doesn't list concrete actions (e.g., scrape LinkedIn, query databases, generate contact lists). The actions are implied rather than explicitly enumerated.	2 / 3
Completeness	The description opens with an explicit 'Use when' clause that clearly answers when to use the skill, and the trigger phrases implicitly convey what the skill does (finding role-holders/titles at companies). Both what and when are addressed with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would actually say: 'find all job titles at these companies', 'find qualified titles', 'find RevOps or marketing-ops buyers', 'ICP', 'company domains', 'people search'. These cover multiple realistic phrasings a user might employ.	3 / 3
Distinctiveness Conflict Risk	The description carves out a clear niche: finding role-holders at known company domains from an ICP, with title discovery preceding paid people search. This is highly specific to a sales/prospecting workflow and unlikely to conflict with general search or contact management skills.	3 / 3
	Total	11 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: getaero-io/gtm-eng-skills
Commit: 449bc08

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.