skills/linkedin-caption-narrative/references/reference-examples.md

# Reference Examples

These examples describe transferable mechanics from the supplied style references

Do not copy their wording mechanically

## claudish-to-english

Observed pattern

- opens on one precise weakness: Claude explanations can feel academic
- names the repo immediately
- gives a compact access strip: free, open-source, local
- explains the mechanism in sequence
- includes exact install commands
- shows two operating modes
- closes with privacy and failure behavior

Transferable lesson

**A technical repo becomes readable when the caption explains the background process in plain verbs**

## 100+ Claude repos catalogue

Observed pattern

- opens with collection scale
- groups resources by job instead of ranking everything
- category labels such as HARNESS, SKILLS, MEMORY, TOOLS, and COST create a mental map
- each category ends with one consequence line
- named repos do most of the credibility work

Transferable lesson

**Large lists need an organizing model and category-level consequences**

## olmOCR

Observed pattern

- opens with a specific category failure
- names the inputs the tool handles
- uses capability then consequence pairs
- includes benchmark, cost, hardware, and license details
- lets operational facts carry the persuasion

Transferable lesson

**For technical tools, constraints and operating details often do more work than adjectives**

## i-have-adhd

Observed pattern

- hook is behavioral rather than architectural
- product behavior is shown as a compact checklist
- every rule maps to a recognizable usage consequence
- architecture is intentionally secondary

Transferable lesson

**When a product changes behavior rather than infrastructure, show the behavior directly**

## /last30days

Observed pattern

- starts from research staleness
- names multiple sources and gives each source a distinct signal role
- reframes the value from searching more to comparing signals
- shows the process as a short chain
- ends with practical pre-work use cases
- bridges directly into the visual

Transferable lesson

**For multi-source research, synthesis is the story, not source count**

## GEO and AEO page example

Observed pattern

- belief correction appears in the first line
- the broad concept becomes three practical criteria
- the post contains a diagnostic question the reader can run immediately
- the visual is explicitly labeled as an example instead of a client result

Transferable lesson

**A strong educational caption converts a broad idea into a concrete check**

## Shared mechanics across the reference set

1. short opening tension
2. named artifact or claim early
3. one main idea per paragraph
4. mechanism before praise
5. specifics as credibility
6. `↳` for consequence or explanation
7. category labels when a list is long
8. practical why-it-matters line
9. one visual bridge when applicable
10. first comment for links or setup
11. one answerable closing question

## What not to imitate

Do not copy

- exact hook wording
- exact category names when the new material needs a different taxonomy
- decorative bolding everywhere
- link placement that hurts the new caption's readability
- unsupported numbers or star counts
- a CTA just because the reference used one

Transfer the communication logic, not the surface pattern