CtrlK
BlogDocsLog inGet started
Tessl Logo

define-offer

Use when turning supplied product, service, or company evidence into an SDR offer brief before targeting or drafting outreach.

64

Quality

76%

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/define-offer/SKILL.md
SKILL.md
Quality
Evals
Security

Define Offer

Purpose

Define what is being offered without turning assumptions into claims. Keep supplied facts, reasonable inferences, and missing information distinct.

Required inputs

  • Supplied product or service description
  • Intended audience or use case, if supplied
  • Approved proof such as dated customer evidence, metrics, or references
  • Known commercial, delivery, legal, or positioning constraints

If an input is absent, mark it missing. Do not fill it from general knowledge.

Workflow

  1. Extract only explicit offer facts: provider, audience, problem or workflow, capabilities, and delivery form.
  2. List desired or supported outcomes. Label each as Fact, Inference, or Missing and attach the supplied proof when one exists.
  3. Record constraints on audience, positioning, delivery, compliance, or use.
  4. Convert unsupported benefits, ROI, customer results, integrations, certifications, and comparisons into excluded claims.
  5. Produce a concise brief. Treat any outreach language as a draft for human review.

Output format

# Offer brief
## Facts
- [claim] — Evidence: [supplied source]
## Outcomes
- [outcome] — Status: Fact | Inference | Missing — Proof: [source or none]
## Proof
- [approved evidence, or "No proof supplied"]
## Constraints
- [constraint]
## Excluded claims
- [claim that must not be used]
## Missing information
- [unresolved input]

Guardrails

  • Never invent or estimate proof, ROI, results, customers, pricing, integrations, certifications, or implementation details.
  • Do not upgrade an aspiration, hypothesis, or product capability into a verified outcome.
  • Cite only supplied evidence. State No proof supplied when appropriate.
  • Do not browse, send outreach, update systems, or perform other external actions.

Quality check

Confirm that every material statement is traceable to an input, every inference is labeled, every missing item remains unresolved, and excluded claims cannot be mistaken for approved messaging.

Example invocation

Use define-offer on the supplied Northstar Relay fixture. Create a short SDR offer brief and leave reliability, time-saved, revenue, and customer outcomes unresolved because no proof was supplied.

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.