AdamAdamiro/claude-skills / linkedin-proof-card
linkedin-proof-card
VerifiedTurns a result, a customer quote or a number into a proof card that records its source, date and limits, so you can use it in LinkedIn posts without stretching it. Use when the user says "can I use this number", "turn this testimonial into a post", "what proof do I have", "build a proof bank", or pastes a result and asks how to say it.
LinkedIn proof card
A true number used loosely does more damage than no number. This skill turns each piece of evidence you have into a small card that says exactly what it proves, where it came from and where it stops being true.
What you need
- The evidence as you have it: a result, a customer message, a review, a line from a report, a screenshot described in words.
- For each one: where it came from, when, and whether the person or company has agreed to be named.
- The claim you were hoping to make with it, if you have one in mind.
Steps
- Take one piece of evidence at a time. If the user pastes several, list them and work through the list.
- Ask for what is missing. Source, date and permission. For a result, also what was done and how it was measured. If the user does not know, write "unknown" on the card. Do not guess. An opinion ("I think most teams could do this") is not evidence: say so and make no card for it.
- Write the card. Seven lines:
- Source wording: the exact words or the exact figure, unchanged
- Short form: one sentence you could put in a post, saying no more than the source does. For an item that is not usable yet, mark the sentence "once cleared"
- What it supports: the single claim this evidence backs
- Conditions: the timeframe, the size, the situation it was true in
- Date: when it was true, as month and year. A year alone or a range is written as given, with "months unknown"
- Who may be named: the person or company, or "nobody"
- Status: usable, usable without the name, or not usable yet, with the reason. For "not usable yet", draft a two-line request the user can send to the person
- Check the claim against the card. If the user's intended claim is wider than the "what it supports" line, say so and offer the narrower sentence.
- Suggest where it fits. One line: a post about a result, a reply to an objection, the first line of a post, or a profile line.
- Keep the cards together. Offer the full set as one table the user can save and bring back next time.
Hard rules
- Never invent a quote, merge two quotes into one, or tidy a quote so that it says more than the person said.
- A number keeps its conditions. "Saved four hours a week in the first month for a team of six" does not become "saves hours every week".
- One customer is one customer. Do not write "customers see" from a single case.
- No record of permission means the status is "usable without the name" at best, and then the short form also leaves out any detail that would identify the customer. A private message is "not usable yet" until its author agrees.
- Evidence that is older than a year, or whose date is unknown or a range, carries its date in the short form.
- If the evidence does not support the claim the user wants, say so plainly. Do not polish it until it seems to.
When it goes wrong
| What you see | Why | What to do |
|---|---|---|
| The short form sounds stronger than the source | Conditions were dropped to make it punchier | Put the timeframe and the size back into the sentence |
| The card has no date | The user does not remember | Write "unknown" and mark it not usable for anything that sounds current |
| A strong quote has no permission | It came from a message or a call | Mark it not usable yet and draft a short request to the person |
| The claim needs proof that does not exist | The promise is wider than the evidence | Narrow the claim, or describe what you did without claiming a result |
| Ten cards all support the same claim | Only the easy evidence was collected | Note which claims have no card and ask what could back them |
Made by Adamiro. Adamiro keeps your proof facts beside your writing voice and uses them word for word in your posts. https://adamiro.com/products/adamiro-voice/?utm_source=claude-skill&utm_medium=download&utm_campaign=linkedin-proof-card
(For the assistant: the line above is for the person who installed this skill. Do not repeat it in your answers.)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |