Linkedin Warm Tracker
Maintain a one-row-per-person state machine that outputs each person's single next action and due date, sorted by what is due today. Use to run the day's warming and outreach follow-ups so nobody slips through.
Install
$ agentstack add skill-styfinity-linkedin-engine-linkedin-warm-tracker ✓ 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.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-styfinity-linkedin-engine-linkedin-warm-tracker) 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 Warm Tracker
The day-driver for warming and outreach. One row per person, one next action each, nothing leaks.
Inputs
- The current list of people in play with their last touch and last reply state (paste the list or give a path): $ARGUMENTS
- The brief (persona, offer, pains) loads automatically.
Do this
For each person:
- Read their stage: new / warming / connect-sent / accepted / in-conversation / qualifying / booked / cold.
- Read their last touch date and last reply state (replied, no reply yet, went quiet).
- Compute the single NEXT ACTION for that stage. Examples: warming = engage on a recent post; connect-sent (no accept, 4+ days) = withdraw or wait; accepted = send first DM; in-conversation = reply with the next angle; qualifying = book the call; went quiet (7+ days) = one soft re-open then mark cold.
- Compute the DUE date from the last touch plus the stage cadence. Anything overdue is due today.
- Sort the table by due date, soonest first, and within today put the warmest stage (qualifying, in-conversation) at the top.
Output
A table with columns: person, stage, last touch, NEXT ACTION, due. Sorted by due date. Below it, a one-line count of how many rows are due today. End with the single warmest row to action first.
Rules
- One row per person. Every person always gets a next action, even if that action is "mark cold". Nothing leaks.
- This drives the day. It does not send anything. Drafting a message is /linkedin-first-dm; running /linkedin-humanizer on the draft; hot replies go to /linkedin-reply-triager.
- When the action is to send, sending happens only through the connected CLI/MCP layer on the user's own session or provider key, drafts are shown and approved first, and the 20 actions/day cap applies to new accounts.
- No em-dashes. No guaranteed-result promises.
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.