locus-palace-init-944ddf — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited locus-palace-init-944ddf (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Bootstrap a structured memory palace from existing flat session memory files (e.g. ~/.claude/projects/*/memory/MEMORY.md).
Parse $ARGUMENTS:
--source <dir> — root to scan for memory files (default: ~/.claude/projects/)--palace <dir> — palace root to write into (default: ~/.locus/)--dry-run — print the plan, write nothing--overwrite — replace existing room files (default: skip rooms that already exist)Set defaults for any omitted flags.
<source>/*/memory/MEMORY.md to find all candidate files.slug — the project directory name (the * part of the glob path)memory_path — full path to MEMORY.md.md files in the same memory/ directory (specialty files)--source path.For each source memory file, extract:
| Field | How to find it |
|---|---|
| title | First # Heading in the file |
| summary | First non-blank paragraph after the heading (≤3 sentences) |
| tech_tags | Comma-separated keywords inferred from headings and bullet lists (e.g., "kubernetes", "python", "terraform") |
| status | Look for "Current phase", "Status", "Milestone", or "v0.x" markers |
| key_files | Lines matching a path pattern (/, ~/, ./) in file-reference context |
Keep each extraction to the first 150 lines of the file — do not load the full file if avoidable.
Assign each project to a group using these heuristics (first match wins):
| Group | Heuristic |
|---|---|
infra | tech_tags contain: kubernetes, terraform, ansible, k3s, proxmox, flux, docker |
tools | tech_tags contain: cli, mcp, sdk, plugin, extension |
data | tech_tags contain: python, jupyter, pandas, ml, model, dataset |
docs | tech_tags contain: wiki, obsidian, markdown, docs, blog |
projects | everything else |
Sort within each group alphabetically by slug.
Report the grouping plan (slug → group) before writing anything.
<palace>/INDEX.md already exists.--overwrite was NOT passed:INDEX.md.--overwrite): start fresh from the template below.For each project (in group order, then alphabetical):
infra, tools, data, docs groups → <palace>/global/<slug>/projects group → <palace>/projects/<slug>/<room-path>/<slug>.md). If it does and--overwrite is not set, skip it with a note.
<slug>.md:# <title>
<summary>
## Overview
<!-- Imported from auto-memory on YYYY-MM-DD. Review and prune. -->
<paste the first 60 lines of the source MEMORY.md, indented as a blockquote or verbatim section>
## Key Files
<!-- Populated from auto-memory import. Verify paths are still current. -->
<key_files extracted in step 3, one per table row>
## References
<!-- Specialty files imported alongside MEMORY.md, if any. -->
<one line per specialty file, or "(none)" if none>
<!--
SOURCE: <memory_path>
IMPORTED: YYYY-MM-DD
STATUS: imported — review and reformat before treating as canonical
-->.md files from memory/ into the room directory as-is.Build the index by iterating groups in this order: infra, tools, data, docs, projects.
Use the template below, omitting any section whose group has no rooms:
# <Palace Name>
Memory palace auto-initialized from <N> project memory files on YYYY-MM-DD.
Review imported rooms and reformat to canonical style before treating as final.
## Global Rooms
| Room | Description | Path |
|---|---|---|
| `<slug>` | <summary, truncated to 80 chars> | `global/<slug>/` |
## Project Rooms
| Room | Description | Path |
|---|---|---|
| `<slug>` | <summary, truncated to 80 chars> | `projects/<slug>/` |
---
_Initialized: YYYY-MM-DD — review imported rooms before first use_
<!--
NAVIGATION: Read this file first. Identify the relevant room(s), then read
only those. Do not load the full palace.
SIZE LIMIT: Keep this file under 50 lines.
-->Emit a summary:
locus-palace-init complete:
Source: <source dir> (<N> memory files found)
Palace: <palace dir>
Rooms created: <N>
Rooms skipped (already exist): <N>
Groups: infra=N tools=N data=N docs=N projects=N
Next steps:
1. Review each room file — imported content is verbatim, not canonical.
2. Reformat to palace conventions (remove the SOURCE/IMPORTED comment block).
3. Run /locus-consolidate on busy rooms once you start using the palace.If --dry-run was passed, prefix every write action with [dry-run] and skip all file I/O.
from auto-memory files, which are themselves auto-generated and may contain stale facts. Always review imported rooms before relying on them.
locus-consolidate on any room immediately if it has sessions/ logsthat were also imported.
--source and --palace defaults assume the standard Claude Codeauto-memory layout. Adjust if your setup differs.
rather than overwriting them. Use --overwrite explicitly to re-import.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.