SKILLEMALL.ai
GitHub ↗ RU Sign in

CD task-board-setup

Deploys a file-based task board with domain/task methodology, derived task graph and unique session anti-drift timers; optional spec/design layer and CLAUDE.md optimization. Upgrade adds missing control layers without replacing task decisions. Triggers: scaffold task board, task tracker, upgrade task board, канбан-доска, спек-слой.

kochetkov-ma/claude-brewcode Claude Code author: kochetkov-ma 16 files · 1 script body ≈ 9 535 tokens Open the sourcegithub.com↗ analyzed 7 h ago

Deploys a file-based task board with domain/task methodology, derived task graph and unique session anti-drift timers; optional spec/design layer and…

As a process D 44/100 · Unfinished process — weak spots: steps, result and completion, when it triggers

TemplateAI and agentstype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
C
80/100
safety, quality, tests
Safety 60%
95
Quality 40%
58
Run on models
none yet
Process rating
D
44/100
Unfinished process
Steps w 15
0
Result and completion w 14
0
Inputs and preconditions w 11
0
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.

Broad scope 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 skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

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 · 1

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Write Edit Bash Glob Grep Agent AskUserQuestion CronCreate CronList CronDelete Skill(brewtools:text-optimize *)

Files scanned: 16. 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 ≈ 9535 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 44/100

  • 0Steps. Prose only: no discrete steps
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 10 mutating operations with no state check
  • 40Execution cost. Instruction body is 9535 tokens: crowds the task out of the window
  • 100Tools and files. Tools declared in frontmatter
  • 100Failures and branches. 4 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 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 (8 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)
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • -31 of 1 scripts are never mentioned in SKILL.md
  • +3Description length 333: enough signal without eating the budget
  • +4Structure: 9 headings
  • +4Has examples (13 code blocks)
  • +4Reference files are cited in the instructions (13 of 13)
  • +1License stated
  • +2Bilingual instructions (RU + EN)

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