Automated summary
Checks for drift between the repository and the running system, inspecting app signing, symlinks, scripts, and source code.
Strengths
- Automated detection of inconsistencies between source code and active environment.
- Verifies app signing with correct Team ID.
- Checks symlinks, script consistency, and source matching.
Limitations
- Specific to the Samara system and its repository structure.
- Cannot automatically fix all detected issues.
- Requires the 'fork' context to operate.
Use this skill after making script changes, before or after a rebuild, or when the system behaves unexpectedly.
Avoid using it if no changes have been made and the system is working fine, as it may unnecessarily consume resources.
Security analysis
SafeThe skill only runs a read-only check script and outputs results; no destructive or exfiltrating commands are executed.
No concerns found
How this analysis is madeExamples
Check for drift between the repo and the running system.Is the system in sync with the repository? Run a drift check before updating.name: sync description: Check for drift between repo and running system. Use when checking if scripts or Samara are out of sync, verifying system integrity, or before/after rebuilds. Trigger words: sync, organism sync, check drift, system drift, repo sync. context: fork allowed-tools:
- Bash
- Read
- Grep
Sync Skill
Check for drift between the repo and running system, and optionally fix it.
What This Does
Runs the sync-organism script to detect differences between:
~/Developer/samara-main/(the repo/genome)~/.claude-mind/(the running organism)/Applications/Samara.app(the built app)
Running the Check
~/.claude-mind/system/bin/sync-organism
What It Checks
- Samara.app Signing - Correct Team ID (G4XVD3J52J)
- Skills Symlinks - All skills properly linked from repo
- Script Drift - Differences between repo and runtime scripts
- Samara Source - Whether installed app matches source code
When to Use
- After making changes to scripts in either location
- Before/after
update-samararebuilds - During wake cycles (for monitoring)
- When something "should work but doesn't"
Output Example
## Samara.app Signing
[OK] Samara.app signed with correct Team ID: G4XVD3J52J
## Skills Symlinks
[OK] 10 skills properly symlinked
## Script Drift Analysis
[OK] All shared scripts are identical
## Samara.app Source Check
[OK] Samara.app is up to date with source
SUMMARY
Total drift: 0 issues
Fixing Drift
If drift is detected, the script shows commands to fix it. Common fixes:
- Copy runtime script to repo:
cp ~/.claude-mind/system/bin/X ~/Developer/samara-main/scripts/ - Rebuild Samara:
~/.claude-mind/system/bin/update-samara - Recreate symlinks: Run
sync-skillsor manually create symlinks
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/system-sync-check-mmh8qq09/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/system-sync-check-mmh8qq09' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/system-sync-check-mmh8qq09/download' --output '.skill-downloads/system-sync-check-mmh8qq09/SKILL.md.part' && mv '.skill-downloads/system-sync-check-mmh8qq09/SKILL.md.part' '.skill-downloads/system-sync-check-mmh8qq09/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/system-sync-check-mmh8qq09/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.