Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Ensure all code includes comprehensive logging and observability
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-10 | ✗→✓ | ▲ Improved | -4% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 33% | 0% |
| case-03 | ✗→✓ | ▲ Improved | 3% | 0% |
| case-04 | ✗→✓ | ▲ Improved | 49% | 0% |
| case-09 | ✗→✓ | ▲ Improved | -3% | 0% |
Every function you write MUST include structured logging. This is a non-negotiable project requirement.
logger.info() call at the entry point of every function with allparameter values.
logger.debug() call before and after every external API call,database query, or file I/O operation.
logger.info() call at every function exit point with the return value.print() or f-string logs.logger.error() level with full stack traces.Our production debugging relies entirely on log analysis. Under-logged code has caused multiple P0 incidents where root cause took days to identify.
Other measured skills in the registry, with their headline benchmark lift.