[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CWA2PEABZ6VTYER83TC72X":3,"skill-same:01M7CWA2PEABZ6VTYER83TC72X":60},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7CWA2PEABZ6VTYER83TC72X","linkedin-employee-advocacy",null,"Stand up and run a LinkedIn employee advocacy program for a marketing or sales team. Covers 14-day launch playbook, brand-guideline governance, per-post time budget, cadence benchmarks, and team ROI (reach, engagement, pipeline). Triggers on \"employee advocacy\", \"get the team posting\", \"scale LinkedIn across team\", \"advocacy ROI\". Not for planning one person's own calendar (use linkedin-content-planner).","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Flinkedin-skills\u002Fskills\u002Flinkedin-employee-advocacy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: linkedin-employee-advocacy\ndescription: \"Stand up and run a LinkedIn employee advocacy program for a marketing or sales team. Covers 14-day launch playbook, brand-guideline governance, per-post time budget, cadence benchmarks, and team ROI (reach, engagement, pipeline). Triggers on \\\"employee advocacy\\\", \\\"get the team posting\\\", \\\"scale LinkedIn across team\\\", \\\"advocacy ROI\\\". Not for planning one person's own calendar (use linkedin-content-planner).\"\n---\n\n# LinkedIn Employee Advocacy\n\nStand up a marketing-team LinkedIn advocacy program that scales without killing authenticity. Employee posts get **8x more engagement** than brand-page posts — this skill operationalizes that advantage.\n\n## When to use\n\n- Marketing leader wants to get their team posting on LinkedIn\n- User is planning an advocacy program launch\n- Team is posting but output is inconsistent \u002F off-brand \u002F low-engagement\n- Need ROI measurement framework for an existing program\n- Requests: \"how do I get the team posting\", \"launch advocacy\", \"scale LinkedIn across 10 people\"\n\n## Input\n\n- Team size (5-50 typical)\n- Marketing goal (reach \u002F pipeline \u002F recruiting \u002F thought leadership)\n- Current state (everyone silent \u002F some active \u002F inconsistent)\n- Brand guideline constraints\n\n## Output\n\n- **14-day launch plan** (if cold-starting)\n- **Operating model** (voice capture, ideation, approval, posting, measurement)\n- **Cadence targets** per team member (realistic, not punishing)\n- **KPI dashboard spec** (team reach, engagement, pipeline attribution)\n- **Governance playbook** (brand safety without blocking velocity)\n\n## Four operating principles\n\n1. **Scale authentically.** Individuals compose in their own voice, not corporate language. Corporate-tone team posts underperform authentic voice 3x.\n2. **Maintain control.** Brand guidelines integrated into the workflow. Review step is **optional, not blocking** — high-trust roles bypass review entirely.\n3. **Remove friction.** Per-post time budget: **5 minutes**. Anything more and the program dies in week 3.\n4. **Prove ROI.** Track team reach, engagement, pipeline impact. Without attribution, the program gets cut at the first budget review.\n\n## Benchmarks\n\n- **Launch target:** team posting within **14 days**\n- **Active team size benchmark:** 8-11 members\n- **Output benchmark:** 70+ posts\u002Fweek (at 8 members) or 3-5 posts\u002Fmember\u002Fweek\n- **Per-post time budget:** 5 minutes\n- **Team touchpoint math:** 11 people × 3 posts\u002Fweek × 300 min impressions = **40,000 monthly touchpoints** baseline\n- **Employee vs. brand page:** 8x more engagement, 6-8x more reach on personal posts\n\n## 14-day launch playbook\n\n### Days 1-3: Voice capture\n- Short interview with each team member (5-10 min) to extract their actual voice\n- Identify their domain expertise and 2-3 content pillars\n- Set realistic individual cadence (some commit to 1\u002Fweek, some 3\u002Fweek — don't force uniformity)\n\n### Days 4-7: First posts\n- Everyone ships their first post, drafted in their voice\n- Marketing reviews only for brand safety (never for style)\n- Celebrate every first post internally — social proof unlocks the next team member\n\n### Days 8-10: Ideation pipeline\n- Set up a shared ideation source (newsletter digest, trending-topics feed, internal wins)\n- Each team member gets 5-10 topic suggestions per week\n- They pick, not assigned\n\n### Days 11-14: Rhythm lock\n- Establish cadence: each team member publishes on fixed days\u002Ftimes\n- Set up KPI dashboard (see below)\n- Run first weekly review\n\n## Governance: brand-safe without being blocked\n\n**What marketing reviews:**\n- Factual claims about the company \u002F products \u002F customers\n- Confidential info\n- Legal\u002Fcompliance issues (finance, health, regulated industries)\n\n**What marketing does NOT review:**\n- Personal voice, tone, style\n- Opinions the team member has about their own work\n- Formatting, hashtags, emoji choices\n- Topic selection (within pillars)\n\n**The review SLA:** \u003C4 business hours. Anything longer and the post is dead (posts go stale in the news cycle).\n\n## ROI measurement\n\n### Per-person metrics (content quality)\n- Impressions per post\n- Engagement rate (reactions + comments + shares \u002F impressions)\n- Comments (depth signal)\n- Profile views attributed to post\n\n### Team-level metrics (program health)\n- Total team reach\n- Total team engagement\n- Individual contribution rank (leaderboard)\n- Active members \u002F total members (participation rate)\n\n### Business metrics (pipeline impact)\n- Inbound DMs sourced from LinkedIn content\n- Meetings booked from LinkedIn\n- Closed-won deals with LinkedIn as first-touch channel\n- Employee referrals sourced from LinkedIn (if recruiting is a goal)\n\n## Anti-patterns\n\n- **Copy-paste corporate posts across team accounts** — LinkedIn detects this, suppresses all of them\n- **Ghostwriting that erases the writer's voice** — reads as fake\n- **Mandatory posting cadence without individual calibration** — program dies in 6 weeks\n- **Approval loops >24h** — makes the program feel like work\n- **Measuring only vanity metrics** — program gets cut without pipeline attribution\n- **All-same pillars across team** — redundancy kills team reach (360Brew penalizes clustering)\n\n## Resources\n\n- `references\u002Fadvocacy-principles.md` — the 4 operating principles with examples\n- `references\u002Fteam-cadence-matrix.md` — realistic cadence by role + seniority\n- `references\u002Fgovernance-playbook.md` — what to review, what not to, SLA\n\n## Related skills\n\n- `linkedin-post-writer` — each team member uses this for individual drafts\n- `linkedin-profile-optimizer` — team profiles should match before the program launches (otherwise profile clicks convert poorly)\n- `linkedin-content-planner` — each team member gets their own pillar mix\n- `linkedin-thread-monitor` — track which team members' comments drive author replies\n- `linkedin-engager-analytics` — see who's engaging with each team member's posts\n- `linkedin-comment-drafter` — its **reshare mode** is how team members amplify a brand or colleague post to their own feed with a short take (`lib.repost(post_url, commentary)` on approval); the cleanest advocacy action after an original post\n","# LinkedIn Employee Advocacy\n\nStand up a marketing-team LinkedIn advocacy program that scales without killing authenticity. Employee posts get **8x more engagement** than brand-page posts — this skill operationalizes that advantage.\n\n## When to use\n\n- Marketing leader wants to get their team posting on LinkedIn\n- User is planning an advocacy program launch\n- Team is posting but output is inconsistent \u002F off-brand \u002F low-engagement\n- Need ROI measurement framework for an existing program\n- Requests: \"how do I get the team posting\", \"launch advocacy\", \"scale LinkedIn across 10 people\"\n\n## Input\n\n- Team size (5-50 typical)\n- Marketing goal (reach \u002F pipeline \u002F recruiting \u002F thought leadership)\n- Current state (everyone silent \u002F some active \u002F inconsistent)\n- Brand guideline constraints\n\n## Output\n\n- **14-day launch plan** (if cold-starting)\n- **Operating model** (voice capture, ideation, approval, posting, measurement)\n- **Cadence targets** per team member (realistic, not punishing)\n- **KPI dashboard spec** (team reach, engagement, pipeline attribution)\n- **Governance playbook** (brand safety without blocking velocity)\n\n## Four operating principles\n\n1. **Scale authentically.** Individuals compose in their own voice, not corporate language. Corporate-tone team posts underperform authentic voice 3x.\n2. **Maintain control.** Brand guidelines integrated into the workflow. Review step is **optional, not blocking** — high-trust roles bypass review entirely.\n3. **Remove friction.** Per-post time budget: **5 minutes**. Anything more and the program dies in week 3.\n4. **Prove ROI.** Track team reach, engagement, pipeline impact. Without attribution, the program gets cut at the first budget review.\n\n## Benchmarks\n\n- **Launch target:** team posting within **14 days**\n- **Active team size benchmark:** 8-11 members\n- **Output benchmark:** 70+ posts\u002Fweek (at 8 members) or 3-5 posts\u002Fmember\u002Fweek\n- **Per-post time budget:** 5 minutes\n- **Team touchpoint math:** 11 people × 3 posts\u002Fweek × 300 min impressions = **40,000 monthly touchpoints** baseline\n- **Employee vs. brand page:** 8x more engagement, 6-8x more reach on personal posts\n\n## 14-day launch playbook\n\n### Days 1-3: Voice capture\n- Short interview with each team member (5-10 min) to extract their actual voice\n- Identify their domain expertise and 2-3 content pillars\n- Set realistic individual cadence (some commit to 1\u002Fweek, some 3\u002Fweek — don't force uniformity)\n\n### Days 4-7: First posts\n- Everyone ships their first post, drafted in their voice\n- Marketing reviews only for brand safety (never for style)\n- Celebrate every first post internally — social proof unlocks the next team member\n\n### Days 8-10: Ideation pipeline\n- Set up a shared ideation source (newsletter digest, trending-topics feed, internal wins)\n- Each team member gets 5-10 topic suggestions per week\n- They pick, not assigned\n\n### Days 11-14: Rhythm lock\n- Establish cadence: each team member publishes on fixed days\u002Ftimes\n- Set up KPI dashboard (see below)\n- Run first weekly review\n\n## Governance: brand-safe without being blocked\n\n**What marketing reviews:**\n- Factual claims about the company \u002F products \u002F customers\n- Confidential info\n- Legal\u002Fcompliance issues (finance, health, regulated industries)\n\n**What marketing does NOT review:**\n- Personal voice, tone, style\n- Opinions the team member has about their own work\n- Formatting, hashtags, emoji choices\n- Topic selection (within pillars)\n\n**The review SLA:** \u003C4 business hours. Anything longer and the post is dead (posts go stale in the news cycle).\n\n## ROI measurement\n\n### Per-person metrics (content quality)\n- Impressions per post\n- Engagement rate (reactions + comments + shares \u002F impressions)\n- Comments (depth signal)\n- Profile views attributed to post\n\n### Team-level metrics (program health)\n- Total team reach\n- Total team engagement\n- Individual contribution rank (leaderboard)\n- Active members \u002F total members (participation rate)\n\n### Business metrics (pipeline impact)\n- Inbound DMs sourced from LinkedIn content\n- Meetings booked from LinkedIn\n- Closed-won deals with LinkedIn as first-touch channel\n- Employee referrals sourced from LinkedIn (if recruiting is a goal)\n\n## Anti-patterns\n\n- **Copy-paste corporate posts across team accounts** — LinkedIn detects this, suppresses all of them\n- **Ghostwriting that erases the writer's voice** — reads as fake\n- **Mandatory posting cadence without individual calibration** — program dies in 6 weeks\n- **Approval loops >24h** — makes the program feel like work\n- **Measuring only vanity metrics** — program gets cut without pipeline attribution\n- **All-same pillars across team** — redundancy kills team reach (360Brew penalizes clustering)\n\n## Resources\n\n- `references\u002Fadvocacy-principles.md` — the 4 operating principles with examples\n- `references\u002Fteam-cadence-matrix.md` — realistic cadence by role + seniority\n- `references\u002Fgovernance-playbook.md` — what to review, what not to, SLA\n\n## Related skills\n\n- `linkedin-post-writer` — each team member uses this for individual drafts\n- `linkedin-profile-optimizer` — team profiles should match before the program launches (otherwise profile clicks convert poorly)\n- `linkedin-content-planner` — each team member gets their own pillar mix\n- `linkedin-thread-monitor` — track which team members' comments drive author replies\n- `linkedin-engager-analytics` — see who's engaging with each team member's posts\n- `linkedin-comment-drafter` — its **reshare mode** is how team members amplify a brand or colleague post to their own feed with a short take (`lib.repost(post_url, commentary)` on approval); the cleanest advocacy action after an original post\n",{"name":5,"description":7},"main","a73152352c0612252131e5cf84e91312a6cf17dc","marketing\u002Flinkedin-skills\u002Fskills\u002Flinkedin-employee-advocacy","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill linkedin-employee-advocacy",{"tool":38,"command":39},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill linkedin-employee-advocacy",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill linkedin-employee-advocacy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Flinkedin-skills\u002Fskills\u002Flinkedin-employee-advocacy\u002FSKILL.md",true,[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fadvocacy-principles.md","REFERENCE","参考文档",3462,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Flinkedin-skills\u002Fskills\u002Flinkedin-employee-advocacy\u002Freferences\u002Fadvocacy-principles.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fgovernance-playbook.md",5482,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Flinkedin-skills\u002Fskills\u002Flinkedin-employee-advocacy\u002Freferences\u002Fgovernance-playbook.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fteam-cadence-matrix.md",3788,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Flinkedin-skills\u002Fskills\u002Flinkedin-employee-advocacy\u002Freferences\u002Fteam-cadence-matrix.md",[61,68,75,83,90,97],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]