BC solon-development-skill
Specialized knowledge for developing Java applications with the Solon framework. Covers core concepts, web, data, security, remoting, AI, flow orchestration, cloud-native, testing, and more. Solon is an independent Java enterprise framework (NOT based on Spring) with its own annotation system, IoC/AOP container, and plugin ecosystem.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-password-literalreferences/api_annotations.md:244Hard-coded password / key literal (may be an example)password: Ssn1…re0
-
low Secrets in code
secret-password-literalreferences/core_concepts.md:291Hard-coded password / key literal (may be an example)password: Ssn1…re0
-
low Secrets in code
secret-password-literalreferences/security.md:176Hard-coded password / key literal (may be an example)password: "liyl…k1C" # 默认算法要求 16 位,建议包含大小写和数字
-
low Secrets in code
secret-password-literalreferences/security.md:201Hard-coded password / key literal (may be an example)password: "liyl…k1C"
-
low Secrets in code
secret-password-literalreferences/security.md:206Hard-coded password / key literal (may be an example)password: "ENC(XgRq…ySA==)"
Files scanned: 15. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1020 tokens
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 335: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 7 items
- +4Reference files are cited in the instructions (13 of 13)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.