soul-audit

Run a six-phase interview to generate SOUL.md, USER.md, ACCESS_POLICY.md, and HEARTBEAT.md.

Updated May 11, 2026
One-click install
npx skills add https://github.com/yunusgungor/gbrain --skill soul-audit-yunusgungor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: soul-audit
Source: https://github.com/yunusgungor/gbrain/tree/main/skills/soul-audit
Command: npx skills add https://github.com/yunusgungor/gbrain --skill soul-audit-yunusgungor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides you through designing and updating an agent's identity, personality, and operational cadence via a structured, re-runable interview that produces SOUL.md, USER.md, ACCESS_POLICY.md, and HEARTBEAT.md.

Core Features & Use Cases

  • Multi-phase interview to generate SOUL.md, USER.md, ACCESS_POLICY.md, and HEARTBEAT.md.
  • Re-run any phase independently to update specific sections.
  • Uses templates as scaffolds to guide content; default mode installs minimal scaffolds when skipped.
  • Ensures content is user-provided and never ships pre-filled data.

Quick Start

Run the soul audit to begin the interactive interview and 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 create an agent identity and operational cadence from scratch?

To create an agent identity, run a phase-based interactive interview that scaffolds markdown files like SOUL.md and HEARTBEAT.md from your direct input, establishing the agent's core persona and operational cadence.

What is the best way to update an existing agent persona without rewriting everything?

Updating an agent persona is handled by re-running any specific phase independently in the interview workflow, which refreshes target files like SOUL.md or ACCESS_POLICY.md individually without affecting other identity artifacts.

How does a phase-driven interview workflow generate markdown for agent bootstrapping?

A phase-driven interview workflow uses a six-phase structure and template scaffolds to guide user input, ensuring generated markdown artifacts contain only user-provided content and never ship pre-filled data during agent bootstrap.

Can I use templates to scaffold agent identity files across multiple projects?

Yes, templates function as scaffolds to guide content generation for agent identity files, supporting ongoing persona tuning and agent bootstrap across projects while enforcing user-provided data over default values.

What files are generated during an interactive agent identity interview?

An interactive agent identity interview generates four target files: SOUL.md, USER.md, ACCESS_POLICY.md, and HEARTBEAT.md, each serving a distinct role in defining the agent's personality and operational cadence.