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

92%

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

85%Weight 40%Scale 1-3

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 clear sequenced migration workflow, verification, rollback, and a single well-signaled bundle reference. The main weakness is minor redundancy between step 7 and the Secondary machine config section.

Suggestions

Merge the 'Secondary machine config' section into step 7 (or vice versa) to eliminate the repeated `./afs config set --mode mount/sync` instructions.

Consolidate the `worktrees/` exclusion guidance so it is stated once in 'Default stance' rather than reprised in the workflow step and 'Notes to surface'.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven without explaining concepts Claude knows, but the 'Secondary machine config' section repeats the `./afs config set --mode mount/sync` instructions already given in step 7, and `worktrees/` exclusion is restated three times — it could be tightened.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands throughout: `make`, `./afs ws import --mount-at-source .codex ~/.codex`, `./afs ws mount .codex ~/.codex`, `./afs status`, and concrete rollback commands.	3 / 3
Workflow Clarity	An explicit 8-step numbered migration sequence includes a verification step (step 8: `./afs status` and `ls -la ~/.codex`) and a rollback section for error recovery, so validation is present rather than missing for this destructive operation.	3 / 3
Progressive Disclosure	Well-organized sections with a single clearly-signaled, one-level-deep reference to a real bundled file ([assets/.afsignore](assets/.afsignore), verified to exist), keeping the SKILL.md an overview rather than a monolith.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 specific, trigger-led description that clearly states what the skill does and when to use it, with concrete actions and a distinct niche. It is third-person and free of vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'migrate Codex state in ~/.codex into Agent Filesystem', 'mount the same shared Codex memory/settings across multiple computers', 'Recommends a .afsignore', and 'defaults to excluding worktrees, caches, logs, and temporary files' — matches the anchor for several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (migrate/mount, recommend .afsignore, default exclusions) and when via the 'Use when the user wants to...' trigger clause, matching the both-what-and-when anchor.	3 / 3
Trigger Term Quality	Natural user phrasings are covered: 'migrate Codex state', 'shared Codex memory/settings across multiple computers', plus concrete exclusions like 'worktrees, caches, logs' that a user of this skill would actually say; not jargon-only.	3 / 3
Distinctiveness Conflict Risk	The niche is narrow and distinct — Codex state in ~/.codex synced via Agent Filesystem/Redis across machines — so it is unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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: 3100b31

Reviewed: 10 days 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.