SKILLEMALL.ai
RU Sign in

BD java-springboot

Get best practices for developing applications with Spring Boot.

github/awesome-copilot Agent Skills author: github MIT 1 file body ≈ 1 006 tokens open source ↗ analyzed 22 h ago

Get best practices for developing applications with Spring Boot.

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

ProcedureSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: GitHub Copilot / VS Code Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
65
Run on models
none yet
Process rating
D
44/100
Unfinished process
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

The same skill appears in 1 more place: RA-Skills

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: 1. 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")

Process rating: all ten parameters 44/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
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 85Steps. 30 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1006 tokens
  • 100Running it twice. No mutating operations
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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 64: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 30 items

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