SKILLEMALL.ai
GitHub ↗ RU Sign in

AC scheduler

Schedule tasks and commands to run at specific times. Execute shell commands, agent tasks, API calls, and automations on a cron schedule. Tested on Telegram & Discord.

modbender/skill-library-mcp Agent Skills author: modbender MIT 2 files body ≈ 2 934 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Schedule tasks and commands to run at specific times.

As a process C 56/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency

IntegrationDiscordTelegramAI and agentstype 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%
100
Quality 40%
75
Run on models
none yet
Process rating
C
56/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Consistency w 8
40
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 · 0

✓ No critical or high findings

Files scanned: 2. 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")
  • note frontmatter-key unknown frontmatter key "command-dispatch"

Process rating: all ten parameters 56/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 40Consistency. Frontmatter name (scheduler) differs from the folder (task-scheduler)
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
  • 85Steps. 46 steps, 3 vague phrases
  • 100When it triggers. States when to use and when not to
  • 100Execution cost. Instruction body is 2934 tokens
  • 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 The response is described with custom markup (11 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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 167: enough signal without eating the budget
  • +4Structure: 17 headings
  • +3Step-by-step instructions: 46 items
  • +4Has examples (6 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)

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