CtrlK
BlogDocsLog inGet started
Tessl Logo

brief-market-topic

Use when turning a supplied market source, account excerpt, or industry item into an ICP-relevant messaging and research brief.

67

Quality

80%

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

SKILL.md
Quality
Evals
Security

Brief Market Topic

Purpose

Translate a supplied source into supported ICP pains, triggers, objections, hooks, and counter-angles without inflating one account into market demand.

Required inputs

  • Supplied source excerpt
  • Source type, date, citation, and observation window
  • Approved ICP and offer facts
  • Requested audience or account scope

Mark missing inputs explicitly. Limit source claims to what the cited excerpt supports; keep separate ICP and offer context labeled.

Workflow

  1. Record the source type, publication date, citation, excerpt, as-of date, and observation window.
  2. Extract only directly supported claims as Fact. Map each fact to the exact source language.
  3. Compare facts with supplied ICP criteria and offer capabilities. Label this relevance analysis Inference, not source fact.
  4. Derive possible pains, triggers, and objections. Label each Supported, Hypothesis, or Missing with its evidence link.
  5. Draft factual hooks and counter-angles that preserve uncertainty and avoid unsupported superiority or demand claims.
  6. Treat future effects and reply likelihood only as Hypothesis; state what additional evidence would test each one. Do not assign probabilities without supplied data.
  7. State sample and scope limits, especially when evidence comes from one account or excerpt.

Output format

# Market topic brief
## Source basis
- Type/date/citation/window: [values or Missing]
## Supported facts
| Fact | Source support |
## ICP relevance
| Pain or trigger | Status | Evidence/reason |
## Objections and counter-angles
| Possible objection | Status | Factual counter-angle |
## Hooks
- [draft hook — fact and inference identified]
## Hypotheses
- Future effect: [hypothesis; evidence needed]
- Reply likelihood: [hypothesis; evidence needed]
## Evidence limits
- [scope or missing evidence]

Guardrails

  • Do not add facts from other sources when the request limits the brief to one excerpt.
  • Do not turn one account, quote, initiative, reply, or model inference into market demand, consensus, purchase intent, or urgency.
  • Do not invent citations, identities, contactability, credentials, pains, budgets, authority, outcomes, future effects, or response rates.
  • Keep account context distinct from personal knowledge and keep facts, inferences, hypotheses, and missing information explicit.
  • Exclude protected-trait targeting and unnecessary sensitive personal data.
  • Do not browse without authorization, scrape, contact people, mutate systems, or claim future work was scheduled.

Quality check

Confirm every fact maps to the supplied source; ICP relevance, pains, triggers, objections, hooks, counter-angles, future effects, and reply likelihood carry explicit evidence status; source metadata and limits are complete; and no account-specific evidence becomes a market-wide claim.

Example invocation

Use brief-market-topic on the 2026-06-12 Meridian Forge engineering excerpt. Brief its supported ICP relevance, hooks, counter-angles, hypotheses, and evidence limits without importing other account facts.

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.