Start with the problem, not the Skill
Before evaluating anything, define what result you expect. An excellent Skill for a problem you don't have is still useless in your operation.
The eight checks
- Real utility: does it solve a concrete and recurring problem?
- Functioning: does it run end-to-end in a clean environment?
- Security: what permissions does it ask for and what does it do with credentials?
- Compatibility: does it work with the runtime and versions you use?
- Documentation: are there sufficient instructions and examples?
- Maintenance: was there an update in recent months?
- Efficiency: is the execution cost proportional to the result?
- Ease of installation: how many manual steps are necessary?
Test in an isolated environment
Never make the first execution in the production environment. Use a disposable machine, with temporary credentials and no access to your real data.
Record the decision
Whether approved or rejected, the evaluation needs to be recorded with the date, tested version, and reason. Without this record, the same discussion returns every quarter.
Frequently Asked Questions
Quanto tempo leva uma avaliação completa?
No laboratório A4 Verified, uma avaliação padrão leva de dois a cinco dias, dependendo da complexidade das integrações.
O que acontece com Skills reprovadas?
Elas recebem status de não recomendada ou bloqueada, com o motivo registrado, e não entram em nenhum kit A4.