CtrlK
BlogDocsLog inGet started
Tessl Logo

build-dossier

Use when assembling a concise evidence-backed account and contact brief from supplied records and dated research.

63

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/build-dossier/SKILL.md
SKILL.md
Quality
Evals
Security

Build Dossier

Purpose

Create a concise account dossier whose material claims map to supplied evidence. Surface unknowns instead of filling common sales-research fields with assumptions.

Required inputs

  • Supplied account record and stable ID
  • Supplied contact records and verification state
  • Dated evidence excerpts with source type and citation
  • Requested scope, observation window, and as-of date
  • Relevant ICP and offer facts, if comparison is requested

Mark absent inputs as Missing. Do not import records outside the requested scope.

Workflow

  1. State scope, as-of date, observation window, and included records.
  2. Extract account facts and map each to source type, date, citation or supplied record location, and verification status.
  3. List only supplied contacts. Record current-employer and role verification independently with their evidence and date.
  4. Summarize dated events as exact observations. Separate Fact, Inference, and Missing.
  5. Describe offer relevance only as a supported comparison or labeled hypothesis; do not infer intent, priority, urgency, or authority.
  6. Add an explicit unknowns section. Omit unsupported revenue, technology stack, vendors, initiatives, priorities, budget, buying committee, procurement, and timing from factual summaries.
  7. Finish with evidence limits and safe next research questions, not external actions.

Output format

# Account dossier
- Account / as of / window: [values or Missing]
## Account facts
| Claim | Status | Evidence | Source type | Date | Citation/location |
## Contacts
| Identity | Employer check | Role check | Evidence/date | Eligibility |
## Recent evidence
| Observation | Date | Citation | Limit |
## Relevance
- [Fact or Inference]: [traceable statement]
## Unknowns
- [unsupported field]
## Evidence limits
- [scope or freshness limit]

Guardrails

  • Do not invent or infer revenue, funding, technology, vendors, priorities, budget, authority, buying committee, contactability, credentials, intent, urgency, or outcomes.
  • Do not treat an email domain as current-employer verification.
  • Do not add identities, records, replies, or sources outside the requested input scope.
  • Keep facts, inferences, and missing information explicit.
  • Require source type, date, citation or supplied location, and observation window for researched claims.
  • Preserve opt-outs, eligibility decisions, and hard disqualifiers.
  • Exclude protected-trait targeting and unnecessary sensitive personal data.
  • Do not browse without authorization, scrape, contact people, mutate systems, or take external action.

Quality check

Confirm the dossier is concise; every material claim is traceable and dated where available; employer and role verification are explicit; hypotheses and unknowns are separate; unsupported standard fields are absent from facts; and only requested records are used.

Example invocation

Use build-dossier on Meridian Forge Software, Avery Lin, and the 2026-06-12 engineering excerpt. Cite every material fact and leave unsupported company details unknown.

Repository
llaskin/AI-SDR-Skill-Pack
Last updated
First committed

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.