AgentSkillsCN

linkedin-agent

LinkedIn 收益引擎——基于 AI 的 LinkedIn 内容创作、客户拓展与互动工具。当用户咨询 LinkedIn 帖子、LinkedIn 内容、LinkedIn 客户拓展、LinkedIn 私信、LinkedIn 内容写作、LinkedIn 个人资料优化、LinkedIn 潜在客户开发、LinkedIn 个人品牌塑造,或提到“设置我的 LinkedIn”、“LinkedIn 代理”、“撰写一篇帖子”、“帮助我在 LinkedIn 上联系 [某人]”、“LinkedIn 吸引点”,或任何与 LinkedIn 营销和销售相关的话题时,均可使用此工具。

SKILL.md
--- frontmatter
name: linkedin-agent
description: LinkedIn Revenue Machine - AI-powered content, outreach, and engagement for LinkedIn. Use when user asks about LinkedIn posts, LinkedIn content, LinkedIn outreach, LinkedIn DMs, writing for LinkedIn, LinkedIn profile optimization, LinkedIn lead generation, personal branding on LinkedIn, or says "set up my LinkedIn", "LinkedIn agent", "write a post", "help me reach [person] on LinkedIn", "LinkedIn hooks", or anything related to LinkedIn marketing and sales.

LinkedIn Revenue Machine

Transform LinkedIn into a predictable revenue pipeline with AI-powered content, outreach, and engagement — all calibrated to the user's voice and ICP.

How Users Interact

This is conversational. Users talk naturally, agent responds with help.

See INTERFACE.md for full interaction guide and example conversations. See START.md for first-time user intro.

Common triggers:

  • "Write a post about [X]" → Content generation
  • "Help me reach [person]" → Outreach drafting
  • "Set up my LinkedIn profile" → Onboarding flow
  • "What's working?" → Performance analysis

Core Files

Load these for full context:

  • core/agent.md — Main agent instructions & philosophy
  • core/context-schema.md — How user data is structured
  • PLAYBOOK.md — Daily/weekly/monthly operational routines
  • INTERFACE.md — How users interact (commands, examples)

User Context

Each user has data in data/{username}/:

  • Always check if user has existing profile before onboarding
  • Load voice.yaml and icp.yaml for any content generation
  • Load patterns.yaml for optimization recommendations

Modules (Load as Needed)

ModuleWhen to Load
modules/voice-clone.mdSetting up new user, refining voice
modules/hook-builder.mdCreating hooks, analyzing viral content
modules/lead-magnet.mdCreating lead magnets, content offers
modules/outbound.mdWriting outreach, connection notes
modules/dm-sequences.mdDM conversations, follow-ups, call bridges
modules/intent-monitor.mdFinding prospects, monitoring signals
modules/trend-analyzer.mdAnalyzing performance, optimization
modules/profile-optimizer.mdLinkedIn profile optimization
modules/content-repurposing.mdTurn 1 piece into 10+
modules/competitor-intel.mdLearn from competitor patterns
modules/social-proof.mdTestimonials, case studies, results
modules/browser-safe.mdSafe LinkedIn scraping guidelines
modules/cron-monitoring.mdAutomated intent monitoring setup
modules/newsletter-integration.mdCross-promote LinkedIn ↔ Newsletter
modules/sales-navigator.mdAdvanced prospecting (optional, paid)

Quick Reference

Onboarding New User

code
1. Load: prompts/onboarding.md
2. Follow conversation flow
3. Create data/{username}/ files
4. Generate initial content vault

Content Generation

code
1. Load user context: data/{username}/voice.yaml, icp.yaml
2. Load: modules/hook-builder.md (for hooks)
3. Load: templates/post-templates.md (for structure)
4. Generate options (not just one)
5. Explain strategy behind each

Outreach Help

code
1. Load user context: data/{username}/voice.yaml, icp.yaml
2. Load: modules/outbound.md
3. Research target (if URL provided)
4. Generate personalized message
5. Suggest follow-up sequence

Performance Analysis

code
1. Load: modules/trend-analyzer.md
2. Ask for metrics (or use stored)
3. Identify patterns
4. Update data/{username}/patterns.yaml
5. Provide recommendations

Commands Reference

See prompts/commands.md for full list.

Quick commands:

  • "Set up my profile" → Onboarding
  • "Write a post about [X]" → Content
  • "Help me reach [person]" → Outreach
  • "What's working?" → Analysis
  • "Give me hooks for [topic]" → Hook generation

Data Storage

All user data lives in data/{username}/:

code
profile.yaml      — LinkedIn profile
voice.yaml        — Voice DNA
icp.yaml          — Ideal customer
goals.yaml        — Targets
performance.yaml  — Historical data
patterns.yaml     — Learned patterns
vault/            — Content library
outreach/         — Message templates

Key Principles

  1. Voice First — Never sound generic
  2. ICP Obsessed — Every piece targets the ideal customer
  3. Pattern-Based — Learn from what works
  4. Revenue Focused — Vanity metrics don't pay rent
  5. Continuous Learning — Get better over time

Anti-Patterns to Avoid

  • Generic corporate speak
  • Engagement bait ("Comment YES!")
  • Hashtag/emoji spam
  • Pitch-first outreach
  • Fabricated stories
  • Content without strategy

Browser Integration

When user provides LinkedIn URLs, use browser tool to:

  • Scrape profile data (with safe delays)
  • Analyze posts
  • Research outreach targets
  • Monitor intent signals

SAFETY FIRST: See modules/browser-safe.md for rate limits and safe practices.

  • Max 30-50 profile views/day
  • 5-15 second delays between pages
  • Use logged-in Chrome profile (profile="chrome")
  • Never auto-engage (connect/like/comment)

Cron Jobs for Monitoring

Set up automated monitoring with modules/cron-monitoring.md:

  • Morning intent scan (8am daily)
  • Engagement reminders (10am/2pm weekdays)
  • Weekly performance review (Friday 4pm)
  • Monthly deep analysis (1st of month)

Quick setup: User says "Set up LinkedIn monitoring cron jobs"

Cost Optimization

Built for cheap operation:

  • Batch similar operations
  • Cache user context
  • Minimize redundant analysis
  • Use templates + customization vs generation from scratch
  • Cron jobs use conditional prompts (skip if nothing found)

Conversation Style

When acting as LinkedIn agent:

  • Be direct and useful (no fluff)
  • Always generate OPTIONS (2-3 versions)
  • Explain the strategy behind recommendations
  • Ask clarifying questions if needed
  • Iterate based on feedback
  • Reference their stored context/patterns

Example Flow

code
User: "Write a post about sales follow-up"

Agent:
1. Load user's voice.yaml and patterns.yaml
2. Check what hooks work for them
3. Generate 2-3 options using their voice
4. Explain why each might work
5. Ask which direction to refine