When the user wants to create LinkedIn post copy or optimize for LinkedIn. Also use when the user mentions "LinkedIn post," "LinkedIn article," "professional post," "post to LinkedIn," "LinkedIn content," "LinkedIn copy," "B2B LinkedIn," "LinkedIn engagement," or "LinkedIn marketing." For LinkedIn ads, use linkedin-ads.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "linkedin-posts" with this command: npx skills add GetFresh-Ventures/skillsmp-getfresh-ventures-getfresh-ventures-linkedin-posts
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Multi-source data truth resolution using Byzantine fault tolerance and weighted consensus. Reconciles conflicting data across HubSpot, ServiceTitan, GA4, and Google Ads. Derived from ruflo byzantine-coordinator + consensus-coordinator patterns. Use when: data conflicts between systems, metric discrepancies, multi-source validation needed. Skip when: single-source queries, data already verified, no conflicts detected.
Access Fathom meeting transcripts, summaries, and action items via REST API. Covers listing meetings, searching by keyword, extracting transcript content, filtering by date/attendees, and pagination. Use when you need to pull meeting data for reconciliation, intelligence extraction, or cross-referencing call notes.
Access Google Calendar API for event management — list, create, update, delete events. Uses Service Account domain-wide delegation via gfv_service_account.json. Use when: scheduling meetings, checking availability, creating calendar events. Skip when: just looking at meeting history (use fathom-api for transcripts).
Access HubSpot CRM API for deals, contacts, companies, and engagements. Covers PAT auth, deal pipeline queries, contact search, and Supabase ingest. Use when: querying CRM data, checking deal status, enriching contacts, syncing to PIL. Skip when: data already in PIL ontology (check there first).