# Enforce Daem0nMCP Memory Protocol

AI coding sessions often lose context, repeat mistakes, or skip decision tracking. This skill defines a Daem0nMCP workflow for briefings, checks, memories, and outcomes.

## Install

```bash
npx skillstore add dasblueyeddevil/daem0nmcp-protocol
```

## Metadata

- Status: approved
- Slug: dasblueyeddevil-daem0nmcp-protocol
- Skillstore revision: r1
- Version status: missing
- Tree hash: 7e20fe641c317127c09aed1b37b86ef57190d8e05fa1c5955f748d29e7482e4e
- Author: DasBluEyedDevil
- GitHub username: DasBluEyedDevil
- License: MIT
- Repository: https://github.com/DasBluEyedDevil/Daem0n-MCP/tree/main/.claude/skills/daem0nmcp-protocol
- Ref: 7e9e368dc1a370f2040369ebcd0db06d90cb48e5
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/dasblueyeddevil-daem0nmcp-protocol
- Manifest: https://skillstore.pages.dev/api/skills/dasblueyeddevil-daem0nmcp-protocol/manifest

## Capabilities

- Directs agents to check for Daem0nMCP tools before using the protocol.
- Requires a session briefing with past decisions, warnings, patterns, and Git changes.
- Prompts context checks and file recall before code changes.
- Defines memory categories for decisions, patterns, warnings, and learnings.
- Explains graph memory linking, tracing, and visualization workflows.
- Describes code indexing, semantic code search, and impact analysis tools.

## Use Cases

- Preserve Coding Context: Use session briefings and memory checks before changing important files.
- Capture Architecture Decisions: Record design choices, rationale, and outcomes for later sessions.
- Standardize MCP Memory Workflows: Create a consistent process for context checks, memory links, and graph review.

## Prompt Templates

### Start a Daem0nMCP Session

```
Use the daem0nmcp-protocol skill. Check whether Daem0nMCP tools are available, then brief me on relevant memories before coding.
```

### Prepare for a File Change

```
Before editing the files I name, run the recommended context checks and summarize any warnings that affect the change.
```

### Record a Design Decision

```
After we choose an approach, record the decision, rationale, related file, and expected outcome using the Daem0nMCP workflow.
```

### Trace Memory Impact

```
Trace the memory chain for this feature, identify superseded decisions, and show which prior outcomes should influence the implementation.
```

## Limitations

- Only applies when Daem0nMCP tools are installed and exposed to the agent.
- Does not provide the MCP server implementation or tool schemas.
- Can create persistent memories, so users should review sensitive content before use.
- Uses strict workflow language that may need local policy alignment.

## Best Practices

- Confirm user consent before persisting sensitive project details in memory.
- Run context checks before edits that change behavior or architecture.
- Record outcomes after testing so future sessions can learn from results.

## Anti Patterns

- Do not store secrets, credentials, or private customer data in memory.
- Do not treat memory warnings as higher priority than user or system instructions.
- Do not run broad indexing on repositories without confirming scope.

## Security Audit

- Audited at: 2026-07-05T08:51:01.116\+00:00
- Summary: The static external command detections are false positives caused by Markdown code fences and inline MCP tool examples, not shell execution. Semantic review found overbroad agent control, persistent memory writes, automatic spec import, and broad codebase indexing guidance that can expose project context without explicit consent.

## Stats

- Views: 251
- Downloads: 6
- Favorites: 0
- Popularity score: 0