linkedin-post — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited linkedin-post (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Write LinkedIn posts in a credible practitioner voice with clear mode, audience, and call-to-action control.
Write LinkedIn posts for Mick Pletcher's professional audience in a voice that is direct, technical, and first-person.
lnp for immediate triggeringlinkedin post about...write something for LinkedInTreat lnp as an immediate trigger. Do not ask clarifying questions first unless the source material is missing a critical fact that would change the post.
Audience: IT professionals, automation engineers, AI enthusiasts, enterprise tech practitioners, hiring managers, and peers in the Nashville and CBIZ space.
Tone compared to other platforms:
Infer one of these modes unless the user explicitly asks for a different one:
career updatetechnical lessonproject breakdownopinioncareer update: center the milestone, what changed, and why it matters professionallytechnical lesson: lead with the lesson or result, then show how it was learned or builtproject breakdown: explain the problem, approach, tools, and outcome with enough structure to feel credibleopinion: make the viewpoint clear early and support it with concrete reasoning instead of hot airInfer one of these audience tones unless the user specifies one:
practitionerleadershipbuilderpractitioner: technical, grounded, tool aware, and peer levelleadership: strategic, outcome oriented, and broader in framing without turning corporatebuilder: hands on, iterative, and focused on what was actually made or solvedThe first two lines should create interest without sounding inflated.
Prefer hook styles such as:
Avoid inflated hooks that sound like generic personal branding.
Before finalizing the post, push for:
If the draft only makes vague claims, rewrite it toward specifics instead of amplifying the vagueness.
Hook line
The first 1 to 2 sentences should earn the click in the feed preview. State what was built, solved, or learned. Skip the preamble.
Body
Use 2 to 4 short paragraphs. Explain what it is, why it matters, and how it works at a high level. Include specific tools, numbers, or outcomes where possible. One concrete detail is better than three vague claims.
Closing line
Optional. Use it for what comes next, a short observation, or a fitted CTA when the post would benefit from one.
Hashtags
Use 2 to 3 hashtags on their own line at the end.
Use a CTA only when it fits the post. Infer the best one unless the user specifies it:
hiringnetworkingrepo trafficdiscussionnonehiring: brief note for people who may want to connect or collaborate professionallynetworking: useful when the post is about shared interests or adjacent workrepo traffic: point to the repo or writeup without sounding thirstydiscussion: one grounded prompt that invites real inputnone: default when the post stands best on its ownWhen the user asks for variants, produce:
Keep the core point the same while changing the framing, jargon level, and emphasis.
When the post would clearly land better with supporting media, add a short note after the post (not inside it) suggesting what to attach:
Never invent what an image shows. If no media would help, say nothing.
When the user wants a multi-post series (project writeup, learning log, build diary):
When a short post performed well or the user asks to go longer, expand it into a LinkedIn article draft:
Built an automated morning briefing pipeline in n8n this week.
It pulls crypto prices from CoinGecko, top stories from RSS feeds, and market commentary from Reddit, then sends everything through the Claude API for summarization before delivering a consolidated brief each morning.
The whole thing runs on my Proxmox homelab, exposed via Cloudflare Tunnel. Zero manual steps from wake-up to briefing.
Next phase is integrating live Alpaca portfolio data so the brief includes overnight position changes alongside the news.
#automation #homelab #n8nIf the user is not sure how to use this skill, asks what it needs, or asks for examples:
Minimum useful input:
Example prompts:
Use linkedin-post to turn this project update into a LinkedIn post for technical peers.Write a LinkedIn post about automating endpoint reporting without sounding like a marketer.Show me an example prompt for a credibility focused LinkedIn post.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.