SKILLEMALL.ai
GitHub ↗ RU Sign in

BC daily-plan-orchestrator

每日计划编排器,daily_plan表PG持久化,从task_template实例化每日计划,carryover上限30天(R72.5保护),每日0:00 DRR状态重置+熔断HALF_OPEN,跨日Pipeline支持。触发:daily-plan-generator Cron每日0:00/手动生成计划。不触发:单次任务执行(用task-dispatcher)

ClawHub Agent Skills author: 天轰穿 v1.0.0 MIT-0 5 files body ≈ 452 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

每日计划编排器,dailyplan表PG持久化,从tasktemplate实例化每日计划,carryover上限30天(R72.5保护),每日0:00 DRR状态重置+熔断HALFOPEN,跨日Pipeline支持。触发:daily-plan-generator…

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorSoftware developmenttype 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
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
73
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
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: 5. 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 "tools"
  • note frontmatter-key unknown frontmatter key "dependencies"

Process rating: all ten parameters 53/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 24 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 452 tokens
  • 100Running it twice. No mutating operations

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 181: enough signal without eating the budget
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 24 items
  • +4Has examples (3 code blocks)
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
The skill performs the advertised daily scheduling work, but it also reads cross-tenant agent memory and automatically changes task priorities without clearly disclosing that behavior.
LLM: suspicious (high) · 15 Aug 2026