[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QJ2AEPPGP660QGSJFJKG1D":3,"skill-same:01M6QJ2AEPPGP660QGSJFJKG1D":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":14,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6QJ2AEPPGP660QGSJFJKG1D","linkedin-engagement",null,"Use when someone wants to grow reach through comments, replies, groups, or outreach on LinkedIn — a commenting roster, a connection request note, a DM or InMail, a networking plan, or a check on whether their outreach volume is safe. Triggers on \"who should I engage with\", \"write a connection request\", \"cold DM\", \"LinkedIn outreach\", \"networking strategy\", \"how many invites can I send\". Builds a weekly comment roster inside a real time budget, assembles one message at a time and refuses templates, and caps volume against LinkedIn's limits. Nothing is ever sent.","Tashima-Tarsh\u002FDisha6.6","Tashima-Tarsh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269906498?v=4","01M6PBH98X03XERH0HFT4PFB1P","NITISH KUMAR","01M6PBH9DA0M6KM3Z12P848F0K",0,"MIT","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Flinkedin-engagement\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"linkedin","linkedin engagement","engagement","message","limits","send","request","weekly","at","cold","grow","volume","time","safe","write","marketing","plan","how","Budget","networking","2026-11-10 10:12:30",false,"---\nname: linkedin-engagement\ndescription: Use when someone wants to grow reach through comments, replies, groups, or outreach on LinkedIn — a commenting roster, a connection request note, a DM or InMail, a networking plan, or a check on whether their outreach volume is safe. Triggers on \"who should I engage with\", \"write a connection request\", \"cold DM\", \"LinkedIn outreach\", \"networking strategy\", \"how many invites can I send\". Builds a weekly comment roster inside a real time budget, assembles one message at a time and refuses templates, and caps volume against LinkedIn's limits. Nothing is ever sent.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-08-25\n---\n\n# LinkedIn Engagement — comments first, outreach second\n\nFrom a standing start your posts reach almost nobody, and publishing harder does not fix it.\nA substantive comment on a post that already has an audience puts your name, headline, and a\nparagraph of thinking in front of people already reading about your subject, for six minutes\nof work — the cheapest distribution on the platform, and the most badly used.\n\n**Nothing here sends anything** — no credentials, no API calls. Automated connecting,\nmessaging, commenting, liking, and sharing are prohibited by User Agreement §8.2.\n\n## Workflow\n\n**1. Build the comment roster.** Name 8-12 accounts they would read anyway, with audience\noverlap and rough size tier, then:\n\n```bash\npython3 scripts\u002Fcomment_target_planner.py --account \"Priya Raman:5:4:larger\" \\\n  --account \"Tomas Lind:5:3:peer\" --minutes-per-day 18 --output human\n```\n\nTiers are `huge` (10x+, crowded), `larger` (2-10x, the best ratio), `peer` (~1x, where\nreciprocity compounds), `smaller` (goodwill). The roster caps any account at twice a week —\ncommenting daily on one person reads as following them around — and keeps the huge tier under\nhalf of any day. It builds the roster, never the comments: a generated comment is exactly\nwhat §8.2 names, and it is recognisable anyway.\n\n**2. Outreach — check the volume before writing anything.**\n\n```bash\npython3 scripts\u002Foutreach_volume_guard.py --invites 20 --pending 5 --minutes 120 \\\n  --acceptance 0.42 --output human\n```\n\nExit 0 safe \u002F 2 tight \u002F 3 over a cap or the time budget \u002F **4 refused** above 40 invitations\na day, because nobody reads that many profiles and writes that many specific lines. Pending\ninvitations count against the weekly limit (observed around 100), and acceptance below 20% is\na stop signal — it is the pattern LinkedIn reviews, and the targeting is wrong.\n\n**3. Write one message, for one person.**\n\n```bash\npython3 scripts\u002Foutreach_message_builder.py --type connection \\\n  --recipient \"Priya\" --specific-line \"...\" --reason \"...\" --output human\n```\n\nIt refuses without a person-specific line, refuses an ask in a first-touch connection note,\nand enforces the 200-character cap (300 with `--premium`). In large third-party samples a\nnote barely moves acceptance (~26.4% either way) but roughly doubles the post-accept reply\nrate: **the note earns the conversation, not the meeting.**\n\n**4. The order that works.** Comment on their work for two weeks. Then invite, referencing\nsomething specific from that reading. Then, after acceptance and a pause, ask once, small.\n\n## Rules\n\n- **Nothing is auto-sent.** Ever. The user pastes and sends, one person at a time.\n- **No engagement pods.** Coordinated reciprocal commenting is inauthentic engagement under\n  §8.2 regardless of who pressed the key. Build a real reciprocity list instead.\n- **Every message carries a line that could only have been written for that person.**\n- **Never paste the same comment twice.** Identical comments at volume are the definition of\n  the thing §8.2 prohibits.\n- **One follow-up, a week later, only with something new to say.**\n- **Agreement is not a comment.** Add the counter-example, the number, or the case where it\n  breaks — or skip the slot.\n\n## Scripts\n\n| Script | Role |\n|---|---|\n| [`scripts\u002Fcomment_target_planner.py`](scripts\u002Fcomment_target_planner.py) | Weekly roster from scored accounts, inside a time budget, with per-account and per-tier caps. |\n| [`scripts\u002Foutreach_message_builder.py`](scripts\u002Foutreach_message_builder.py) | Assembles one message; refuses templates, premature asks, and 14 dead phrases. |\n| [`scripts\u002Foutreach_volume_guard.py`](scripts\u002Foutreach_volume_guard.py) | Caps invitations against the observed weekly limit, pending backlog, acceptance floor, and the hours available. |\n\n## References and assets\n\n- [`references\u002Fcomment_strategy.md`](references\u002Fcomment_strategy.md) — tiers, what a comment competes on, pods, replying to your own posts (7 sources)\n- [`references\u002Foutreach_ethics_and_benchmarks.md`](references\u002Foutreach_ethics_and_benchmarks.md) — the benchmark numbers with their provenance, and the personalisation claim corrected (7 sources)\n\n- [`assets\u002Foutreach_worksheet.md`](assets\u002Foutreach_worksheet.md) — fillable per-person prep sheet\n- [`assets\u002Fexample_outreach.json`](assets\u002Fexample_outreach.json) — input shape for the builder\n\n## Distinct from\n\n- **`linkedin-content`** — writes posts. A comment is a different craft on a different budget.\n- **`marketing-skill\u002Fcold-email`** — email. Different channel, law, and caps.\n- **`business-growth\u002F`, `commercial\u002F`** — sales process and deal economics, not networking.\n\n---\n**Version:** 1.0.0\n","# LinkedIn Engagement — comments first, outreach second\n\nFrom a standing start your posts reach almost nobody, and publishing harder does not fix it.\nA substantive comment on a post that already has an audience puts your name, headline, and a\nparagraph of thinking in front of people already reading about your subject, for six minutes\nof work — the cheapest distribution on the platform, and the most badly used.\n\n**Nothing here sends anything** — no credentials, no API calls. Automated connecting,\nmessaging, commenting, liking, and sharing are prohibited by User Agreement §8.2.\n\n## Workflow\n\n**1. Build the comment roster.** Name 8-12 accounts they would read anyway, with audience\noverlap and rough size tier, then:\n\n```bash\npython3 scripts\u002Fcomment_target_planner.py --account \"Priya Raman:5:4:larger\" \\\n  --account \"Tomas Lind:5:3:peer\" --minutes-per-day 18 --output human\n```\n\nTiers are `huge` (10x+, crowded), `larger` (2-10x, the best ratio), `peer` (~1x, where\nreciprocity compounds), `smaller` (goodwill). The roster caps any account at twice a week —\ncommenting daily on one person reads as following them around — and keeps the huge tier under\nhalf of any day. It builds the roster, never the comments: a generated comment is exactly\nwhat §8.2 names, and it is recognisable anyway.\n\n**2. Outreach — check the volume before writing anything.**\n\n```bash\npython3 scripts\u002Foutreach_volume_guard.py --invites 20 --pending 5 --minutes 120 \\\n  --acceptance 0.42 --output human\n```\n\nExit 0 safe \u002F 2 tight \u002F 3 over a cap or the time budget \u002F **4 refused** above 40 invitations\na day, because nobody reads that many profiles and writes that many specific lines. Pending\ninvitations count against the weekly limit (observed around 100), and acceptance below 20% is\na stop signal — it is the pattern LinkedIn reviews, and the targeting is wrong.\n\n**3. Write one message, for one person.**\n\n```bash\npython3 scripts\u002Foutreach_message_builder.py --type connection \\\n  --recipient \"Priya\" --specific-line \"...\" --reason \"...\" --output human\n```\n\nIt refuses without a person-specific line, refuses an ask in a first-touch connection note,\nand enforces the 200-character cap (300 with `--premium`). In large third-party samples a\nnote barely moves acceptance (~26.4% either way) but roughly doubles the post-accept reply\nrate: **the note earns the conversation, not the meeting.**\n\n**4. The order that works.** Comment on their work for two weeks. Then invite, referencing\nsomething specific from that reading. Then, after acceptance and a pause, ask once, small.\n\n## Rules\n\n- **Nothing is auto-sent.** Ever. The user pastes and sends, one person at a time.\n- **No engagement pods.** Coordinated reciprocal commenting is inauthentic engagement under\n  §8.2 regardless of who pressed the key. Build a real reciprocity list instead.\n- **Every message carries a line that could only have been written for that person.**\n- **Never paste the same comment twice.** Identical comments at volume are the definition of\n  the thing §8.2 prohibits.\n- **One follow-up, a week later, only with something new to say.**\n- **Agreement is not a comment.** Add the counter-example, the number, or the case where it\n  breaks — or skip the slot.\n\n## Scripts\n\n| Script | Role |\n|---|---|\n| [`scripts\u002Fcomment_target_planner.py`](scripts\u002Fcomment_target_planner.py) | Weekly roster from scored accounts, inside a time budget, with per-account and per-tier caps. |\n| [`scripts\u002Foutreach_message_builder.py`](scripts\u002Foutreach_message_builder.py) | Assembles one message; refuses templates, premature asks, and 14 dead phrases. |\n| [`scripts\u002Foutreach_volume_guard.py`](scripts\u002Foutreach_volume_guard.py) | Caps invitations against the observed weekly limit, pending backlog, acceptance floor, and the hours available. |\n\n## References and assets\n\n- [`references\u002Fcomment_strategy.md`](references\u002Fcomment_strategy.md) — tiers, what a comment competes on, pods, replying to your own posts (7 sources)\n- [`references\u002Foutreach_ethics_and_benchmarks.md`](references\u002Foutreach_ethics_and_benchmarks.md) — the benchmark numbers with their provenance, and the personalisation claim corrected (7 sources)\n\n- [`assets\u002Foutreach_worksheet.md`](assets\u002Foutreach_worksheet.md) — fillable per-person prep sheet\n- [`assets\u002Fexample_outreach.json`](assets\u002Fexample_outreach.json) — input shape for the builder\n\n## Distinct from\n\n- **`linkedin-content`** — writes posts. A comment is a different craft on a different budget.\n- **`marketing-skill\u002Fcold-email`** — email. Different channel, law, and caps.\n- **`business-growth\u002F`, `commercial\u002F`** — sales process and deal economics, not networking.\n\n---\n**Version:** 1.0.0\n",{"name":5,"license":15,"metadata":44,"description":7},{"author":45,"updated":46,"version":47,"category":34},"Alireza Rezvani",1787616000000,"1.0.0","main","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Flinkedin-engagement","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6","https:\u002F\u002Fdisha6.6.thenitishkr.in\u002F","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh","www.thenitishkr","thenitishkr | AI • Cyber-security • Research\r\n","2026-11-08 03:33:25",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add Tashima-Tarsh\u002FDisha6.6 --skill linkedin-engagement",{"tool":63,"command":64},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill linkedin-engagement",{"tool":66,"command":67},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill linkedin-engagement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Flinkedin-engagement\u002FSKILL.md",true,[],[72,103,125,152,177,201],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":83,"publishedAt":39},"01M6QRD07D4TGNDK6VJ4EHF8BV","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[78],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,25,102],"youtube full","youtube","full","transcript","search","monitoring","data","Video","Audio","list","files","do","get","age","trigger","URL","for","browsing","youtube transcripts",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":39},"01M6QRCJ3112VYPA97YG7KGMC2","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[110,111,112,113,88,114,115,35,116,117,118,119,33,120,121,122,29,123,124,100],"twitter","x twitter growth","growth","research","content","engineering","web search","competitors","analyze","engine","strategy","use","platform","posting","competitive",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":134,"publishedAt":39},"01M6QRBN3EHQNJY42RERP7A149","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[131],{"categoryNo":132,"categoryName":133,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000023","Skill与智能体开发",[135,33,136,137,138,139,140,141,121,142,143,48,144,145,146,147,148,149,150,151],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","structure","new agent","resources","with","tree","progressive disclosure","author",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":39},"01M6QRB6G8P33PNGAF9Y69EJ9T","wrap-up","Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says \"wrap up\", \"close this out\", \"what do I own now\", \"give me the summary\", \"recap the agent\", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained .\u002Fmy-agent\u002Fagent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[159,160,161,162,163,164,165,166,167,121,168,95,169,170,171,172,173,174,175,176],"wrap up","up","wrap","gemini","deployment","run","file","hardening","closeout","stop","upgrade","founder","close","companion","you","tables","directions","phase",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":184,"publishedAt":39},"01M6QRA5AYC1RBFZ39GTWGS3N8","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[183],{"categoryNo":132,"categoryName":133,"taxonomyType":81,"taxonomyTypeDesc":82},[185,186,187,188,189,137,164,190,191,192,193,194,33,195,94,196,197,198,199,200],"workflow","workflow builder","builder","design","workflows","code","orchestrate","pipeline","loop","multi-agent","context","across","fresh","scripts","judge","claude code workflow",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":207,"publishedAt":39},"01M6QR7QMCZESKQA0ERW1E657M","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[208,209,26,210,211,212,213,214,215,193,216,217,218,219,220,221,96,222,223,176],"review","weekly review","deterministic scripts","reflect","feeds","inventory","open","team","projects","project-management","scanner","conversation","back","project","sprint","cadence"]