Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

biostartechnologylinkedin

v1.0.0

Write high-performing, persuasive, and authentic LinkedIn posts across any professional niche. Uses research-backed hooks, proven post structures, and Linked...

0· 214·0 current·0 all-time
byClayton Silva@claytonbernardodasilva

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for claytonbernardodasilva/biostartechnologylinkedin.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "biostartechnologylinkedin" (claytonbernardodasilva/biostartechnologylinkedin) from ClawHub.
Skill page: https://clawhub.ai/claytonbernardodasilva/biostartechnologylinkedin
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install biostartechnologylinkedin

ClawHub CLI

Package manager switcher

npx clawhub@latest install biostartechnologylinkedin
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The SKILL.md content matches the described purpose (creating LinkedIn posts, templates, hooks, and first-comment ideas). However, registry metadata (skill name 'biostartechnologylinkedin', owner ID, and version) does not match the embedded _meta.json (different ownerId, slug 'linkedin-post-engine', and a different version). This metadata mismatch is unexpected and should be explained by the publisher.
Instruction Scope
Runtime instructions are purely about drafting LinkedIn content: asking for audience, goal, proof, producing hooks/posts/variants. There are no instructions to read local files, access environment variables, or transmit data to third-party endpoints beyond a non-actionable link to linkedin.com.
Install Mechanism
Instruction-only skill with no install spec, no binaries, and no code files that would be written to disk. This is the lowest-risk install mechanism.
Credentials
The skill declares no required environment variables, no credentials, and no config paths. That is proportionate to its stated function (content generation).
Persistence & Privilege
always is false and the skill is user-invocable. disable-model-invocation is false (normal). The skill does not request elevated or persistent privileges.
What to consider before installing
This skill appears to genuinely implement a LinkedIn post-writing template and is instruction-only (lower technical risk). However, the package metadata contains inconsistencies (different owner ID, slug, and version inside _meta.json vs registry metadata). Before installing: 1) confirm the publisher identity and why metadata differs (could be a repackaging or mistake); 2) prefer installing only if you trust the publisher; 3) be cautious about later versions or add-ons that might request LinkedIn credentials or post-on-your-behalf access—do not supply OAuth tokens or passwords unless you verify the integration endpoint and permissions; 4) test generated outputs in a safe/sandbox account and avoid providing real client-sensitive data to the skill. If the publisher cannot explain the metadata mismatch, treat the package as untrusted.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

💼 Clawdis
latestvk974fhvsz5tcy90pbzakc2zvpn8332r3
214downloads
0stars
1versions
Updated 22h ago
v1.0.0
MIT-0

READ BEFORE USE

HOW TO USE THIS SKILL EFFECTIVELY

READ BEFORE USE

LinkedIn Post Engine

Overview

This skill helps you create strong LinkedIn posts that feel human, useful, and credible.

It combines:

  • proven hook frameworks,
  • clear narrative structures,
  • proof-first writing,
  • and practical CTA design.

Keywords: linkedin, thought leadership, personal brand, founder posts, b2b content, storytelling, case study, hooks, engagement, authority


Process Workflow

Phase 1: Audience + Positioning (CRITICAL)

Before writing, define:

  1. Audience — Who is this for? (founders, recruiters, engineers, operators, marketers, sales leaders, etc.)
  2. Goal — Reach, authority, leads, hiring, trust, replies, profile visits?
  3. Core insight — What is the one thing worth remembering?
  4. Proof — What makes this believable (numbers, before/after, constraints, mistakes, outcomes)?

If proof is missing, use placeholders like [X%], [Y hours] and request exact values.

Phase 2: Structure + Hook Selection

Choose a format first, then write:

  • Story
  • Framework
  • Contrarian
  • Case study
  • Teardown
  • Build-in-public

Then select 2-3 hooks and finalize one.

Phase 3: Draft + Polish

  • Keep paragraphs short (1-2 lines)
  • Front-load specifics
  • Remove generic filler
  • End with one clear CTA
  • Add 3-6 hashtags max

