AdamAdamiro/claude-skills / linkedin-right-to-say-it
linkedin-right-to-say-it
VerifiedChecks a LinkedIn draft sentence by sentence for what you saw first-hand, what you heard from someone else and what is opinion, then fixes the sentences you could not defend. Use when the user says "check this post", "does this sound credible", "is this too much", "review my LinkedIn draft", or shares a draft full of general claims.
LinkedIn right to say it
Readers can tell when a post repeats something its author has only read. This skill goes through your draft one sentence at a time, marks what you have the standing to say, and repairs the rest.
What you need
- The draft.
- Two lines about you: what you do, and for how long.
- For any result or story in the draft: were you there, did someone tell you, or did you read it?
Steps
- Split the draft into sentences and number them.
- Mark each one.
- Seen: the author did it, built it, measured it or watched it happen
- Heard: a customer, a colleague or a source told them
- Opinion: a judgement or a prediction
- General: a claim about how the world is, with no source ("most teams", "everyone knows", "studies show") If you cannot tell which it is, ask. Do not assume "seen". If the author is not there to answer, mark the sentence "unconfirmed" and leave it unchanged. A general claim that is really the author's own view is an opinion: ask which it is.
- Show the marked list and count each kind.
- Repair.
- Seen: keep it. If it is vague, ask for the detail that proves the author was there: a date, a number, what was said.
- Heard: say who it came from, in the author's words ("a customer in logistics told me"). If they cannot say who, cut it.
- Opinion: let it stand as one. "I think" or "my bet is" is stronger than a judgement dressed as a fact. An opinion that generalises from one case says so ("going by one client").
- General: ask for the source. With a source, name it. Without one, cut the sentence or turn it into what the author has seen ("in the teams I have worked with", with the real count if the author gives one).
- Check the balance. A post where more than half the sentences are general claims and opinion gives the reader little the author saw. Ask for one thing the author did or saw on this subject, and rebuild the post around it.
- Return the repaired draft with a short list of what changed and why.
Hard rules
- Never supply an experience, a customer, a number or a quote the author did not report. If the post needs one and the author has none, say so.
- Do not raise the author's authority. Three years in a field is three years.
- "Studies show", "research says" and "experts agree" need a named source, or they go.
- Keep limits and doubts the author states. "This worked for us, with a team of five" is more credible than the same line without its ending.
- Do not flatten the author's voice while repairing. Change the fewest words that fix the problem.
- If all but one or two sentences are marked seen, say the draft is sound and stop.
When it goes wrong
| What you see | Why | What to do |
|---|---|---|
| The repaired post is much shorter | Most of the draft was general claims | Ask for one more thing the author saw first-hand and build on it |
| Every sentence is marked opinion | The author has views on this but no experience yet | Suggest writing it as a question they are working on, or choosing another subject |
| The author says "everyone knows this" | It may be true and still unsourced | Keep it only as the view the author is arguing with, not as a fact |
| "Seen" sentences have no detail | The memory is real and the wording is generic | Ask what day, how many, who said what |
| The post now hedges every line | Limits were added where none were needed | Remove the hedges from the sentences marked seen |
Made by Adamiro. Adamiro writes from your own notes and proof facts in your voice, so a draft starts from what you have seen. https://adamiro.com/products/adamiro-voice/?utm_source=claude-skill&utm_medium=download&utm_campaign=linkedin-right-to-say-it
(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 |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |