Agent SkillsWingedGuardian/GENesis-AGI › linkedin-comment-strategy

linkedin-comment-strategy

GitHub

指导撰写高价值LinkedIn评论,避免套话。通过加载用户语音风格,生成增补见解、尊重质疑、经验分享或提问等评论,旨在建立专业可见度并促进互动。

src/genesis/skills/linkedin-comment-strategy/SKILL.md WingedGuardian/GENesis-AGI

Trigger Scenarios

要求为LinkedIn帖子写评论 请求帮助回复帖子 询问如何参与LinkedIn互动 希望提高LinkedIn可见度

Install

npx skills add WingedGuardian/GENesis-AGI --skill linkedin-comment-strategy -g -y
More Options

Non-standard path

npx skills add https://github.com/WingedGuardian/GENesis-AGI/tree/main/src/genesis/skills/linkedin-comment-strategy -g -y

Use without installing

npx skills use WingedGuardian/GENesis-AGI@linkedin-comment-strategy

指定 Agent (Claude Code)

npx skills add WingedGuardian/GENesis-AGI --skill linkedin-comment-strategy -a claude-code -g -y

安装 repo 全部 skill

npx skills add WingedGuardian/GENesis-AGI --all -g -y

预览 repo 内 skill

npx skills add WingedGuardian/GENesis-AGI --list

SKILL.md

Frontmatter
{
    "name": "linkedin-comment-strategy",
    "phase": 8,
    "consumer": "cc_foreground",
    "skill_type": "workflow",
    "description": "This skill should be used when the user asks to \"write a comment for this LinkedIn post\", \"help me respond to this post\", \"what should I comment on this\", \"craft a LinkedIn comment\", or when Genesis identifies high-value posts in the user's network worth engaging with. Also triggered by \"how should I engage on LinkedIn\" or \"help me be more visible on LinkedIn\".\n"
}

LinkedIn Comment Strategy

Purpose

Write LinkedIn comments that build genuine professional visibility — not generic "Great post!" noise. Every comment should demonstrate expertise, add value to the conversation, or make the author want to respond. Comments are the highest-ROI LinkedIn activity for building network presence.

Voice Loading

Before writing comments, load the user's voice via voice-master's overlay resolution:

  1. Read ../voice-master/SKILL.md and follow its User Calibration Overlay section to load exemplars and voice-dimensions from the out-of-repo overlay (or template fallback with warning if no overlay).
  2. This skill's medium is social. Select social-medium exemplars from whatever voice-master loads.
  3. Read ../voice-master/references/anti-slop.md — apply the Universal and Professional / LinkedIn sections.

If no overlay is present, voice-master falls back to generic voice guidance and warns — note this in your output.

Comments follow the same voice rules as posts but in compressed form.

Comment Types

1. Add-Value Comment

Extend the post's point with additional insight, a related experience, or a nuance the author didn't cover.

When to use: The post makes a good point that you can genuinely build on. Length: 2-4 sentences. Example pattern: "[Specific agreement with a detail]. In my experience with [specific context], [additional insight]. [Optional: question or implication]."

2. Respectful Challenge

Disagree with or complicate the post's thesis — with reasoning, not contrarianism.

When to use: The post oversimplifies something or misses a key angle. Length: 3-5 sentences. Example pattern: "[Acknowledge the valid part]. Where I'd push back is [specific point] because [evidence/experience]. [What this changes about the conclusion]."

3. Experience Share

Contribute a relevant personal experience that illustrates or complicates the post's point.

When to use: The post resonates with something you've lived through. Length: 3-6 sentences. Example pattern: "[Brief connection to the post]. When I was [specific situation], [what happened]. [What you learned or how it relates]."

4. Question Comment

Ask a genuine question that advances the discussion. Not a rhetorical question for engagement — a question you'd actually want answered.

When to use: The post raises something you're genuinely curious about. Length: 1-3 sentences. Example pattern: "[What specifically triggered the question]. How do you think about [specific aspect]?"

Anti-Slop Rules for Comments

  • NEVER: "Great post, [Name]!" / "Love this!" / "So true!" / "Couldn't agree more!"
  • NEVER: "Thanks for sharing this, [Name]!" without adding substance
  • NEVER: Tag people who aren't part of the conversation
  • NEVER: Use the comment to pivot to self-promotion
  • NEVER: Write a comment longer than the original post
  • NEVER: Start with an emoji
  • Always reference something SPECIFIC from the post (proves you read it)
  • Always add something the author or readers didn't have before

Comment Workflow

  1. Read the post — The user pastes or describes the post content.

  2. Identify the angle — What's the most natural type of comment given the user's expertise and relationship to the topic?

  3. Check relevance — Is this a post worth commenting on? Criteria:

    • Author is someone the user wants to build a relationship with
    • Topic intersects with the user's expertise
    • Post has meaningful engagement potential (not dead)
    • Comment would be genuine, not forced
  4. Draft — Write the comment in voice. Short, specific, adds value.

  5. Anti-slop check — Verify no banned patterns. Verify it references something specific from the post.

Strategic Commenting Guidance

When the user asks for a general commenting strategy (not a specific comment):

  • Target authors: People in the user's target audience or industry who post regularly and engage with comments. Commenting consistently on 5-10 key authors builds more visibility than scattered commenting.

  • Timing: Comment within the first hour of a post going live. Early comments get more visibility as engagement grows.

  • Frequency: 3-5 meaningful comments per day is more effective than 15 generic ones. Quality signals expertise; quantity signals desperation.

  • Reciprocity: When someone comments on the user's posts, prioritize engaging with their content. Builds genuine relationships.

Output Format

post_summary: <brief summary of the post being commented on>
comment_type: <add-value | challenge | experience | question>
comment: |
  <the comment text>
rationale: |
  <why this type and angle were chosen>

References

  • ../voice-master/SKILL.md — Voice authority; follow its User Calibration Overlay section to load social exemplars from the user overlay
  • ../voice-master/references/anti-slop.md — Universal + Professional/LinkedIn anti-slop rules

Version History

  • f9015bb Current 2026-07-05 18:17

Same Skill Collection

.claude/skills/code-intelligence/SKILL.md
.claude/skills/content-publish/SKILL.md
.claude/skills/genesis-development/SKILL.md
.claude/skills/genesis-voice/SKILL.md
.claude/skills/gitnexus/gitnexus-cli/SKILL.md
.claude/skills/gitnexus/gitnexus-debugging/SKILL.md
.claude/skills/gitnexus/gitnexus-exploring/SKILL.md
.claude/skills/gitnexus/gitnexus-guide/SKILL.md
.claude/skills/gitnexus/gitnexus-impact-analysis/SKILL.md
.claude/skills/gitnexus/gitnexus-refactoring/SKILL.md
.claude/skills/shelve/SKILL.md
.claude/skills/unshelve/SKILL.md
.claude/skills/youtube-fetch/SKILL.md
config/gstack-patches/codex-SKILL.md
src/genesis/skills/browser-automation/SKILL.md
src/genesis/skills/debugging/SKILL.md
src/genesis/skills/evaluate/SKILL.md
src/genesis/skills/forecasting/SKILL.md
src/genesis/skills/integrate-module/SKILL.md
src/genesis/skills/lead-generation/SKILL.md
src/genesis/skills/linkedin-content-calendar/SKILL.md
src/genesis/skills/linkedin-dm-outreach/SKILL.md
src/genesis/skills/linkedin-hook-writer/SKILL.md
src/genesis/skills/linkedin-post-writer/SKILL.md
src/genesis/skills/linkedin-profile-optimizer/SKILL.md
src/genesis/skills/obstacle-resolution/SKILL.md
src/genesis/skills/onboarding/SKILL.md
src/genesis/skills/osint/SKILL.md
src/genesis/skills/prospect-researcher/SKILL.md
src/genesis/skills/research/SKILL.md
src/genesis/skills/retrospective/SKILL.md
src/genesis/skills/stealth-browser/SKILL.md
src/genesis/skills/triage-calibration/SKILL.md
src/genesis/skills/user_evaluate/SKILL.md
src/genesis/skills/video-processing/SKILL.md
.claude/skills/deliverable-builder/SKILL.md
.claude/skills/voice-master/SKILL.md
src/genesis/skills/voice-master/SKILL.md

Metadata

Files
0
Version
f9015bb
Hash
07109f9d
Indexed
2026-07-05 18:17

Home - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-13 13:38
浙ICP备14020137号-1 $Map of visitor$