eide Rapport d’évaluation.

Plan de validation

Ce que l’Agent doit faire ensuite

1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. 2Install in an isolated workspace or sandbox with no production secrets available.
3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
5. 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Ne pas utiliser quand

Conditions exigeant une autre skill

• Équipes qui nécessitent un SLA soutenu par le fournisseur
• production agents without a repository review
• The skill description contains a typo: 'Cl.eide' should be 'cl.eide'.
• Indices de permissions à haut risque : exécution shell ou de commande
• The config.example.json uses hardcoded absolute paths (e.g., C:\Users\Administrator...) which may not be portable across environments, but this is user-configurable.
• The skill relies on PyYAML but includes a fallback parser; however, the fallback parser may not handle all YAML constructs, potentially causing misparsing of complex eide.yml files.