SKILLEMALL.ai
GitHub ↗ RU Sign in

BD implement

TRIGGER when: user asks to implement, fix, build, or work on something — whether from a docs/feat/wip plan OR a standalone task (bug fix, GitHub issue, one-off change). Examples: "work on task 1", "fix this bug", "implement feature X from the issue". Provides structured execution with profile detection, dependency handling, review checkpoints.

serpro69/claude-toolbox Agent Skills author: serpro69 NOASSERTION 26 files · 5 scripts body ≈ 1 888 tokens Open the sourcegithub.com↗ analyzed 5 h ago

TRIGGER when: user asks to implement, fix, build, or work on something — whether from a docs/feat/wip plan OR a standalone task (bug fix, GitHub issue…

As a process D 44/100 · Unfinished process — References files that are not bundled: shared-capy-knowledge-protocol.md, shared-profile-detection.md

ProcedureGitHubKubernetesData and analyticstype 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
B
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
76
Run on models
none yet
Process rating
D
44/100
Unfinished process
References files that are not bundled: shared-capy-knowledge-protocol.md, shared-profile-detection.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: implement (serpro69/claude-toolbox)

How to improve

  1. The text references files that are not there: add them or drop the references.
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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: shared-capy-knowledge-protocol.md
  • warning missing-ref reference to a missing file: shared-profile-detection.md

Process rating: all ten parameters 44/100

Will not run. References files that are not bundled: shared-capy-knowledge-protocol.md, shared-profile-detection.md
  • 0Tools and files. 2 referenced file(s) missing: shared-capy-knowledge-protocol.md, shared-profile-detection.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 50Failures and branches. 0 branches, has a failure section
  • 70When it triggers. States when to use, but not when not to
  • 85Steps. 39 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1888 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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 3 example trigger phrases
  • +3Description length 345: enough signal without eating the budget
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 39 items

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