engram-server-api
API contract guardrails for Engram server changes. Trigger: Any route, handler, payload, or status code modification.
63
Quality
73%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Securityby
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/server-api/SKILL.mdWhen to Use
Use this skill when:
- Adding or changing HTTP routes
- Updating handler request/response schemas
- Modifying status code behavior
Contract Rules
- Every new/changed endpoint must have tests.
- Cover both success and error paths.
- Keep scripts and docs aligned with real handlers.
- Do not reference non-existent endpoints in plugins/hooks.
Required Validation
- Handler-level tests for parsing/validation errors
- E2E tests for route behavior and response body
- Regression test for every bugfix related to API contracts
Docs Rules
If payload or route changes, update docs in the same PR.
- Repository
- Gentleman-Programming/engram
- Commit
763a6ba
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.