SKILLEMALL.ai
RU Sign in

CC roster

Creates weekly shift rosters (KW-JSON) from CSV availability data and pushes them to GitHub.

ClawHub Agent Skills author: kleberbaum v1.5.0 MIT-0 12 files · 5 scripts body ≈ 11 021 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process C 58/100 · Has gaps — weak spots: result and completion, inputs and preconditions, execution cost

GeneratorGitHubInfrastructureData and analyticstype 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
C
69/100
safety, quality, tests
Safety 60%
75
Quality 40%
60
Run on models
none yet
Process rating
C
58/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Execution cost w 6
40
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 · 5

✓ No critical or high findings

Medium and low: 5
  • medium Exfiltration net-credential-use scripts/get-employees.sh:17
    Credential used in a network call (verify the destination is the intended service)
    RESPONSE=$(curl -s -H "Authorization: token $GITHUB_TOKEN" \
  • medium Exfiltration net-credential-use scripts/push-to-github.sh:60
    Credential used in a network call (verify the destination is the intended service)
    RESPONSE=$(curl -s -H "Authorization: token $GITHUB_TOKEN" \
  • medium Exfiltration net-credential-use scripts/update-employees.sh:51
    Credential used in a network call (verify the destination is the intended service)
    RESPONSE=$(curl -s -H "Authorization: token $GITHUB_TOKEN" \
  • medium Exfiltration net-credential-use SKILL.md:161
    Credential used in a network call (verify the destination is the intended service)
    curl -s -o /dev/null -w "%{http_code}" -H "Authorization: token $GITHUB_TOKEN" \
  • medium Exfiltration net-credential-use SKILL.md:910
    Credential used in a network call (verify the destination is the intended service)
    curl -s -H "Authorization: token $GITHUB_TOKEN" \

Files scanned: 12. 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")
  • warning body-long SKILL.md body ≈ 11021 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 58/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 40Execution cost. Instruction body is 11021 tokens: crowds the task out of the window
  • 50When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 100Steps. 261 steps
  • 100Failures and branches. 24 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 16 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (9 tags): a typed call is more reliable

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 92: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -268 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +4Structure: 55 headings
  • +3Step-by-step instructions: 261 items
  • +4Has examples (17 code blocks)
  • +3All 5 scripts are documented

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

External checks

ClawHub: suspicious
This looks like a real roster tool, but it can persistently change employee records and trigger GitHub workflows that send rosters externally with loose confirmation boundaries.
LLM: suspicious (high) · VirusTotal: benign · 28 May 2026