logging-best-practices
Pass
Audited by Gen Agent Trust Hub on Sep 10, 2026
Risk Level: SAFEMETADATA_POISONINGINDIRECT_PROMPT_INJECTION
Full Analysis
- [SAFE]: The skill provides documentation and code examples for standard software engineering best practices regarding observability and logging. It includes references to official documentation from Stripe and technical articles from established domains.
- [METADATA_POISONING]: A discrepancy exists between the author name in the YAML frontmatter ('boristane') and the provided author context ('likas07'). This appears to be an artifact of the skill being based on existing technical literature rather than a malicious attempt at deception.
- [INDIRECT_PROMPT_INJECTION]: The skill describes patterns for logging data from external sources, which constitutes a potential log injection surface. 1. Ingestion points: 'c.req.json()', 'c.req.header()', and 'error.message' found in 'rules/wide-events.md' and 'rules/structure.md'. 2. Boundary markers: Absent. 3. Capability inventory: The 'logger.info' call in 'rules/structure.md' emits structured data to the standard logging output. 4. Sanitization: Absent; the guidelines do not explicitly detail PII scrubbing or character escaping for log injection prevention.
Audit Metadata