emasoft/amcos-config-snapshot
skills/amcos-config-snapshot/SKILL.md
Use when capturing config snapshots, detecting config changes, or resolving config version conflicts. Trigger with config management or snapshot needs. Loaded by ai-maestro-chief-of-staff-main-agent
data-ai
Updated Apr 26, 2026
$ install --global
skillsauthnpx skillsauth add emasoft/ai-maestro-chief-of-staff amcos-config-snapshotInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 26, 2026, 4:30 AM137.6s55 files scanned
SKILL.md
- name:
- amcos-config-snapshot
- description:
- Use when capturing config snapshots, detecting config changes, or resolving config version conflicts. Trigger with config management or snapshot needs. Loaded by ai-maestro-chief-of-staff-main-agent
- user-invocable:
- false
- license:
- Apache-2.0
- compatibility:
- Requires file system access to design/memory/ directory. Requires AI Maestro installed.
- author:
- Emasoft
- version:
- 1.0.0
- context:
- fork
- agent:
- ai-maestro-chief-of-staff-main-agent
Config Snapshot Management
Overview
Captures config state at session start, detects drift, and resolves conflicts.
Prerequisites
- Session memory initialized (
amcos-memory-initialization) - Config files in
design/config/(if AMOA installed)
Instructions
Copy this checklist and track your progress:
- [ ] Capture config snapshot at session start
- [ ] Detect, classify, and resolve conflicts
PROCEDURE 7: Capture Config Snapshot
Trigger: Session init, after loading memory, before work.
- Read configs from
design/config/ - Create snapshot with timestamp and file hashes
- Save to
design/memory/config-snapshot.md; record inactiveContext.md
Guide: See 19-config-snapshot-creation in Resources below
PROCEDURE 8: Detect Config Changes
Trigger: Every 30 min, before major tasks, on unexpected behavior.
- Read current configs and saved snapshot
- Compare timestamps; if different, compare hashes
- Classify changes; log in
activeContext.md; trigger Procedure 9 if critical
Guide: See 20-config-change-detection in Resources below
PROCEDURE 9: Handle Config Conflicts
Trigger: Critical changes detected or orchestrator request.
Types: A Non-Breaking, B Breaking-Future, C Breaking-Immediate, D Irreconcilable.
Steps: Classify (A-D), apply strategy, update snapshot.
Chief of Staff Integrations
Output
| Procedure | Result |
|-----------|--------|
| Capture Snapshot | config-snapshot.md with hashes |
| Detect Changes | Change report in activeContext.md |
| Handle Conflicts | Resolved per type, snapshot updated |
Error Handling
| Issue | Resolution | |-------|------------| | Config dir missing | Skip if AMOA not installed; log warning | | Snapshot corrupted | Re-capture from current configs | | Hash mismatch | Recalculate; check encoding | | Irreconcilable conflict | Stop work, escalate |
Examples
# Capture snapshot
uv run python scripts/amcos_memory_manager.py add-decision \
--decision "Config snapshot captured"
# Adopt config after Type B
uv run python scripts/amcos_memory_manager.py set-focus \
--focus "Adopting config v2.1 (Type B)"
Checklist
Copy this checklist and track your progress:
- [ ] Capture config snapshot at session start
- [ ] Detect changes periodically or before major tasks
- [ ] Classify and resolve any conflicts found
Resources
- 19-config-snapshot-creation — Snapshot creation procedures
- When you need to understand the overview
- Understanding config snapshots
- Why snapshots matter
- How to create snapshots
- Creating initial snapshot
- Updating snapshot
- Validating snapshot
- Understanding snapshot structure
- For implementation examples
- If issues occur
- 20-config-change-detection — Change detection methods
- When you need to understand the overview
- Understanding detection methods
- How to detect changes
- Timestamp-based detection
- Content-based detection
- Handling change notifications
- Periodic drift checking
- Classifying changes
- For implementation examples
- If issues occur
Related Skills
emasoft/amcos-context-management
data-ai
VerifiedTrustedCommunity
Use when managing context or patterns. Trigger with context update or compaction needs. Loaded by ai-maestro-chief-of-staff-main-agent
SKILL.mdUpdated Apr 26, 2026
emasoft/amcos-context-management-ref
data-ai
VerifiedTrustedCommunity
Use when consulting detailed context management references. Trigger with context management lookups. Loaded by ai-maestro-chief-of-staff-main-agent
SKILL.mdUpdated Apr 26, 2026
emasoft/amcos-config-snapshot-ref
data-ai
VerifiedTrustedCommunity
Use when consulting detailed config snapshot references. Trigger with config snapshot lookups. Loaded by ai-maestro-chief-of-staff-main-agent
SKILL.mdUpdated Apr 26, 2026
emasoft/amcos-agent-termination
data-ai
VerifiedTrustedCommunity
Use when terminating agents or performing clean shutdown. Trigger with agent termination or stop requests. Loaded by ai-maestro-chief-of-staff-main-agent
SKILL.mdUpdated Apr 26, 2026