linkedin-engagement
The linkedin-engagement skill automates finding relevant LinkedIn posts, drafting contextual comments with genuine insights, and posting them after user approval. Use this when you need to generate and publish LinkedIn engagement on specific topics while maintaining control through a required approval step before posting. LinkedIn session credentials stored locally in .env enable the workflow to operate without transmitting sensitive data externally.
git clone --depth 1 https://github.com/ZhixiangLuo/10xProductivity /tmp/linkedin-engagement && cp -r /tmp/linkedin-engagement/.cursor/skills/linkedin-engagement ~/.claude/skills/linkedin-engagementSKILL.md
> **Canonical:** `workflows/linkedin_automation/linkedin_engagement.md` (in this repo). This file is a thin pointer for Cursor skill discovery — load the canonical workflow doc for the full agent loop, setup, privacy notes, and risk warning. Read `workflows/linkedin_automation/linkedin_engagement.md` and follow it.
>
Distill a colleague into a reusable AI skill (work + persona) using tool connections — Slack, Slack AI, Jira, GHE, Bitbucket, Confluence, SharePoint, Teams, Outlook, Notion, Linear, Google Docs, and more — without manual paste. Use when the user wants a colleague skill, digital twin of a coworker, or capture of someone's technical voice from workplace systems. Requires tool_connections + 10xProductivity verified_connections (or equivalent .env).
Design and build automation workflows using building blocks — clarify outcomes, decompose by dependencies, reuse prior art, verify each block before chaining, and research when stuck. Covers generic divide-and-conquer (problem framing, observable surfaces, investigation vs shipping, CLI contracts) plus human-like pacing for social and communication platforms. Use when automating multi-step processes across tools or platforms.
Walk through a UI flow once manually and capture a durable interaction map — which DOM elements to click, which network requests they trigger, and what field shapes they expose. Produces a reusable selector+endpoint reference for automation scripts. Use before writing any Playwright block for a JS-heavy SPA (LinkedIn, Figma, Notion, etc.) where selectors and API paths are not obvious from source inspection alone. Three modes: Chrome DevTools Recorder (fastest), Playwright observer (richest), Playwright codegen+trace (most structured).
>
Connect any tool you use at work to your agent — including internal company tools, custom-built systems, deployment portals, incident trackers, internal knowledge bases, HR systems, and commercial tools like Slack, Confluence, Jira, Linear, GitHub, Outlook, Datadog, and PagerDuty. Use when the user wants to set up a tool connection, connect an internal or custom-built tool, or add a new tool integration from scratch.