prospect-brief — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited prospect-brief (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This skill helps a salesperson, BD person, or founder turn a company name or URL into a short, useful prospect brief in under two minutes. The goal is not exhaustive research — it's enough research to write a personalized outreach message that lands.
At minimum, the input required is a company name OR URL, AND an outreach goal. If either is missing, request it from the user once. If the user proceeds without supplying it, work with what's available and note in the Confidence section that output quality is degraded due to missing input.
If the company name is ambiguous (e.g. "Acme" — could be many companies), ask one clarifying question to disambiguate (industry, location, or URL). Do not guess.
This skill uses public web sources via web search and web fetch. It does not pull from paid databases.
A structured brief with five sections, in this exact order. Brevity is the point — a salesperson should be able to read the whole thing in 60 seconds.
Things that have happened in the last ~12 months (relative to today's date) that an outreach message could legitimately reference. Prioritize:
If you cannot find any signals, say so explicitly: "No notable public signals in the last 12 months — recommend escalating to a human researcher or proceeding with a generic intro."
Things you'd actually mention in a first message. These are the bridges between "what I learned" and "what I'd say." Each hook should be:
A single, personalized opening sentence the user can drop into a cold email or LinkedIn message. It needs to sound human — as though the sender spent meaningful time thinking about this company before writing — but stay short and to the point. Reference at least one specific signal or hook by name. Stay under 40 words.
Output the brief as Markdown with the section headers above. Return Markdown, not JSON, unless the user explicitly asks for JSON. The audience is a human salesperson reading on their phone or in a CRM — Markdown renders cleanly in both.
On signal quality: Not every news mention is a signal. A funding round is a signal. A press release about attending a conference is not. When in doubt, ask: "Could a salesperson reference this in a way that sounds like they actually pay attention to this company?" If yes, include it. If no, drop it.
On the draft intro: This is the hardest part and the most valuable. The intro should feel like it was written by someone who spent 20 minutes thinking about the prospect, even though the Skill spent 90 seconds. The point of this line is to prove the sender actually researched the prospect — generic openers like "I hope this finds you well" or "I came across your company" do the opposite, signaling a template and destroying the entire reason for doing the research. The same logic applies to vague praise ("big fan of what you're building") or vague observations ("saw you've been growing"): if the line could be sent unchanged to any company in their industry, it has failed its job. Aim for a sentence that would be embarrassing to send to the wrong prospect.
On confidence: Be honest. If the prospect is a small private company with little public footprint, the confidence is low and you say so. A salesperson would rather know the limits of the brief than discover them after sending a bad intro.
On escalation: If you cannot produce at least one specific signal AND one specific hook, recommend escalation. A bad personalized intro is worse than no intro at all.
This is what a real run of this skill produced when researching TLDR (tldr.tech) for a candidate applying to their Senior SWE, Applied AI role.
Outreach goal: Cover letter for Senior SWE, Applied AI role — hook tied to the "build Claude Skills for non-technical teammates" framing.
(The full brief continues with sections 4 and 5, plus sources. See examples/tldr-prospect-brief.md for the complete output.)
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.