How Scoring Works
Understand how Solenvus skill scores help users evaluate quality, speed, and readiness.
Solenvus uses visible scoring signals to help users evaluate skills faster.
These scores do not replace judgment.
They are designed to make comparison easier and more consistent.
Trust score reflects confidence-related factors around a skill.
It helps users identify skills that appear stronger for serious evaluation.
Speed score reflects execution responsiveness.
It helps users compare skills where latency matters.
Battle score reflects comparative performance in battle-oriented evaluation contexts.
It is useful when users want to compare alternatives directly.
Docs score reflects how well a skill is documented and explained.
It is useful when implementation clarity matters.
How to use scores well
Scores work best when they are read together.
A high score in one area does not always mean the skill is the best choice for every use case.
For example:
A fast skill may still need stronger documentation for production adoption
A well-documented skill may not be the best fit for a specific protocol need
A battle-strong skill may still depend on the action you want to run
Best evaluation approach
Use this order when choosing a skill:
Confirm the protocol and action match your use case
Review live execution support
Compare trust, speed, battle, and docs scores
Use Battle Arena if you need a direct comparison
What scores are for
Scores are meant to reduce guesswork.
They help users shortlist options faster and inspect the strongest candidates with more confidence.
