excrtx-harness-promptlog

Appends structured configuration change entries to MEMORY.md for audit and reproducibility.

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/elderbernardi/exocortex.saas --skill excrtx-harness-promptlog-elderbernardi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: excrtx-harness-promptlog
Source: https://github.com/elderbernardi/exocortex.saas/tree/main/skills/excrtx-harness-promptlog
Command: npx skills add https://github.com/elderbernardi/exocortex.saas --skill excrtx-harness-promptlog-elderbernardi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Configuration changes to files like SOUL.md, MEMORY.md, and config.yaml are easily lost or forgotten, making it impossible to audit what changed or reproduce a setup on a new instance. This Skill maintains a structured, append-only log of every configuration prompt so the full history is traceable. ## Core Features & Use Cases - Structured Audit Entries: Logs each configuration change with a sequential Prompt ID, ISO 8601 UTC timestamp, phase (P1-P6), modified artifacts, status, and a one-line summary. - Sequential ID Management: Derives the next PDD-ID by counting existing entries in MEMORY.md, preventing ID collisions. - Reproducibility: Any agent can read MEMORY.md and reconstruct the complete configuration history of a Hermes instance. - Use Case: After updating SOUL.md to change your communication style, the Skill appends an entry like [PDD-004] 2024-01-15T10:30:00Z | Phase: P3 | Status: success with the artifact list and summary, so the change can be replayed later. ## Quick Start Log the configuration change I just made to SOUL.md in MEMORY.md so I can reproduce this setup later.

Frequently Asked Questions about excrtx-harness-promptlog

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

FAQPage Schema
How do I log configuration changes to MEMORY.md?▼

Append a structured entry containing a sequential PDD-ID, ISO 8601 UTC timestamp, phase (P1-P6), modified artifacts, status, and a one-line summary. Use grep to count existing entries for the next ID and date -u for the timestamp.

What changes should be recorded in a configuration audit log?▼

Log only prompts that modify SOUL.md, MEMORY.md, config.yaml, or install skills and tools. Normal conversation, task execution, briefings, and code changes without configuration impact should not be logged.

How do I avoid ID collisions when appending log entries?▼

Derive the next ID by counting existing entries with grep -c '^\[PDD-' on MEMORY.md and adding one. Never hardcode or guess IDs, and verify the last PDD-ID before writing when multiple sessions may write concurrently.

Why is my configuration log timestamp inconsistent?▼

Inconsistent timestamps happen when local time zones are used. Always generate timestamps with date -u +%Y-%m-%dT%H:%M:%SZ to produce uniform ISO 8601 UTC values across all entries.

When should I not use a prompt logging skill?▼

Do not use it for normal conversation, task execution, briefings, or self-diagnostics. It is scoped strictly to configuration changes; use briefing or self-test skills for status checks and diagnostics instead.