Install
$ agentstack add skill-styfinity-linkedin-engine-linkedin-connection-note ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
LinkedIn Connection Note
A connection note is not a pitch. It earns the accept by referencing one real, specific detail. This skill writes two short variants so the operator can pick.
Inputs
- The target profile (name, role, company) and how you found them, plus the one real hook (a post they wrote, a comment, a mutual, a signal): $ARGUMENTS
- The brief (persona tone, pains, voice) loads automatically.
Do this
- Pull the single most specific real hook from the input. If there is no real hook, say so and ask for one. Do not invent it.
- Write Variant A: a connection note that opens on that exact detail. Under 200 characters. No pitch.
- Write Variant B: a different angle on the same hook, or a second real detail. Under 200 characters. No pitch.
- Count the characters in each. If either is over 200, cut it down and recount.
Output
Variant A and Variant B, each on its own line, with the exact character count in brackets after it (for example: [184 chars]). One line below: each is draft only, pick one, then approve before it goes out.
Rules
- Under 200 characters, counted and shown. No exceptions.
- No pitch, no ask, no offer. The note buys the accept, nothing more.
- No "I came across your profile", no "hope you're well", no exclamation marks.
- No em-dashes. Use a comma, a period, or " - ".
- Reads like one peer messaging another about a real thing they noticed.
- Draft only. Claude drafts, the operator approves and sends.
- Sending happens only through the connected opt-in CLI/MCP layer wired to your own LinkedIn session or provider key, and is hard-capped at 20 actions per day on new accounts. This skill never sends.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: styfinity
- Source: styfinity/linkedin-engine
- License: MIT
- Homepage: https://styfinity.com
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.