af-create-log

Append structured NDJSON log entries with ISO 8601 timestamps to workflow logs.

1|Updated Nov 12, 2025
One-click install
npx skills add https://github.com/e-stpierre/agentic-forge --skill af-create-log
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: af-create-log
Source: https://github.com/e-stpierre/agentic-forge/tree/main/src/claude/.claude/skills/create-log
Command: npx skills add https://github.com/e-stpierre/agentic-forge --skill af-create-log

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a simple, reliable way to record structured log entries for Agentic Forge workflows, removing manual log management and ensuring consistent, machine-readable records for debugging and auditing.

Core Features & Use Cases

  • Structured NDJSON entries with ISO 8601 timestamps and explicit level and step fields for traceability.
  • Append-only logging to agentic/outputs/{workflow-id}/logs.ndjson for stable audit trails and post-run analysis.
  • Use case: Record progress milestones, warnings when rate limits approach, or critical errors that require immediate attention.

Quick Start

Add a log entry for workflow 1234 with level Information, step implement, and message Completed milestone 1.

Frequently Asked Questions about af-create-log

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add structured workflow logs with ISO 8601 timestamps?

To add structured workflow logs with ISO 8601 timestamps, append NDJSON entries to agentic/outputs/{workflow-id}/logs.ndjson. Each entry requires defined level, step, and message fields to ensure machine-readable traceability for debugging and auditing.

What is the best way to record progress milestones and errors in Agentic Forge workflows?

Recording progress milestones and errors in Agentic Forge workflows is done by appending structured NDJSON entries to a dedicated logs.ndjson file. This creates stable, append-only audit trails for post-run analysis and debugging.

How do I create an append-only audit trail for workflow debugging?

You create an append-only audit trail for workflow debugging by writing structured NDJSON entries to agentic/outputs/{workflow-id}/logs.ndjson. This approach records progress milestones, warnings, and critical errors with explicit level and step fields.

Can I use NDJSON to log warnings and decision context for post-run analysis?

Yes, you can use NDJSON to log warnings and decision context for post-run analysis. The Skill writes structured entries with ISO 8601 timestamps, level, step, and message fields directly into the workflow's logs.ndjson file.

Does Agentic Forge logging require specific fields for each log entry?

Agentic Forge logging requires specific fields for each NDJSON entry: level, step, and message. These defined fields, combined with automatic ISO 8601 timestamps, ensure consistent and machine-readable records for workflow auditing.

When do I need structured NDJSON logs instead of plain text for workflows?

You need structured NDJSON logs instead of plain text when you require machine-readable records for debugging and auditing. NDJSON provides explicit level and step fields alongside ISO 8601 timestamps for reliable traceability during post-run analysis.