LinkedIn Feed Dynamics (Practical)

What usually performs best:

  1. Strong first two lines (stops the scroll)
  2. Specificity (numbers > adjectives)
  3. Credible vulnerability (mistakes + lessons)
  4. Clear structure (easy to skim on mobile)
  5. Conversation CTA (quality comments over empty likes)

Avoid:

  • Buzzword soup
  • Generic motivation posts
  • Overlong hashtag blocks
  • Fake certainty without evidence

Hook Formulas (Most Important)

The Contrarian Hook

  • “Most people do [X]. That’s exactly why they stay stuck.”
  • “Unpopular opinion: [industry belief] is outdated.”

The Specific Result Hook

  • “In [timeframe], we improved [metric] by [number]. Here’s how.”
  • “We cut [cost/time] by [X%]. Not with a new tool—by changing this one workflow.”

The Mistake Hook

  • “I made this [role]-mistake for months. It cost us [outcome].”
  • “We shipped the wrong thing fast. Here’s what fixed it.”

The Framework Hook

  • “The [3-step/4-step] framework I use for [outcome].”
  • “If I had to restart as [role], I’d follow these 5 rules.”

The Question Hook

  • “Would you let your team do [X] without [Y]?”
  • “What’s your biggest bottleneck in [domain] right now?”

High-Performing Post Formats

1) “This runs now” (Operational Story)

Best for real systems, workflows, and automations.

Template:

  • bold claim
  • “Not as a demo. As an actual [responsibility/workflow].”
  • “Here’s what it does:” with 4-6 concrete bullets
  • measurable result
  • perspective line + CTA question

2) Case Study

Template:

  • starting problem
  • constraints
  • intervention
  • before/after metrics
  • key lesson
  • optional “comment TEMPLATE” CTA

3) Contrarian Opinion

Template:

  • challenge popular view
  • explain why it fails in practice
  • give 3 practical principles
  • ask a polarizing but constructive question

4) Framework Post

Template:

  • name framework
  • 3-5 steps
  • one mistake to avoid
  • one practical “do this today” action

5) Build-in-Public Update

Template:

  • what shipped this week
  • what worked
  • what broke
  • what changed next
  • ask for informed feedback

Persuasion Principles

Use these to increase clarity and trust:

  • Specificity: “Saved 3.2 hours/week” beats “saved time.”
  • Mechanism: Explain how, not just outcomes.
  • Credibility: Mention tradeoffs, not only wins.
  • Relevance: Tie insight to audience reality.
  • Clarity: One post = one core idea.

Writing Rules

  • Hook in first 1-2 lines
  • 1-2 sentence paragraphs
  • Prefer plain language over hype
  • Use emojis sparingly as section markers
  • Keep claims realistic
  • Never invent outcomes, clients, or credentials

Hashtags:

  • 3-6 max
  • niche + function + audience mix
  • avoid spammy broad tags only

Output Contract

By default, provide:

  1. 3 hook options
  2. 1 full post
  3. 1 spicier variant
  4. 3 first-comment ideas (to deepen discussion)

Optional on request:

  • NL / EN / NL-EN mixed variants
  • X/Twitter adaptation
  • Short + long versions
  • Carousel text outline

Quick Prompt Template

When user gives a raw idea, ask/fill:

  • Audience:
  • Goal:
  • Topic:
  • Proof points:
  • Tone:
  • CTA preference:

Then generate outputs per contract above.


Common Pitfalls to Avoid

  • Generic “AI changed everything” without concrete examples
  • No proof signals
  • Too many ideas in one post
  • CTA mismatch (asking for leads on a pure thought-leadership post)
  • Over-formatting with noisy symbols

Execution Checklist

Before finalizing:

  • Hook is strong and specific
  • Core claim is clear
  • Includes at least one proof signal
  • Easy to skim on mobile
  • CTA invites real conversation
  • Hashtags are relevant and limited
  • Tone feels authentic to author

Comments

Loading comments...