linkedin-post-writer SKILL.md skillA
linkedin-post-writer from kulykivska/claude-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kulykivska/claude-plugins/linkedin-post-writer@git:20260922.a4bd47bPins git:20260922.a4bd47b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kulykivska/claude-plugins
- Path
content/skills/linkedin-post-writer/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260922.a4bd47b, committed Sep 22, 2026
- First version recorded
- Sep 22, 2026
- Size
- 9,234 bytes
- Repository stars
- 6
- License
- MIT
Use this skill whenever the user wants to write, draft, or improve a LinkedIn post — especially when the goal is maximum reach, impressions, or engagement. Trigger for requests like "write a LinkedIn post", "help me draft a post", "create a LinkedIn post about...", "write a LinkedIn post about...", "draft a post for my LinkedIn", "how should I post about X on LinkedIn", or any request to create social media content for LinkedIn. Also trigger when the user says "publish this post…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# LinkedIn Post Writer — Proven High-Reach Formula This skill is built from analysis of real LinkedIn post data for a Senior AI Engineer profile (956 followers, 28 110 impressions/year, +32% growth). The patterns below are what actually drove the highest-performing posts — not general best practices, but observed results from the account. ## The Core Post Formula Every high-performing post follows this 4-part structure: ``` [HOOK] — First 1–2 lines. Visible BEFORE "...see more". This is everything. [CONTEXT] — Why it matters right now, for this audience. [VALUE] — Structured body with specifics: numbers, emojis as anchors, concrete data. [QUESTION] — One open question inviting a reply. Required for comments. ``` The hook is the single biggest lever. If it doesn't create curiosity or tension, nothing else matters — the post won't be expanded. **Hook patterns that work (ranked by observed impact):** - Personal admission: *"3 weeks ago I deleted ChatGPT."* → 6 279 impressions - Provocative contrast: *"The tech industry feels like a pool of inflatable balloons."* → 425 impressions, strong comments …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_bjelynzf2x5pgeuo/0fc4aeba010233032aa362a6e02f025effe50c3ac0265a0af421cb6aab1d50e9.json
Then /plugin install linkedin-post-writer@markdownregistry-bjelynzf2x5pgeuo in Claude Code. It installs git:20260922.a4bd47b, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add kulykivska/claude-plugins/linkedin-post-writer@sha256:0fc4aeba01023303The line at the top of this page pins the label git:20260922.a4bd47b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_bjelynzf2x5pgeuo)
3 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in kulykivska/claude-plugins/linkedin-post-writer since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of linkedin-post-writer from somewhere else? Ask it: where did my linkedin-post-writer come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, all committed on Sep 22, 2026.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260922.a4bd47b latest | 2026-09-22 | a4bd47b | 9,234 B | A | view · diff |
| git:20260922.754ed13 | 2026-09-22 | 754ed13 | 9,293 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/linkedin-post-writer/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9234 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kulykivska/claude-plugins · 6 stars · license MIT · pushed 2026-11-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bjelynzf2x5pgeuo GET https://markdownregistry.com/api/v1/resolve?ref=kulykivska/claude-plugins/linkedin-post-writer GET https://markdownregistry.com/api/v1/blob/0fc4aeba010233032aa362a6e02f025effe50c3ac0265a0af421cb6aab1d50e9
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from kulykivska/claude-plugins
Every file in kulykivska/claude-plugins