Home / linkmcp-io / linkmcp · GitHub

linkedin-account-brief SKILL.md skillA

linkedin-account-brief from linkmcp-io/linkmcp is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add linkmcp-io/linkmcp/linkedin-account-brief@v1.0.0

Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: linkmcp-io/linkmcp
Path: skills/linkedin-account-brief/SKILL.md
Versions recorded: 1
Latest version: v1.0.0, committed Oct 12, 2026
Size: 5,089 bytes
Repository stars: 3
License: MIT

Prepare a one-page account brief before a sales call, demo or meeting, with LinkedIn data from the LinkMCP connector. The brief covers the company and its recent posts, the people the user will meet and their posts, and shared connections. It also gives talking points and questions to ask. Use when the user asks to research a company or a person on LinkedIn before a call. Also use it when the user asks for call prep, meeting prep or an account brief with LinkedIn data. Reads LinkedIn data only…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# LinkedIn account brief

Make a short brief that the user can read in two minutes before a call. Use only facts from the LinkMCP tools and from the user. Mark each guess as a guess.

## Rules

- This skill only reads. Do not send messages or connection requests. Do not post, comment or react.
- If the user asks for an introduction message, write it in the chat as a draft. Do not send it. A send is a separate request, and it needs the user's approval of that exact message.
- Do not make a LinkedIn URL from the name of a person. Ask the user for the URL, or use people search (step 4).
- Do not look up email addresses or phone numbers. The brief does not need them.
- LinkMCP lookups can use part of the monthly LinkMCP usage of the user. Do not request the same data two times.

## Tools

This skill uses these LinkMCP tools. All of them only read: `linkedin_get_company`, `linkedin_get_company_posts`, `linkedin_get_profile`, `linkedin_get_person_posts`, `linkedin_search_people`, `linkedin_get_shared_connections`.

Your client can show a tool name with a prefix, for example `mcp__linkmcp__linkedin_get_company`. Use the tool whose name ends with the name in this skill.

## Steps
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add linkmcp-io/linkmcp/linkedin-account-brief@sha256:ce7ab1d5aa1f7b4f

The line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_fk2hbjazs2lec6xl.svg)](https://markdownregistry.com/a/art_fk2hbjazs2lec6xl)

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Oct 12, 2026.

version	committed	commit	size	audit
v1.0.0 latest	2026-10-12	4139e63	5,089 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (5089 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

linkmcp-io/linkmcp · 3 stars · license MIT · pushed 2026-10-26 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_fk2hbjazs2lec6xl
GET https://markdownregistry.com/api/v1/resolve?ref=linkmcp-io/linkmcp/linkedin-account-brief
GET https://markdownregistry.com/api/v1/blob/ce7ab1d5aa1f7b4f8aeaeaf23f6f80e943d4375b8862f7d4bdf4c225315bb55c

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.