ClawHub
Skill flagged — suspicious patterns detected

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

Pub Slack

v1.0.0

Control Slack from Clawdbot including reacting to messages and pinning items. And also 50+ models for image generation, video generation, text-to-speech, spe...

⭐ 0· 185·0 current·0 all-time
by@kirkraman
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
high confidence
!
Purpose & Capability
Name/description promise: 'Control Slack from Clawdbot' (reacting to messages, pinning). Actual requirements and SKILL.md: only document calls to https://api.heybossai.com/v1 (SkillBoss) and many model APIs. No Slack API endpoints, no Slack credentials (e.g., SLACK_BOT_TOKEN, SLACK_SIGNING_SECRET) are requested. This is a clear mismatch — either the description is wrong/misleading or the skill is incomplete.
!
Instruction Scope
SKILL.md contains curl examples to call SkillBoss endpoints for chat, image/video/tts/stt, search, and more. There are no instructions on interacting with Slack (no HTTP calls to slack.com/api, no instructions to read Slack events, no use of Slack-specific env vars). The instructions do not justify Slack-related claims and do not direct the agent to access or modify Slack messages or pins.
✓
Install Mechanism
Instruction-only skill with no install spec and no code files — low installation risk. Nothing is downloaded or written to disk by an installer.
!
Credentials
The skill requires a single env var SKILLBOSS_API_KEY which matches the documented SkillBoss API usage in SKILL.md. However, given the Slack-centric description, absence of any Slack credential requirement is disproportionate/incoherent. If the intended behavior is to control Slack, missing Slack credentials or any explanation of how SkillBoss would access Slack is suspicious.
✓
Persistence & Privilege
The skill is not forced-always (always:false) and uses default autonomous invocation settings. It does not request elevated persistence or modify other skills/system settings in the provided materials.
What to consider before installing
Do not provide sensitive API keys until you understand what the skill will actually do. This skill appears mislabeled: it promises Slack control but only documents a third‑party model API (heybossai/SkillBoss). Ask the publisher for clarification: where are the Slack integration steps, and why are Slack credentials not requested? If you intended to get Slack-control functionality, request a version that clearly documents Slack API calls and requires a Slack bot token (and verify the code). Treat the SKILLBOSS_API_KEY like any sensitive credential — only supply it to trusted sources and consider testing in an isolated account or sandbox.

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

latestvk9794hszaphbx6zqmxx5cw5eg182sp2k

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

EnvSKILLBOSS_API_KEY
Primary envSKILLBOSS_API_KEY

Comments