Skip to content

Guide · Agent skill

How to use the CCS Align Memory Seat agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The CCS Align skill turns an agent into a scheduled "seat" for the claude-mem memory plugin. It checks that your local claude-mem worker is healthy, pulls recent notable observations into a separate cache file, and can compare your house, project and seat rule files for conflicts. This guide is for developers who already run claude-mem and want a curated hourly cache; after reading it you should be able to install the skill, trigger it with plain requests and understand what it writes.

CCS Align Memory Seatthedotmack/claude-mem · Apache-2.0

Quick start

  1. 1Confirm the worker is running. Make sure the local claude-mem worker is up on your user's port before asking the agent to do anything.
  2. 2Install the skill. Unzip the downloaded ZIP into ~/.claude/skills/ for personal use or a project's .claude/skills/ folder, or upload it under Settings, Capabilities, Skills.
  3. 3Ask for a cycle run. Send a plain request such as "Run CCS Align" or "Breathe the alignment seat" and let the agent resolve the port and check health.
  4. 4Review the middle cache. Look at ~/.claude-mem/ccs-align/<viewerId>/middle.jsonl to confirm new observations were appended without duplicates.
  5. 5Exclude or restore an observation. Ask the agent to exclude or restore a specific observation; the change applies to the compiled cache, not the underlying history.
  6. 6Walk the rules. Ask the agent to walk rules or check rules conflicts, then read the append-only rules-report.md.

What the ccs-align skill makes the agent do

An agent skill is a folder with a SKILL.md file that tells the agent how to perform a specific task. This one is the CCS Align seat's hourly cycle. Once an hour it confirms the local claude-mem worker is up, searches for recent needle observations (decisions, bugfixes, security alerts and similar types), fetches their details and appends new records to a seat-owned cache file at ~/.claude-mem/ccs-align/<viewerId>/middle.jsonl, skipping duplicates.

The skill can also mark observations as excluded so they are filtered out of the compiled cache, and it can walk your house, project and seat rule layers to report conflicts. Conflict types it names are SHADOW_HOUSE, DENY_ALLOW, DRIFT and CLOCK_HEADER, written to an append-only rules-report.md.

  • Checks worker health before doing anything else
  • Pulls observations through search, timeline and get_observations
  • Writes a deduplicated middle cache with atomic replacement
  • Manages exclude marks on cached observations
  • Reports rules conflicts in an append-only rules-report.md

What the skill does not do

The skill does not delete history. Exclude marks only filter the compiled middle cache; the diary and SQLite database remain authoritative. It also does not enforce rules, restart the worker or write profile.md. The SKILL.md states that the rules walker only reports conflicts, and that SHADOW_HOUSE leaf patches are off by default.

Install the ccs-align skill

Download the ZIP from this page and unzip it. For a personal install, place the skill folder in ~/.claude/skills/. To limit it to one project, place it in that project's .claude/skills/ folder instead.

You can also upload the skill in the Claude apps: open Settings, go to Capabilities, then Skills, and add the ZIP there.

  • Personal install: ~/.claude/skills/ccs-align/
  • Project install: .claude/skills/ccs-align/ inside your project

Check the requirements before you run it

Every step depends on a local claude-mem worker. The skill talks to that worker on a per-user port, around 37700, and never to the cloud CMEM service. It needs Node.js, which it uses to read the port from your settings file, plus curl. The settings file at ~/.claude-mem/settings.json is optional and holds overrides.

  • Local claude-mem worker running
  • Node.js installed
  • curl available
  • Optional: ~/.claude-mem/settings.json overrides

Resolve the worker port and check health

Before any pull, the skill resolves the worker port once and reuses it. The port comes from the CLAUDE_MEM_WORKER_PORT environment variable, then the settings file, then the per-user default. Ports are per-user, so the skill does not hardcode 37777. If the health check fails, the skill aborts with a one-line miss.

WORKER_PORT="${CLAUDE_MEM_WORKER_PORT:-$(node -e "...")}"

Run the hourly breathing cycle

The cycle runs in a fixed order: health check, search for needle observations since the last cursor, timeline around the newest result, get_observations for the collected ids, then grab the middle cache, append new records, filter exclude marks and replace the file atomically. The skill is designed for a weekday house board and has one purpose per run.

  • Health: GET /api/health or GET /health
  • Search: needle observations since the cursor
  • Timeline: anchored on the newest result
  • get_observations: fetch full records
  • Grab, append, filter exclude-marks, replace

Settings you can override

Defaults live in SettingsDefaultsManager.ts and can be overridden in ~/.claude-mem/settings.json. The master switch is CLAUDE_MEM_CCS_ALIGN_ENABLED, which defaults to true. The viewer ids default to ccs-align, and the trigger types default to decision, bugfix, security_alert and sensitive. The patch gate CLAUDE_MEM_CCS_ALIGN_PATCH_SHADOWS defaults to false, meaning report-only.

  • CLAUDE_MEM_CCS_ALIGN_ENABLED (default true)
  • CLAUDE_MEM_CCS_ALIGN_VIEWER_IDS (default ccs-align)
  • CLAUDE_MEM_CCS_ALIGN_TRIGGER_TYPES (default decision,bugfix,security_alert,sensitive)
  • CLAUDE_MEM_CCS_ALIGN_PATCH_SHADOWS (default false)

What people use it for

  • Keeping an hourly cache of recent decisions and bugfixes from claude-mem for quick review
  • Excluding a sensitive observation from the compiled middle cache while keeping the underlying record
  • Checking a team's house, project and seat rule files for shadowed or conflicting lines
  • Checking the Worker Watch board to see whether the seat's cycle is running

Frequently asked questions

How do I install the ccs-align skill?

Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. You can also upload the ZIP in the Claude apps under Settings, Capabilities, Skills.

What do I need before running ccs-align?

You need a local claude-mem worker running on your per-user port, around 37700, plus Node.js and curl. The skill reads optional overrides from ~/.claude-mem/settings.json.

Is ccs-align free to use?

The source is licensed under Apache-2.0. Check the repository licence for the full terms before redistributing.

Does ccs-align delete my claude-mem history?

No. The SKILL.md states it does not delete history. Exclude marks only filter the compiled middle.jsonl cache, and the diary and SQLite stay authoritative.

Does the skill run scripts and use the network?

Yes, it runs scripts and makes network calls, but only to your local claude-mem worker on your per-user port, not to a cloud service.

What is the alternative if I do not use claude-mem?

The skill cannot work without a local claude-mem worker, since every step depends on it. Users without claude-mem should choose a different memory or rules tool.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

This skill suits developers already running a local claude-mem worker who want an hourly, deduplicated cache of key observations, or teams that keep layered agent rule files and want conflict reports. It is not useful without claude-mem, and it will not delete history or enforce rules on your behalf.

Download the skill