← Back to Scanner

slack-api Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

slack-api is an AI agent skill, created by byungkyu and published at openclaw/skills. ClawSecure audited slack-api across 3 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 90/100 (Safe). The 3 findings concentrate in Policy Violation, Data Exfiltration and Permissions Manifest, including Code block in SKILL.md at line 675 contains potentially dangerous... and Missing config.json - agent may not be properly configured. None were rated high or critical severity.

Is slack-api safe?

ClawSecure audited slack-api and assigned a security score of 90/100 (Safe), identifying 3 findings across Policy Violation and Data Exfiltration. Review the findings below before installing.

What did ClawSecure find in slack-api?

ClawSecure identified 3 findings in slack-api, concentrated in Policy Violation, Data Exfiltration and Permissions Manifest. The most severe include Code block in SKILL.md at line 675 contains potentially dangerous... and Missing config.json - agent may not be properly configured.

How was slack-api audited?

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

What does a score of 90 mean?

ClawSecure assigned slack-api a security score of 90/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status; the 3 findings detected are lower-severity. 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 slack-api

ClawSecure detected 3 security findings in slack-api, spanning Policy Violation, Data Exfiltration and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for slack-api

Resolve policy violations
slack-api trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
Audit external network connections
slack-api sends data to external endpoints. Confirm each destination is expected and authorized, and remove any callback that exfiltrates data. ClawSecure monitors for known exfiltration and C2 endpoints.
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.
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

OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security StandardsUnderstanding Our 3-Layer Audit ProtocolClawHavoc Explained: The Malware Family Targeting AI Agents

Related AI Agent Security Audits

fa375a9a777c1d8dScore 75/100playwright-best-practicesScore 95/100bd2aa53d1889dd92Score 80/1006fb89c3f86a53456Score 95/100b4abd97bcb77151aScore 75/100

Scanned on March 7, 2026. slack-api 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