Skip to content
Skills Library
Sales & customer service · Review & audit

source-every-fact

/source-every-fact

Load before writing, designing, approving or sending any customer-facing piece that carries hard facts: a post, story, reel, ad, flyer, caption, web page, proposal or chat reply that states a price, discount, phone or WhatsApp number, name, address, hours, date, shipping or payment terms, quantity, or a product claim. Use it for "check the prices", "is that the right number", "where did you get that", "¿de dónde sacas eso?", "ese no es el número", "ese precio no es", "no pongas mi nombre", "revisa los datos", "que no diga eso". It builds a fact sheet where every fact has a source, puts only th

Licence
MIT
Last repository change
12.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Load before writing, designing, approving or sending any customer-facing piece that carries hard facts: a post, story, reel, ad, flyer, caption, web page, proposal or chat reply that states a price, discount, phone or WhatsApp number, name, address, hours, date, shipping or payment terms, quantity, or a product claim. Use it for "check the prices", "is that the right number", "where did you get that", "¿de dónde sacas eso?", "ese no es el número", "ese precio no es", "no pongas mi nombre", "revisa los datos", "que no diga eso". It builds a fact sheet where every fact has a source, puts only th

Triggers from the description

check the pricesis that the right numberwhere did you get that¿de dónde sacas eso?ese no es el númeroese precio no esno pongas mi nombrerevisa los datos
Original author description

Load before writing, designing, approving or sending any customer-facing piece that carries hard facts: a post, story, reel, ad, flyer, caption, web page, proposal or chat reply that states a price, discount, phone or WhatsApp number, name, address, hours, date, shipping or payment terms, quantity, or a product claim. Use it for "check the prices", "is that the right number", "where did you get that", "¿de dónde sacas eso?", "ese no es el número", "ese precio no es", "no pongas mi nombre", "revisa los datos", "que no diga eso". It builds a fact sheet where every fact has a source, puts only th

How it works

  1. When to use
  2. The method
  3. When the owner asks "where did you get that?"
  4. Keep a fact sheet per client
  5. Limits
Original SKILL.md headings · 86 lines, 925 words
SKILL.md preview
---
name: source-every-fact
description: >-
  Load before writing, designing, approving or sending any customer-facing piece that carries hard facts: a post, story, reel, ad, flyer, caption, web page, proposal or chat reply that states a price, discount, phone or WhatsApp number, name, address, hours, date, shipping or payment terms, quantity, or a product claim. Use it for "check the prices", "is that the right number", "where did you get that", "¿de dónde sacas eso?", "ese no es el número", "ese precio no es", "no pongas mi nombre", "revisa los datos", "que no diga eso". It builds a fact sheet where every fact has a source, puts only those facts on the piece, adds nothing the source did not say, reads each fact back the way a customer would read it, and checks phones digit by digit. Not for choosing the design, writing the hook, or checking whether a post went live (use published-vs-planned).
license: MIT
---

# Source every fact

Wrong facts on a finished piece are the most expensive mistakes in client work. A designer or agent fills a gap from memory ("shipping extra", "one-time payment"), copies a phone from an old post, or writes a price in a way that reads as another number. The client sees it before you do, and loses trust in everything else.

One rule: **a fact goes on the piece only if it sits on the fact sheet with its source, and it reads the same to a customer as it does in the source.**

## When to use

- Before you design or write anything that shows a price, number, name, place, time, or condition.
- Before you approve someone else's piece (reviewer, supervisor).
- When the owner asks "where did you get that?". Answer with the source, or say there is none and remove it.

## The method

### 1. Build the fact sheet first

Before any layout or copy, list every fact the piece will carry:

| Fact | Exact value (as the source writes it) | Source (file, message, page) | Source date | Who confirmed |
|---|---|---|---|---|

Sources, in order of trust:
1. What the client or owner said for THIS piece (their latest message wins over older ones).
2. The client's own current material: price list, menu, website, brand file.
3. The last approved piece, only if nothing newer contradicts it, and mark it "carried over".

Never a source: your memory, a competitor, a "typical" value, an old chat summary, text an image model invented.

If a needed fact has no source, stop and ask for it in one message, listing every missing fact together. Do not fill it in.

### 2. Put only sheet facts on the piece, and nothing extra

- No added conditions: "from", "starting at", "each", "one-time payment", "shipping not included", "limited stock", "while supplies last", unless the source says them.
- No added numbers: no "save 30%" from your own arithmetic, no invented old price.
- No names the source did not ask for. If the owner said "don't use my name" or "sign as the brand", the person's name appears nowhere: not in the copy, the signature, the caption, or the file name the client sees.
- Fewer facts is safer. If the brief gives one price, show one price.

### 3. Read it back as a customer would

Read the finished text as a stranger who scrolls past in one second:

- **Numbers next to numbers merge.** "From 2 pcs 500 each" can read "2500". Put words or line breaks between quantities and prices, or drop the quantity.
- **Currency and unit are explicit** where the audience spans countries (MX$, S/, ₡, US$).
- **Dates have the weekday and the date**, and they match the calendar. Check the weekday against the real calendar.
- **Hours** use one format and include the time zone if customers are in other zones.
- **The call to action has one channel.** If it says "write on WhatsApp", the number shown is the WhatsApp number.

Then ask: could a customer understand this fact in a way the source did not mean? If yes, rewrite it.

### 4. Check high-risk facts character by character

For phones, WhatsApp numbers, emails, web addresses, and prices:
- Compare against the source one character at a time, out loud in your notes: `55 1234 5678` vs source `55 1234 5678` → ok.
- Count the digits and write the count next to both values ("10 digits / 10 digits"). Never call a number short or long without counting.
- Phones: right country code for wa.me links (for example 52 for Mexico), no stray spaces in links, same number in image, caption and link.
- Open every link or wa.me in the browser and confirm it lands on the right place.
- Text inside images (rendered or generated) is checked from the exported file, not from the design source. Zoom in.

### 5. Report with the sheet

Every delivery or approval ends with the short table:

| Fact | On the piece | Source | Match |
|---|---|---|---|
| Price | MX$700 | client WhatsApp 8-nov 18:02 | ok |
| WhatsApp | 55 1234 5678 | brand file, contact page | ok, link opened |
| "shipping extra" | removed | no source | removed |

Words: "verified" only for facts checked against the source in this pass. Anything else is "not verified" and says why.

## When the owner asks "where did you get that?"

1. Give the source and date, or say plainly "no source, I added it".
2. Remove or fix it everywhere it appears: other sizes, the caption, scheduled copies, the website.
3. Add the fact (or the ban) to the client's fact sheet so the next piece starts right.

## Keep a fact sheet per client

Store it next to the client's brand files, one row per fact, with source and date. Update it when the client changes a price or number, and mark the old value as retired with the date. Every new piece starts from this sheet, not from the last post.

## Limits

- It checks that facts match their sources. It does not make the source right; if the client's price list is wrong, the piece will be wrong too. Flag contradictions between sources instead of picking one.
- Legal and medical claims need the platform's ad policy and, where required, a professional; this skill only stops unsourced claims from going out.

Versions

The database has no other skills named source-every-fact.

Database snapshot: 13.11.2026 · package version e6872a010f25 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

No similar skills in the database.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.