linkedin-comment-writing
Write and audit LinkedIn comments and reply strategies that add professional value, start useful discussion, and increase ethical visibility. Use when drafting comments on LinkedIn posts, replying to comments, improving comment prompts, or planning comment-based engagement without spam.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 1.6k
- Forks
- 483
01 前言 Front Matter
- name
- linkedin-comment-writing
- license
- MIT
- metadata
- { "tags": "linkedin-writing,linkedin,comments,engagement,content-writing,social-media", "version": "0.1.0", "category": "Marketing", "displayName": "LinkedIn Comment Writing" }
- description
- Write and audit LinkedIn comments and reply strategies that add professional value, start useful discussion, and increase ethical visibility. Use when drafting comments on LinkedIn posts, replying to comments, improving comment prompts, or planning comment-based engagement without spam.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 4
- 参考文档references/core/examples.md1.2 KB
- 参考文档references/core/knowledge.md2.5 KB
- 参考文档references/core/rules.md1.5 KB
- 参考文档workflows/write-value-comments.md1.0 KB
03 SKILL.md 正文
LinkedIn Comment Writing
Source Traceability
Primary source: Growth Hacking LinkedIn by Bjorn Radde, especially sections 3.4.4 "Comments", 3.4.8 "Power Engagement", and 3.4.9 "Engagement-purchase". Guidance is transformed and paraphrased.
Reference Routing
| Need | Read |
|---|---|
| Comment model and source notes | references/core/knowledge.md |
| Comment rules and risk checks | references/core/rules.md |
| Comment patterns | references/core/examples.md |
| Daily comment workflow | workflows/write-value-comments.md |
Workflow
- Identify the original post's claim, audience, and conversation state.
- Choose a comment job: extend, clarify, add example, respectfully disagree, ask a better question, or summarize a useful implication.
- Write a comment that can stand alone and adds value to the thread.
- For comments on the user's own posts, reply quickly and keep the conversation substantive.
- Avoid fake, generic, incentivized, or automated engagement.
Output Format
# LinkedIn Comment Drafts
## Context
- Original post topic:
- Comment job:
- Desired tone:
## Draft Options
1. [Comment]
2. [Comment]
3. [Comment]
## Follow-Up
- If author replies:
- If thread turns negative:
- Risk notes:
Quality Bar
- Add a new thought, example, question, or useful synthesis.
- Make disagreement professional and specific.
- Do not write engagement-bait comments.
- Do not recommend pods, purchased comments, or automated comment tools.
04 同仓库更多 Skills
migrate-to-e2e
Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for /migrate-to-e2e, "migrate our tests to e2e", "port these Maestro flows", "move our TesterArmy tests", or when a project has an e2e config and an older suite still running.
e2e
Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.
create-verification-skill
Generate a project-local verify-<app> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for /create-verification-skill, "make a verification skill for this repo", or when a project has no scripted way to prove UI behavior.
deja-search
deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.
deja-reflect
End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.
revid
Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.