[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MGAJC4HXEASS56NDQNG6HW":3,"skill-same:01M6MGAJC4HXEASS56NDQNG6HW":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":13,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M6MGAJC4HXEASS56NDQNG6HW","linkedin-content",null,"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.","JiayiV\u002Fquestion_mixing","JiayiV","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54466889?v=4","01M6JFJYYMRZ3QRGP9339JNQ2K","01M6JFJZ35KB0QVT50NAHPJA7G",0,"MIT","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-linkedin-content-skill-799cb0b9\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"content","linkedin","linkedin content","video script","splits","standalone","carousel","posts","reuse","sources","material","long","triggers","review","mechanics","good","use","Video","transcript","lint","2026-11-10 10:12:30",false,"---\nname: linkedin-content\ndescription: 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.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-08-25\n---\n\n# LinkedIn Content — format, draft, lint\n\nThe post is not the deliverable; the specific thing only this person can say is. The scripts\nhandle format choice, mechanical faults, and de-duplication. The interesting part — what\nactually happened and what it cost — comes from the user, and cannot be generated.\n\n## Workflow\n\n**1. Check the brief exists.** If there is no positioning brief, offer `linkedin-strategy`\nfirst as a question. Posts without pillars are noise. Never chain silently.\n\n**2. Pick the format from the material, not from fashion.**\n\n```bash\npython3 scripts\u002Fformat_picker.py --goal authority --material data --material tutorial \\\n  --minutes 120 --output human\n```\n\nExit 0 recommends \u002F 2 asks when the top two are within a point (tie-break on which one they\nwould enjoy making — the one they repeat beats the one that scores higher once) \u002F 3 no fit,\ngo get material. It refuses video with no camera and no footage, and a poll with no real\ndecision behind it.\n\n**3. Draft.** Interview for specifics before writing a line: the number, the mistake, the\nsentence someone said. Then write to the fold — **the first ~140 characters are the whole\npost for most readers**, and a sentence must complete inside them.\n\n**4. Lint before it ships.**\n\n```bash\npython3 scripts\u002Fpost_linter.py --input draft.md --has-image --output human\n```\n\nExit 0 SHIP \u002F 2 REVISE (or any blocking finding) \u002F 3 REWRITE. Blocking findings have named\nconsequences: over the 3,000-character cap; engagement bait, named as demoted content in the\nProfessional Community Policies; Unicode pseudo-bold, which screen readers announce as\nmathematical symbols and search does not index as words. Two passes is normal; the stop\ncondition is exit 0 or a stated decision to accept a warning.\n\n**5. Repurposing.** Split a source and keep the ledger — it prevents the specific recurring\nfailure of the same idea going out three times over eight months. Commit it alongside the\nsource; it is project state, not a cache. Every unit is source material, not a post: add the\nsentence only the author can write — what it cost, or what they would do differently.\n\n```bash\npython3 scripts\u002Frepurpose_splitter.py --input talk.md --ledger .linkedin-ledger.json --output human\npython3 scripts\u002Frepurpose_splitter.py --input talk.md --ledger .linkedin-ledger.json --record 2 --posted-on 2026-08-25\n```\n\n## Rules\n\n- **Never fabricate a number, a client, a result, or a quote.** Not one, not as a placeholder.\n- **Write to the mobile fold.** A sentence completes before character 140.\n- **Links in the first comment**, and say so in the post.\n- **No Unicode pseudo-bold, ever.** It is an accessibility failure, not a style choice.\n- **Alt text on every image; captions on every video.** LinkedIn does not add them for you.\n- **No engagement bait.** Ask the question the post actually earned.\n- **The author reads every line before it ships.** They are the author of record.\n\n## Scripts\n\n| Script | Role |\n|---|---|\n| [`scripts\u002Fpost_linter.py`](scripts\u002Fpost_linter.py) | 0-100 across mechanics \u002F hook \u002F integrity \u002F accessibility; blocking findings for the cap, bait, and pseudo-bold. |\n| [`scripts\u002Fformat_picker.py`](scripts\u002Fformat_picker.py) | Ranks nine native formats against goal, material, and minutes; refuses camera-less video and decision-less polls. |\n| [`scripts\u002Frepurpose_splitter.py`](scripts\u002Frepurpose_splitter.py) | Splits a source into standalone units, scores them, and skips anything already in the reuse ledger. |\n\n## References and assets\n\n- [`references\u002Fhook_and_fold_mechanics.md`](references\u002Fhook_and_fold_mechanics.md) — the first 140 characters, and the openers to delete on sight (7 sources)\n- [`references\u002Fpost_formats_canon.md`](references\u002Fpost_formats_canon.md) — what each native format is good at, and the carousel trap (7 sources)\n- [`references\u002Frepurposing_discipline.md`](references\u002Frepurposing_discipline.md) — standalone units, the reuse ledger, source types and their risks (7 sources)\n- [`references\u002Faccessibility_and_inclusion.md`](references\u002Faccessibility_and_inclusion.md) — pseudo-bold, alt text, captions, and why they are blocking (7 sources)\n\n- [`assets\u002Fpost_templates.md`](assets\u002Fpost_templates.md) — five worked post shapes with the hook already doing its job\n- [`assets\u002Fexample_post.md`](assets\u002Fexample_post.md) — a post that passes the linter, annotated\n\n## Distinct from\n\n- **`linkedin-strategy`** — decides what the posts are about. This writes them.\n- **`linkedin-engagement`** — comments and DMs. A comment is a different craft with a\n  different budget; it lives there.\n- **`marketing-skill\u002Fcopywriting` \u002F `content-humanizer`** — general copy and de-AI passes.\n  Reach for those for tone; this one owns LinkedIn's mechanics and its accessibility floor.\n\n---\n\n**Version:** 1.0.0\n","# LinkedIn Content — format, draft, lint\n\nThe post is not the deliverable; the specific thing only this person can say is. The scripts\nhandle format choice, mechanical faults, and de-duplication. The interesting part — what\nactually happened and what it cost — comes from the user, and cannot be generated.\n\n## Workflow\n\n**1. Check the brief exists.** If there is no positioning brief, offer `linkedin-strategy`\nfirst as a question. Posts without pillars are noise. Never chain silently.\n\n**2. Pick the format from the material, not from fashion.**\n\n```bash\npython3 scripts\u002Fformat_picker.py --goal authority --material data --material tutorial \\\n  --minutes 120 --output human\n```\n\nExit 0 recommends \u002F 2 asks when the top two are within a point (tie-break on which one they\nwould enjoy making — the one they repeat beats the one that scores higher once) \u002F 3 no fit,\ngo get material. It refuses video with no camera and no footage, and a poll with no real\ndecision behind it.\n\n**3. Draft.** Interview for specifics before writing a line: the number, the mistake, the\nsentence someone said. Then write to the fold — **the first ~140 characters are the whole\npost for most readers**, and a sentence must complete inside them.\n\n**4. Lint before it ships.**\n\n```bash\npython3 scripts\u002Fpost_linter.py --input draft.md --has-image --output human\n```\n\nExit 0 SHIP \u002F 2 REVISE (or any blocking finding) \u002F 3 REWRITE. Blocking findings have named\nconsequences: over the 3,000-character cap; engagement bait, named as demoted content in the\nProfessional Community Policies; Unicode pseudo-bold, which screen readers announce as\nmathematical symbols and search does not index as words. Two passes is normal; the stop\ncondition is exit 0 or a stated decision to accept a warning.\n\n**5. Repurposing.** Split a source and keep the ledger — it prevents the specific recurring\nfailure of the same idea going out three times over eight months. Commit it alongside the\nsource; it is project state, not a cache. Every unit is source material, not a post: add the\nsentence only the author can write — what it cost, or what they would do differently.\n\n```bash\npython3 scripts\u002Frepurpose_splitter.py --input talk.md --ledger .linkedin-ledger.json --output human\npython3 scripts\u002Frepurpose_splitter.py --input talk.md --ledger .linkedin-ledger.json --record 2 --posted-on 2026-08-25\n```\n\n## Rules\n\n- **Never fabricate a number, a client, a result, or a quote.** Not one, not as a placeholder.\n- **Write to the mobile fold.** A sentence completes before character 140.\n- **Links in the first comment**, and say so in the post.\n- **No Unicode pseudo-bold, ever.** It is an accessibility failure, not a style choice.\n- **Alt text on every image; captions on every video.** LinkedIn does not add them for you.\n- **No engagement bait.** Ask the question the post actually earned.\n- **The author reads every line before it ships.** They are the author of record.\n\n## Scripts\n\n| Script | Role |\n|---|---|\n| [`scripts\u002Fpost_linter.py`](scripts\u002Fpost_linter.py) | 0-100 across mechanics \u002F hook \u002F integrity \u002F accessibility; blocking findings for the cap, bait, and pseudo-bold. |\n| [`scripts\u002Fformat_picker.py`](scripts\u002Fformat_picker.py) | Ranks nine native formats against goal, material, and minutes; refuses camera-less video and decision-less polls. |\n| [`scripts\u002Frepurpose_splitter.py`](scripts\u002Frepurpose_splitter.py) | Splits a source into standalone units, scores them, and skips anything already in the reuse ledger. |\n\n## References and assets\n\n- [`references\u002Fhook_and_fold_mechanics.md`](references\u002Fhook_and_fold_mechanics.md) — the first 140 characters, and the openers to delete on sight (7 sources)\n- [`references\u002Fpost_formats_canon.md`](references\u002Fpost_formats_canon.md) — what each native format is good at, and the carousel trap (7 sources)\n- [`references\u002Frepurposing_discipline.md`](references\u002Frepurposing_discipline.md) — standalone units, the reuse ledger, source types and their risks (7 sources)\n- [`references\u002Faccessibility_and_inclusion.md`](references\u002Faccessibility_and_inclusion.md) — pseudo-bold, alt text, captions, and why they are blocking (7 sources)\n\n- [`assets\u002Fpost_templates.md`](assets\u002Fpost_templates.md) — five worked post shapes with the hook already doing its job\n- [`assets\u002Fexample_post.md`](assets\u002Fexample_post.md) — a post that passes the linter, annotated\n\n## Distinct from\n\n- **`linkedin-strategy`** — decides what the posts are about. This writes them.\n- **`linkedin-engagement`** — comments and DMs. A comment is a different craft with a\n  different budget; it lives there.\n- **`marketing-skill\u002Fcopywriting` \u002F `content-humanizer`** — general copy and de-AI passes.\n  Reach for those for tone; this one owns LinkedIn's mechanics and its accessibility floor.\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"license":14,"metadata":48,"description":7},{"author":49,"updated":50,"version":51,"category":52},"Alireza Rezvani",1787616000000,"1.0.0","marketing","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-02-claude-skills-main-gemini-skills-linkedin-content-skill-799cb0b9","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill linkedin-content",{"tool":65,"command":66},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill linkedin-content",{"tool":68,"command":69},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill linkedin-content","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-linkedin-content-skill-799cb0b9\u002FSKILL.md",true,[],[74,99,127,159,187,218],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":43},"01M6NN9PJS9NHWPDG4QP93BP8F","webmcpify","Make a web app agent-ready — propose a WebMCP tool manifest, integrate, verify in a real browser, heal; unrelated code stays untouched. Use for \"webmcpify\", \"add WebMCP\", or \"expose app actions to AI agents\".","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fwebmcpify\u002FSKILL.md",[],[76,81,82,83,84,85,86,87,88,89,90,91,92,39,93,94,95,96,97,98],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","ready","unrelated","app","scope","for","webmcp",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":43},"01M6NN6KZE5RBN6NGHN2WXV1RE","vardoger-analyze","Use when the user asks to personalize the GitHub Copilot CLI assistant, adapt Copilot to their style, use vardoger, or analyze their Copilot CLI conversation history. Reads the local session directory at `~\u002F.copilot\u002Fsession-state\u002F`, extracts recurring preferences and conventions, and writes a fenced personalization block into `~\u002F.copilot\u002Fcopilot-instructions.md`. Runs entirely on the user's machine via the local `vardoger` CLI (`pipx install vardoger`); no network calls and no uploads. Triggers: 'personalize my copilot', 'analyze my copilot history', 'tailor copilot to me', 'run vardoger', 'update my copilot instructions from history', 'make copilot learn my style'.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fvardoger-analyze\u002FSKILL.md",[],[107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126],"vardoger analyze","analyze","directory","cli","github copilot","copilot","run","update","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","my","at","copilot instructions",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":141,"publishedAt":43},"01M6NN3CZGQP3XAJ04BM1NNYGT","transloadit-media-processing","Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS\u002FMP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftransloadit-media-processing\u002FSKILL.md",[133,138],{"categoryNo":134,"categoryName":135,"taxonomyType":136,"taxonomyTypeDesc":137},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":139,"categoryName":140,"taxonomyType":136,"taxonomyTypeDesc":137},"01JBSEEDCAT000000000000023","Skill与智能体开发",[142,143,144,145,146,147,148,149,150,151,40,152,153,39,154,155,156,157,97,158],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Audio","mp4","images","files","transformation","free","hls",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":168,"publishedAt":43},"01M6NN28E92F9GH4WFYQ2H1Y15","terraform-azurerm-set-diff-analyzer","Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-azurerm-set-diff-analyzer\u002FSKILL.md",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":136,"taxonomyTypeDesc":137},"01JBSEEDCAT000000000000011","运维与部署",[169,170,171,172,173,174,175,176,177,39,178,179,180,181,182,183,184,185,186,97],"terraform","SET","terraform azurerm set diff analyzer","diff","analyzer","diffs","azure","gateway","firewall","only","resource changes","provider","resources","load balancer","attributes","front","load","balancer",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":200,"publishedAt":43},"01M6NN1QMH2TDYWTH3XY3N5XPV","technical-job-search","Use this skill when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV\u002Fresume, writing a cover letter, evaluating a job offer, or drafting a post-interview follow-up email. Do not activate for general career advice unrelated to an active job search action.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-job-search\u002FSKILL.md",[193,196,197],{"categoryNo":194,"categoryName":195,"taxonomyType":136,"taxonomyTypeDesc":137},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":198,"categoryName":199,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000038","人力资源",[201,202,203,204,205,206,207,208,108,209,39,210,211,212,213,214,215,216,97,217],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","activate","do","task","cv","letter",{"skillNo":219,"name":220,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":222,"categories":223,"keywords":224,"publishedAt":43},"01M6NMZFA67XYS1GS09WT42235","steno-mode","Shorthand-first response compression that cuts ~40% of response tokens while preserving technical precision and exact literals. Use when the user says \"steno mode\", \"shorthand mode\", \"compressed responses\", \"token reduction\", \"brief structured output\", or invokes \u002Fsteno. Supports four compression levels: lite, brief, court, machine. Do not trigger for requests needing polished prose such as onboarding\u002Ftutorial content, stakeholder or customer-facing copy, or teaching-focused explanations.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fsteno-mode\u002FSKILL.md",[],[225,226,227,228,229,204,230,39,214,231,232,233,234,235,236,237,238,239,97,240],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]