codex-settings-sync

Use when the user wants to migrate Codex state in ~/.codex into Agent Filesystem and mount the same shared Codex memory/settings across multiple computers. Recommends a .afsignore before migration and defaults to excluding worktrees, caches, logs, and temporary files.

1.61x

Quality

96%

Does it follow best practices?

Impact

100%

1.61x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, highly actionable skill body with a clearly sequenced destructive-operation workflow that includes verification and rollback, plus a well-signaled one-level reference to a verified bundle file.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or re-explanation of concepts Claude already knows; every line (default stance, numbered workflow, rollback commands) earns its place.	5 / 5
Actionability	Fully executable copy-paste commands throughout (./afs ws import, ./afs config set --mode mount, ./afs ws unmount, rm -rf rollback) covering the common migration and rollback cases.	5 / 5
Workflow Clarity	Clear 8-step numbered sequence with an explicit verification checkpoint (./afs status and ls -la ~/.codex) and separate rollback procedures for a destructive operation involving rm -rf.	5 / 5
Progressive Disclosure	Well-organized into focused sections with a single one-level-deep reference to the real bundled assets/.afsignore (verified present); no nested references or inlined bulk content.	5 / 5
	Total	20 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with an explicit trigger clause and concrete actions covering migration, mounting, and ignore-file defaults. Only minor gap is the absence of synonyms/file-extension terms in the trigger.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — migrate ~/.codex into Agent Filesystem, mount across multiple computers, recommend a .afsignore, and default exclusions — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both 'what' (migrate Codex state into Agent Filesystem and mount it across machines) and 'when' via a clear 'Use when...' trigger clause with concrete phrasing.	5 / 5
Trigger Term Quality	Includes natural trigger phrasing ('Use when the user wants to migrate... mount the same shared... across multiple computers') with relevant terms, though it lacks synonyms and file-extension variants that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Codex settings sync via Agent Filesystem) with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: redis/agent-filesystem
Path: skills/codex-settings-sync/SKILL.md
Commit: c23daa6

Reviewed: 13 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.