linkedin-content Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower

Source:

SHA-256:

linkedin-content is an AI agent skill, created by okaris and published at openclaw/skills. ClawSecure audited linkedin-content across 2 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 85/100 (Safe). The 3 findings concentrate in Code Injection, Permissions Manifest and Policy Violation, including Potentially dangerous code pattern detected: curl.*\|.*sh and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is linkedin-content safe?

ClawSecure audited linkedin-content and assigned a security score of 85/100 (Safe), identifying 3 findings across Code Injection and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in linkedin-content?

ClawSecure identified 3 findings in linkedin-content, concentrated in Code Injection, Permissions Manifest and Policy Violation. 1 was rated high or critical severity. The most severe include Potentially dangerous code pattern detected: curl.*\|.*sh and Missing config.json - agent may not be properly configured.

How was linkedin-content audited?

ClawSecure ran linkedin-content through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 2 files from openclaw/skills.

What does a score of 85 mean?

ClawSecure assigned linkedin-content a security score of 85/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status, though 1 finding was rated high or critical and warrants review. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).

Audit Findings for linkedin-content

ClawSecure detected 3 security findings in linkedin-content, spanning Code Injection, Permissions Manifest and Policy Violation.

high · Potentially dangerous code pattern detected: curl.*\|.*sh. Code Injection finding detected in SKILL.md.
medium · Missing config.json - agent may not be properly configured. Permissions Manifest finding.
info · Missing License Declaration. Policy Violation finding detected in SKILL.md.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for linkedin-content

Eliminate dynamic code execution

linkedin-content evaluates code at runtime (for example eval or dynamic exec). Remove dynamic evaluation of untrusted input, and where code generation is unavoidable, sandbox it and validate every input.

Add a config.json permissions manifest

A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.

Resolve policy violations

linkedin-content trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.

Pin dependencies to exact versions

Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.

Related Security Research

Why Generic Scanners Fail at AI Agent Security→Beyond Static Scans: Why ClawSecure Verifies Agentic Intent→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

@mohtasham/md-to-docxScore 85/100 pptxScore 93/100 summarizeScore 95/100 Powerpoint / PPTXScore 95/100 cve-2026-42945-nginx-rewrite-analysisScore 85/100

Scanned on February 26, 2026. linkedin-content is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan