[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MGB76WVCQT71M2E2003J1W":3,"skill-same:01M6MGB76WVCQT71M2E2003J1W":68},{"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":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":13,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6MGB76WVCQT71M2E2003J1W","linkedin-strategy",null,"Use when someone needs a LinkedIn plan rather than a post — content pillars, positioning for a career change or consulting or thought leadership, a sustainable posting cadence, or a newsletter decision. Triggers on \"what should I post about\", \"how often should I post\", \"LinkedIn content strategy\", \"should I start a LinkedIn newsletter\", \"grow my following\", \"90-day plan\". Validates the positioning brief, sizes the week against real hours and refuses a plan that will not survive week five, and gates a newsletter against eligibility and a six-month cadence commitment.","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-strategy-skill-717d07d5\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"linkedin","strategy","linkedin strategy","positioning","for","linkedin content strategy","content pillars","cadence","post","triggers","posting","gates","leadership","change","use","linkedin content","decision","plan","how","brief","2026-11-10 10:12:30",false,"---\nname: linkedin-strategy\ndescription: Use when someone needs a LinkedIn plan rather than a post — content pillars, positioning for a career change or consulting or thought leadership, a sustainable posting cadence, or a newsletter decision. Triggers on \"what should I post about\", \"how often should I post\", \"LinkedIn content strategy\", \"should I start a LinkedIn newsletter\", \"grow my following\", \"90-day plan\". Validates the positioning brief, sizes the week against real hours and refuses a plan that will not survive week five, and gates a newsletter against eligibility and a six-month cadence commitment.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-08-25\n---\n\n# LinkedIn Strategy — brief, cadence, newsletter\n\nThree decisions, in this order. Out of order is why most LinkedIn efforts produce a feed of\nunrelated observations and stop in week five.\n\n## Workflow\n\n**1. The brief — an editorial constitution, not a wish.** Walk the five questions one at a\ntime, each with a recommended answer, then validate:\n\n```bash\npython3 scripts\u002Fpositioning_brief.py --input brief.json --output human\n```\n\nIt refuses on the two things that make everything downstream impossible: an objective that\nis not one of the six real ones (`career-change`, `consulting`, `thought-leadership`,\n`hiring`, `fundraising`, `community`), and an audience too broad to exclude anyone. It also\nrefuses fewer than two exclusions — **a positioning that excludes nothing is availability.**\n\nPillars: two to four, shares summing to 100, at least one backed by proof that already\nexists, at least one at 10-20% as the experimental slot. Every pillar needs a \"why you\"; if\nanyone could post it, cut it.\n\nThe script emits observable 90-day criteria. Follower count is deliberately absent — it moves\nfor reasons unrelated to whether the objective is being met.\n\n**2. The cadence — priced against a bad week.**\n\n```bash\npython3 scripts\u002Fcadence_planner.py --minutes 240 --stage starting --target-posts 3 --output human\n```\n\nExit 0 fits \u002F 2 below the 90-minute floor \u002F 3 over budget with the overage named. Every\nactivity is priced in minutes including the reply window, which is part of the post and not\nan extra. Allocation shifts with stage: from a standing start **60% of the budget belongs in\nother people's comment sections**, because a post published to nobody reaches nobody.\n\nBelow 90 minutes a week it refuses to plan a posting schedule and returns a comment-only\nweek: a cadence abandoned in week five is worse than one never started, because the\nabandonment is visible on the profile. Every plan ships with a minimum viable week.\n\n**3. The newsletter — only if the promise can be paid.**\n\n```bash\npython3 scripts\u002Fnewsletter_planner.py --followers 1800 --cadence biweekly \\\n  --minutes-per-month 420 --pillar \"...\" --output human\n```\n\nRefuses below LinkedIn's published 150-follower evaluation floor, and refuses a cadence\nwhose six-month cost exceeds the budget. Emits a 12-issue arc rotating issue types across\npillars, and a stop rule written before issue one.\n\n## Rules\n\n- **One objective.** Two objectives serve neither; the audiences overlap less than they look.\n- **The exclusion list is the positioning.** Refuse to skip it.\n- **Price the week from a bad week, not a good one.**\n- **Consistency over volume.** A skipped week is fine; a skipped month resets you.\n- **Review the brief quarterly, not weekly.** A brief revised monthly is a mood.\n\n## Scripts\n\n| Script | Role |\n|---|---|\n| [`scripts\u002Fpositioning_brief.py`](scripts\u002Fpositioning_brief.py) | Validates objective, audience, 2-4 proof-backed pillars, and the exclusion list; emits observable 90-day criteria. |\n| [`scripts\u002Fcadence_planner.py`](scripts\u002Fcadence_planner.py) | Prices the week in minutes, allocates by stage, refuses over-budget targets, emits the minimum viable week. |\n| [`scripts\u002Fnewsletter_planner.py`](scripts\u002Fnewsletter_planner.py) | Eligibility + six-month sustainability gate, 12-issue arc across pillars, stop rule. |\n\n## References and assets\n\n- [`references\u002Fobjective_to_pillars.md`](references\u002Fobjective_to_pillars.md) — the six objectives and the pillar arithmetic (7 sources)\n- [`references\u002Fcadence_and_consistency.md`](references\u002Fcadence_and_consistency.md) — what a post really costs and why the floor exists (7 sources)\n- [`references\u002Fnewsletter_playbook.md`](references\u002Fnewsletter_playbook.md) — eligibility, cadence as a promise, the stop rule (7 sources)\n\n- [`assets\u002Fpositioning_brief_template.md`](assets\u002Fpositioning_brief_template.md) — fillable brief\n- [`assets\u002Fexample_brief.json`](assets\u002Fexample_brief.json) — a passing brief, for the validator\n\n## Distinct from\n\n- **`linkedin-content`** — drafts and lints individual posts. This decides what they are about\n  and how many there are. Posts without pillars are noise; offer this first, never chain silently.\n- **`linkedin-analytics`** — tells you what happened. This decides what to do next.\n- **`marketing-skill\u002Fcontent-strategy`** — company-level content marketing. This is one\n  person's own presence.\n\n---\n\n**Version:** 1.0.0\n","# LinkedIn Strategy — brief, cadence, newsletter\n\nThree decisions, in this order. Out of order is why most LinkedIn efforts produce a feed of\nunrelated observations and stop in week five.\n\n## Workflow\n\n**1. The brief — an editorial constitution, not a wish.** Walk the five questions one at a\ntime, each with a recommended answer, then validate:\n\n```bash\npython3 scripts\u002Fpositioning_brief.py --input brief.json --output human\n```\n\nIt refuses on the two things that make everything downstream impossible: an objective that\nis not one of the six real ones (`career-change`, `consulting`, `thought-leadership`,\n`hiring`, `fundraising`, `community`), and an audience too broad to exclude anyone. It also\nrefuses fewer than two exclusions — **a positioning that excludes nothing is availability.**\n\nPillars: two to four, shares summing to 100, at least one backed by proof that already\nexists, at least one at 10-20% as the experimental slot. Every pillar needs a \"why you\"; if\nanyone could post it, cut it.\n\nThe script emits observable 90-day criteria. Follower count is deliberately absent — it moves\nfor reasons unrelated to whether the objective is being met.\n\n**2. The cadence — priced against a bad week.**\n\n```bash\npython3 scripts\u002Fcadence_planner.py --minutes 240 --stage starting --target-posts 3 --output human\n```\n\nExit 0 fits \u002F 2 below the 90-minute floor \u002F 3 over budget with the overage named. Every\nactivity is priced in minutes including the reply window, which is part of the post and not\nan extra. Allocation shifts with stage: from a standing start **60% of the budget belongs in\nother people's comment sections**, because a post published to nobody reaches nobody.\n\nBelow 90 minutes a week it refuses to plan a posting schedule and returns a comment-only\nweek: a cadence abandoned in week five is worse than one never started, because the\nabandonment is visible on the profile. Every plan ships with a minimum viable week.\n\n**3. The newsletter — only if the promise can be paid.**\n\n```bash\npython3 scripts\u002Fnewsletter_planner.py --followers 1800 --cadence biweekly \\\n  --minutes-per-month 420 --pillar \"...\" --output human\n```\n\nRefuses below LinkedIn's published 150-follower evaluation floor, and refuses a cadence\nwhose six-month cost exceeds the budget. Emits a 12-issue arc rotating issue types across\npillars, and a stop rule written before issue one.\n\n## Rules\n\n- **One objective.** Two objectives serve neither; the audiences overlap less than they look.\n- **The exclusion list is the positioning.** Refuse to skip it.\n- **Price the week from a bad week, not a good one.**\n- **Consistency over volume.** A skipped week is fine; a skipped month resets you.\n- **Review the brief quarterly, not weekly.** A brief revised monthly is a mood.\n\n## Scripts\n\n| Script | Role |\n|---|---|\n| [`scripts\u002Fpositioning_brief.py`](scripts\u002Fpositioning_brief.py) | Validates objective, audience, 2-4 proof-backed pillars, and the exclusion list; emits observable 90-day criteria. |\n| [`scripts\u002Fcadence_planner.py`](scripts\u002Fcadence_planner.py) | Prices the week in minutes, allocates by stage, refuses over-budget targets, emits the minimum viable week. |\n| [`scripts\u002Fnewsletter_planner.py`](scripts\u002Fnewsletter_planner.py) | Eligibility + six-month sustainability gate, 12-issue arc across pillars, stop rule. |\n\n## References and assets\n\n- [`references\u002Fobjective_to_pillars.md`](references\u002Fobjective_to_pillars.md) — the six objectives and the pillar arithmetic (7 sources)\n- [`references\u002Fcadence_and_consistency.md`](references\u002Fcadence_and_consistency.md) — what a post really costs and why the floor exists (7 sources)\n- [`references\u002Fnewsletter_playbook.md`](references\u002Fnewsletter_playbook.md) — eligibility, cadence as a promise, the stop rule (7 sources)\n\n- [`assets\u002Fpositioning_brief_template.md`](assets\u002Fpositioning_brief_template.md) — fillable brief\n- [`assets\u002Fexample_brief.json`](assets\u002Fexample_brief.json) — a passing brief, for the validator\n\n## Distinct from\n\n- **`linkedin-content`** — drafts and lints individual posts. This decides what they are about\n  and how many there are. Posts without pillars are noise; offer this first, never chain silently.\n- **`linkedin-analytics`** — tells you what happened. This decides what to do next.\n- **`marketing-skill\u002Fcontent-strategy`** — company-level content marketing. This is one\n  person's own presence.\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"license":14,"metadata":43,"description":7},{"author":44,"updated":45,"version":46,"category":47},"Alireza Rezvani",1787616000000,"1.0.0","marketing","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-02-claude-skills-main-gemini-skills-linkedin-strategy-skill-717d07d5","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill linkedin-strategy",{"tool":60,"command":61},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill linkedin-strategy",{"tool":63,"command":64},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill linkedin-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-linkedin-strategy-skill-717d07d5\u002FSKILL.md",true,[],[69,93,121,154,182,217],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":38},"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",[],[71,76,77,78,79,80,81,82,83,84,85,86,87,32,88,89,90,91,22,92],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","ready","unrelated","app","scope","webmcp",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":38},"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",[],[101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120],"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":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":135,"publishedAt":38},"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",[127,132],{"categoryNo":128,"categoryName":129,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":133,"categoryName":134,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000023","Skill与智能体开发",[136,137,138,139,140,141,142,143,144,145,146,147,148,32,149,150,151,152,22,153],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":163,"publishedAt":38},"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",[160],{"categoryNo":161,"categoryName":162,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000011","运维与部署",[164,165,166,167,168,169,170,171,172,32,173,174,175,176,177,178,179,180,181,22],"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":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":199,"publishedAt":38},"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",[188,191,196],{"categoryNo":189,"categoryName":190,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":192,"categoryName":193,"taxonomyType":194,"taxonomyTypeDesc":195},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":197,"categoryName":198,"taxonomyType":194,"taxonomyTypeDesc":195},"01JBSEEDCAT000000000000038","人力资源",[200,201,202,203,204,205,206,207,102,208,32,209,210,211,212,213,214,215,22,216],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","activate","do","task","cv","letter",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":223,"publishedAt":38},"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",[],[224,225,226,37,227,203,228,32,213,229,230,231,232,233,234,235,236,237,22,238],"steno mode","mode","customer","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]