soul-audit

Generates agent identity files (SOUL.md, USER.md, ACCESS_POLICY.md, HEARTBEAT.md via interactive interview.

1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/edwifiguy/era-agents-ops --skill soul-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: soul-audit
Source: https://github.com/edwifiguy/era-agents-ops/tree/main/skills/era-agents-op/gbrain/skills/soul-audit
Command: npx skills add https://github.com/edwifiguy/era-agents-ops --skill soul-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams generate and maintain an agent's identity and operational configuration by guiding an interactive interview that yields four key files: SOUL.md, USER.md, ACCESS_POLICY.md, and HEARTBEAT.md. The process is repeatable and re-runable so you can update any section without starting from scratch.

Core Features & Use Cases

  • Interactive Identity Interview: builds a complete agent identity profile (SOUL.md) and a user profile (USER.md) along with access policy (ACCESS_POLICY.md) and cadence (HEARTBEAT.md).
  • Independent Phases: each phase can be re-run to update a single section without affecting others.
  • Template-driven scaffolds: templates provide prompts and structure while user responses populate content.

Quick Start

Run the soul audit to generate SOUL.md, USER.md, ACCESS_POLICY.md, and HEARTBEAT.md.

Frequently Asked Questions about soul-audit

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

FAQPage Schema
How do I define an agent's identity and operational cadence?▼

To define an agent's identity and operational cadence, run an interactive interview that generates four configuration files: SOUL.md, USER.md, ACCESS_POLICY.md, and HEARTBEAT.md. This structured workflow ensures repeatable, audit-friendly agent configurations.

Can I update just the access policy without redoing the entire agent identity interview?▼

Yes, you can update the access policy independently because the workflow uses an independently re-runnable phase pipeline. You simply re-run the specific ACCESS_POLICY.md phase without affecting the SOUL.md, USER.md, or HEARTBEAT.md configurations.

What files are generated when configuring an agent's identity and access policy?▼

Configuring an agent's identity and access policy generates four frontmatter-driven YAML files: SOUL.md for identity, USER.md for the user profile, ACCESS_POLICY.md for permissions, and HEARTBEAT.md for operational cadence.

How do I maintain an agent's operational cadence and configuration over time?▼

You maintain an agent's operational cadence by re-running specific phases of the structured pipeline to update individual files like HEARTBEAT.md. This template-driven approach allows repeatable updates to operational cadence without affecting other identity configurations.

Does the agent identity interview use frontmatter or YAML for configuration?▼

Yes, the agent identity interview relies on frontmatter-driven YAML sections within the generated SOUL.md, USER.md, ACCESS_POLICY.md, and HEARTBEAT.md files. This structure ensures repeatable, audit-friendly configurations across the workflow pipeline.