linkedin-content
Use when someone wants to write, edit, or lint a LinkedIn post — a story, how-to, opinion piece, carousel script, video script, or poll — or wants an article, talk, or transcript repurposed into posts. Triggers on "write a LinkedIn post", "is this hook any good", "review my post", "turn this into LinkedIn posts", "carousel", "what format should this be". Lints posts 0-100 on mechanics, hook, integrity, and accessibility; picks the format the material actually supports; and splits long sources into standalone units with a reuse ledger.
- License 许可
- MIT
- 最近更新
- 2026-10-10
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- linkedin-content
- license
- MIT
- metadata
- { "author": "Alireza Rezvani", "updated": 1787616000000, "version": "1.0.0", "category": "marketing" }
- description
- Use when someone wants to write, edit, or lint a LinkedIn post — a story, how-to, opinion piece, carousel script, video script, or poll — or wants an article, talk, or transcript repurposed into posts. Triggers on "write a LinkedIn post", "is this hook any good", "review my post", "turn this into LinkedIn posts", "carousel", "what format should this be". Lints posts 0-100 on mechanics, hook, integrity, and accessibility; picks the format the material actually supports; and splits long sources into standalone units with a reuse ledger.
02 资源文件 9
- 资产文件assets/example_post.md2.3 KB
- 资产文件assets/post_templates.md3.8 KB
- 参考文档references/accessibility_and_inclusion.md5.8 KB
- 参考文档references/hook_and_fold_mechanics.md6.0 KB
- 参考文档references/post_formats_canon.md6.0 KB
- 参考文档references/repurposing_discipline.md5.8 KB
- 脚本scripts/format_picker.py11.8 KB
- 脚本scripts/post_linter.py15.5 KB
- 脚本scripts/repurpose_splitter.py11.9 KB
03 SKILL.md 正文
LinkedIn Content — format, draft, lint
The post is not the deliverable; the specific thing only this person can say is. The scripts handle format choice, mechanical faults, and de-duplication. The interesting part — what actually happened and what it cost — comes from the user, and cannot be generated.
Workflow
1. Check the brief exists. If there is no positioning brief, offer linkedin-strategy
first as a question. Posts without pillars are noise. Never chain silently.
2. Pick the format from the material, not from fashion.
python3 scripts/format_picker.py --goal authority --material data --material tutorial \
--minutes 120 --output human
Exit 0 recommends / 2 asks when the top two are within a point (tie-break on which one they would enjoy making — the one they repeat beats the one that scores higher once) / 3 no fit, go get material. It refuses video with no camera and no footage, and a poll with no real decision behind it.
3. Draft. Interview for specifics before writing a line: the number, the mistake, the sentence someone said. Then write to the fold — the first ~140 characters are the whole post for most readers, and a sentence must complete inside them.
4. Lint before it ships.
python3 scripts/post_linter.py --input draft.md --has-image --output human
Exit 0 SHIP / 2 REVISE (or any blocking finding) / 3 REWRITE. Blocking findings have named consequences: over the 3,000-character cap; engagement bait, named as demoted content in the Professional Community Policies; Unicode pseudo-bold, which screen readers announce as mathematical symbols and search does not index as words. Two passes is normal; the stop condition is exit 0 or a stated decision to accept a warning.
5. Repurposing. Split a source and keep the ledger — it prevents the specific recurring failure of the same idea going out three times over eight months. Commit it alongside the source; it is project state, not a cache. Every unit is source material, not a post: add the sentence only the author can write — what it cost, or what they would do differently.
python3 scripts/repurpose_splitter.py --input talk.md --ledger .linkedin-ledger.json --output human
python3 scripts/repurpose_splitter.py --input talk.md --ledger .linkedin-ledger.json --record 2 --posted-on 2026-08-25
Rules
- Never fabricate a number, a client, a result, or a quote. Not one, not as a placeholder.
- Write to the mobile fold. A sentence completes before character 140.
- Links in the first comment, and say so in the post.
- No Unicode pseudo-bold, ever. It is an accessibility failure, not a style choice.
- Alt text on every image; captions on every video. LinkedIn does not add them for you.
- No engagement bait. Ask the question the post actually earned.
- The author reads every line before it ships. They are the author of record.
Scripts
| Script | Role |
|---|---|
scripts/post_linter.py |
0-100 across mechanics / hook / integrity / accessibility; blocking findings for the cap, bait, and pseudo-bold. |
scripts/format_picker.py |
Ranks nine native formats against goal, material, and minutes; refuses camera-less video and decision-less polls. |
scripts/repurpose_splitter.py |
Splits a source into standalone units, scores them, and skips anything already in the reuse ledger. |
References and assets
-
references/hook_and_fold_mechanics.md— the first 140 characters, and the openers to delete on sight (7 sources) -
references/post_formats_canon.md— what each native format is good at, and the carousel trap (7 sources) -
references/repurposing_discipline.md— standalone units, the reuse ledger, source types and their risks (7 sources) -
references/accessibility_and_inclusion.md— pseudo-bold, alt text, captions, and why they are blocking (7 sources) -
assets/post_templates.md— five worked post shapes with the hook already doing its job -
assets/example_post.md— a post that passes the linter, annotated
Distinct from
linkedin-strategy— decides what the posts are about. This writes them.linkedin-engagement— comments and DMs. A comment is a different craft with a different budget; it lives there.marketing-skill/copywriting/content-humanizer— general copy and de-AI passes. Reach for those for tone; this one owns LinkedIn's mechanics and its accessibility floor.
Version: 1.0.0
04 同仓库更多 Skills
syllabus
Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.
pulse
Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.
patent
Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.
notebooklm
Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio/Video Overviews, Mind Maps, Reports incl. Briefing Doc/Study Guide/FAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.
litreview
Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed/OpenAlex (or Consensus) query.
grants
NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance/Innovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget/scope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.