Use when turning a supplied market source, account excerpt, or industry item into an ICP-relevant messaging and research brief.
67
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Translate a supplied source into supported ICP pains, triggers, objections, hooks, and counter-angles without inflating one account into market demand.
Mark missing inputs explicitly. Limit source claims to what the cited excerpt supports; keep separate ICP and offer context labeled.
Fact. Map each fact to the exact source language.Inference, not source fact.Supported, Hypothesis, or Missing with its evidence link.Hypothesis; state what additional evidence would test each one. Do not assign probabilities without supplied data.# 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]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.
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.
56ebfd3
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.