Security and quality
A skill can guide implementation; it cannot independently prove that a module is safe.
- Never treat SKILL.md as executable code or evidence of safety.
- Do not change core files outside a reviewed development branch.
- Check permissions per resource, not only in navigation.
- Use CSRF protection, HTTPS and rate limits on sensitive public forms.
- Never put secrets or customer data into shared caches.
- Validate packages against the native contract and run complete tests.
bash
php tools/validate.php path/to/extension --json
php tests/run.php
php tools/measure.php --checkTransactional features require verified Éclair 2.0 compatibility before deployment. Experimental public authentication is not part of the standard core.