# Configure Daem0n-MCP Project Memory

Developers lose context when work spans repositories and sessions. This skill guides Daem0n-MCP setup for shared memory, linked projects, hooks, and search tuning.

## Install

```bash
npx skillstore add dasblueyeddevil/summon-daem0n
```

## Metadata

- Status: approved
- Slug: dasblueyeddevil-summon-daem0n
- Skillstore revision: r1
- Version status: missing
- Tree hash: ecba3b15ae4cd64f60ca91b5ab4b23603f29af8844cf44080fd899cae781575c
- Author: DasBluEyedDevil
- GitHub username: DasBluEyedDevil
- License: MIT
- Repository: https://github.com/DasBluEyedDevil/Daem0n-MCP/tree/main/.claude/skills/summon\_daem0n
- Ref: 3e4b6c31a74a3bd1a291c98cf585d720cb9fbc88
- 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, filesystem
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/dasblueyeddevil-summon-daem0n
- Manifest: https://skillstore.pages.dev/api/skills/dasblueyeddevil-summon-daem0n/manifest

## Capabilities

- Explains single-repository Daem0n-MCP initialization.
- Shows parent and linked setup patterns for related repositories.
- Documents consolidation of child project memory databases.
- Provides Claude hook settings for pre-edit, post-edit, and stop events.
- Lists recall, search tuning, indexing, and health check options.
- Describes backup and migration steps for existing Daem0n data.

## Use Cases

- Set up one project memory store: Use the skill to understand how Daem0n-MCP initializes memory for a single repository.
- Connect related repositories: Plan shared or linked memory for client, server, and support repositories.
- Tune recall and indexing: Review search, condensed recall, automatic tags, and health indicators for larger codebases.

## Prompt Templates

### Initialize a single repository

```
Help me set up Daem0n-MCP memory for this one repository. Explain the steps before suggesting any command.
```

### Choose a multi-repo layout

```
I have related frontend and backend repositories. Compare parent memory and linked memory, then recommend one approach.
```

### Review an existing memory store

```
Inspect my current Daem0n-MCP setup conceptually and propose a cautious migration plan with backup and verification steps.
```

### Design a guarded hook workflow

```
Design a safe Claude hook workflow for Daem0n-MCP. Include consent points, script review, and rollback steps.
```

## Limitations

- It is documentation only and does not install Daem0n-MCP.
- It assumes Daem0n-MCP commands and hook scripts already exist.
- Examples use placeholder paths that users must adapt carefully.
- Hook behavior depends on local scripts outside this skill.

## Best Practices

- Back up Daem0n-MCP data before consolidation or cleanup.
- Review hook scripts before enabling automatic command execution.
- Use one shared memory root for repositories that form one product.

## Anti Patterns

- Do not run destructive cleanup commands without a verified backup.
- Do not enable hooks from unreviewed local scripts.
- Do not merge unrelated project memories into one store.

## Security Audit

- Audited at: 2026-07-09T08:40:38.829\+00:00
- Summary: Most static findings are false positives caused by Markdown code fences, inline tool names, and documentation examples. Confirmed risks remain around persistent Claude hook command execution, automatic memory capture, and a destructive hidden-directory cleanup command.

## Stats

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