Versioned security assessment

Report ID: SA-16F7C1A8

6/30/2026, 6:07:25 PM

slack-bot-builder security assessment v2

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
slack-bot-builder
Version
v2
Maintainer
sickn33
Source
github.com/sickn33/antigravity-awesome-skills/tree/main/skills/slack-bot-builder
Coverage
1 Files scanned · 265 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Medium

3 confirmed security findings require attention.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

Static command execution and weak cryptography alerts are false positives from Markdown fences and words such as description. The skill is not malicious, but it includes security-sensitive Slack OAuth and token handling examples that require careful secret storage, state validation, and output escaping.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

1 Files scanned · 265 Lines analyzed

6 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Not recorded by this audit

Network access

May connect to external services.

Observed in 1 evidence location

Filesystem access

May read or write local files.

Observed in 2 evidence locations

Env variables

May read values from the process environment.

Observed in 6 evidence locations

External commands

May invoke commands or programs outside the Skill.

Not recorded by this audit

Capability review items (3)
Medium
SKILL.md:36-37SKILL.md:111SKILL.md:234-237
Slack Credential Handling Requires Secret Controls
The examples read Slack bot tokens, signing secrets, client IDs, and client secrets from environment variables. This is legitimate for Slack apps, but copied production code must protect these secrets and prevent logging or accidental exposure.
The file clearly accesses Slack credentials from environment variables. The usage is expected for Slack Bolt apps, so the risk is operational rather than malicious.
Medium
SKILL.md:196-197SKILL.md:247
File-Backed OAuth State Store in Example
The OAuth example imports file-backed installation and state stores, then uses FileOAuthStateStore. File-backed OAuth state can be unsafe for distributed or production deployments without strict filesystem controls.
The example explicitly references file-backed OAuth storage. The text also recommends database-backed production storage, which reduces confidence that this is a serious flaw.
Low
SKILL.md:36-37SKILL.md:102SKILL.md:247
Dangerous Combination Heuristics Not Confirmed
The critical and high combination heuristics are caused by legitimate Slack examples that mention credentials, a documentation URL, and file-backed OAuth state. No evidence of obfuscation, credential exfiltration, or malicious instruction was found.
The risky elements appear in explanatory Slack app patterns and do not combine into executable exfiltration behavior. The skill file is documentation, not an installed script.

Risk findings

Confirmed security concerns are separated from items that still need review.

Confirmed security concerns (3)

RISK-001 Medium
SKILL.md:137-149SKILL.md:158
Unescaped User Content in Slack Markdown
The Block Kit example interpolates incident fields into Slack mrkdwn text. If those fields come from users or external systems, Slack mentions, links, or formatting could be spoofed unless escaped or normalized.
The interpolation is visible, but the source of incident data is not shown. The concern depends on whether the application accepts untrusted incident content.
RISK-002 Low
SKILL.md:55
Filesystem Alert Is Slack Modal API Usage
The static filesystem alert points to client.views_open, which opens a Slack modal through the Slack API. It does not write or append to a local file.
The cited line is a Slack client method call inside a slash command handler. There is no file path, open call, write call, or append operation.
RISK-003 Low
SKILL.md:222
System Reconnaissance Alert Is OAuth Data Lookup
The system reconnaissance alert points to an enterprise_id lookup in OAuth installation records. This is Slack workspace metadata handling, not host or network reconnaissance.
The surrounding code queries Slack installation records by team and enterprise ID. It does not inspect the local system, network, users, processes, or environment.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Static false positives ignored (3)
Low
SKILL.md:28SKILL.md:89SKILL.md:107SKILL.md:173SKILL.md:193
Command Execution Alerts Are Markdown False Positives
The static Ruby backtick alerts point to fenced Python examples in Markdown. No executable backtick shell command is present in the skill file.
The cited lines are Markdown code fence boundaries or starts of Python examples. There is no shell execution syntax or command runner at those locations.
Low
SKILL.md:102
Hardcoded URL Is Documentation
The hardcoded URL points to Slack Block Kit Builder for prototyping. It is a documentation link, not a network request or exfiltration endpoint.
The line is plain Markdown text that references an official Slack tool. No code sends data to the URL.
Low
SKILL.md:3SKILL.md:74-80SKILL.md:153-158
Weak Cryptography Alerts Are Text Matches
The static weak cryptography detections are caused by words and identifiers such as description, desc_block, and desc_input. No weak hash or cipher algorithm is shown at the cited lines.
The cited lines contain descriptive text and field names, not calls to MD5, DES, SHA1, or another weak algorithm. The nearby encrypt and decrypt placeholders are not listed static locations.

Verify and export

JSON report CITATION.cff SARIF 2.1.0 Signed installation manifest

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable