contact-cache

Track all identified/contacted people across strategies. CSV-backed contact database with dedup by LinkedIn URL or email. Prevents duplicate outreach when running strategies on a recurring cadence.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/lead-generation/capabilities/contact-cache/SKILL.md

Quality

Content

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

The body is highly actionable and well-structured for a simple skill, with copy-paste commands and a clean bundled-script layout. The main gap is the absence of explicit validation/verification steps around the batch CSV import and export operations.

Suggestions

Add a validation step after bulk import, e.g. run `check` on the imported identifiers or print a dedup/added/skipped summary to confirm results before proceeding.

Drop the duplicated opening paragraph (it repeats the frontmatter description) to recover tokens.

Show a quick verification after `update` (e.g. re-run `check` or `export --status contacted`) so users can confirm a status change landed.

Dimension	Reasoning	Score
Conciseness	The body is lean with concrete commands and no concept over-explanation; the only redundancy is the frontmatter description being repeated verbatim as the opening paragraph, a minor trim opportunity keeping it just below 5.	4 / 5
Actionability	Copy-paste ready CLI commands cover all common cases — check, single add, bulk CSV import, update, export (csv/json/by status/by strategy), and stats — fully executable with concrete flags.	5 / 5
Workflow Clarity	Operations are clearly listed, but bulk import (add --csv) and export are batch operations with no explicit validation or verification checkpoint shown in the body, so workflow clarity is capped at 3 per the batch-operations rule.	3 / 5
Progressive Disclosure	A simple under-50-line skill with well-organized sections (Usage, Data, Valid Statuses) and a bundled script (scripts/cache.py) referenced via concrete commands; no nested or buried references, so it qualifies for the simple-skill 5.	5 / 5
	Total	17 / 20 Passed

Description

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

The description is specific and third-person with a clear niche, but lacks an explicit 'Use when' trigger clause and a few natural synonyms users might say. Capping completeness at 3 reflects the missing trigger guidance.

Suggestions

Add an explicit trigger clause, e.g. 'Use when running lead-generation strategies on a recurring cadence to avoid contacting the same person twice.'

Include natural synonyms users might say — 'leads', 'outreach list', 'CRM' — alongside 'contacts'.

Tighten 'Track all identified/contacted people across strategies' to lead with the core action (dedup + prevent duplicate outreach) for sharper distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'Track all identified/contacted people', 'CSV-backed contact database with dedup by LinkedIn URL or email', 'Prevents duplicate outreach' — but coverage is not fully comprehensive, so it sits above the 3-anchor and below 5.	4 / 5
Completeness	The 'what' is clear, but there is no explicit 'Use when...' trigger clause; the only 'when' signal ('when running strategies on a recurring cadence') is weakly implied context rather than trigger guidance, so completeness is capped at 3 per the guidelines.	3 / 5
Trigger Term Quality	Relevant domain terms like 'contact database', 'dedup', 'LinkedIn URL', 'email', and 'duplicate outreach' are present, but common user synonyms such as 'leads', 'CRM', or 'outreach tracking' are missing.	3 / 5
Distinctiveness Conflict Risk	The contact-cache/dedup niche is fairly distinct with low conflict risk, though the broad lead-generation framing leaves minor overlap with related outreach skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/lead-generation/capabilities/contact-cache/SKILL.md
Commit: 2523432

Reviewed: 7 days 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.