SKILLEMALL.ai
GitHub ↗ RU Sign in

AB agent-slackbot

Interact with Slack workspaces using bot tokens - send messages, read channels, manage reactions

ClawHub Agent Skills author: Jeon Suyeol v1.10.5 7 files · 3 scripts body ≈ 2 606 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process B 69/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice

IntegrationSlackAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
99
Quality 40%
76
Run on models
none yet
Process rating
B
69/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 1

✓ No critical or high findings

Medium and low: 1
  • low Secrets in code secret-slack-token references/authentication.md:80
    Slack token (placeholder value)
    "token": "xoxb…..."
    placeholder

Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 69/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 9 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 36 steps
  • 100Failures and branches. 5 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2606 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 13 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 96: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 32 headings
  • +3Step-by-step instructions: 36 items
  • +3Output format is stated explicitly
  • +4Has examples (15 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.

External checks

ClawHub: suspicious
This Slack bot skill is mostly coherent, but it gives an agent broad Slack read/write access and persists sensitive tokens and workspace metadata locally, so it needs careful review before use.
LLM: suspicious (high) · VirusTotal: · 29 May 2026