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.
88
81%
Does it follow best practices?
Impact
100%
1.61xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted description that clearly defines both what the skill does and when to use it, with a distinct niche that minimizes conflict risk. The main weakness is that trigger terms lean technical and may miss more casual user phrasings like 'sync my settings' or 'share config across machines'. Overall it performs strongly across most dimensions.
Suggestions
Add more natural-language trigger variations such as 'sync settings', 'share configuration', 'backup codex config', or 'use codex on multiple machines' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: migrate Codex state, mount shared memory/settings across computers, recommend .afsignore, exclude worktrees/caches/logs/temporary files. These are detailed and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (migrate Codex state into Agent Filesystem, mount shared settings, recommend .afsignore, exclude certain file types) and 'when' (opens with 'Use when the user wants to migrate Codex state... across multiple computers'). | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'migrate', 'Codex', '~/.codex', 'Agent Filesystem', '.afsignore', and 'shared memory/settings', but these are fairly niche/technical. Missing common user phrasings like 'sync settings', 'share config', 'backup codex', or 'multiple machines'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific niche: migrating Codex state into Agent Filesystem across multiple computers. The combination of 'Codex', '~/.codex', 'Agent Filesystem', and '.afsignore' creates a very distinct trigger profile unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with a well-sequenced migration workflow, concrete CLI commands, and thoughtful inclusion of rollback procedures. Its main weaknesses are minor redundancy between the workflow steps and the secondary machine config section, and a reference to a bundle asset that isn't provided. Overall it serves its purpose well as a practical guide for syncing Codex settings across machines.
Suggestions
Consolidate the 'Secondary machine config' section into step 7 of the migration workflow to eliminate redundancy and improve conciseness.
Ensure the referenced assets/.afsignore file is included in the bundle so the progressive disclosure reference is functional.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some redundancy—e.g., the 'Secondary machine config' section partially repeats step 7 of the migration workflow. The 'Notes to surface' section is useful but a couple items could be tightened. Overall reasonable but not maximally lean. | 2 / 3 |
Actionability | Provides specific, executable CLI commands throughout (afs ws import, afs ws mount, afs config set, afs ws unmount), concrete file paths, and clear rollback commands. The guidance is copy-paste ready and leaves little ambiguity about what to run. | 3 / 3 |
Workflow Clarity | The migration workflow is clearly sequenced with 8 numbered steps, includes a pre-migration validation step (.afsignore creation), a verification step (afs status + ls), and a dedicated rollback section with distinct paths for source vs secondary machines. The instruction to stop Codex first and the choice-point callout for worktrees/ serve as important checkpoints. | 3 / 3 |
Progressive Disclosure | References the bundled asset [assets/.afsignore] which is good progressive disclosure, but no bundle files were actually provided, making the reference unverifiable. The content is reasonably structured with clear sections, but the 'Secondary machine config' section could have been folded into the workflow or split out more cleanly. For a skill of this length, the organization is adequate but not exemplary. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- redis/agent-filesystem
- Commit
ef5c9a4
- Reviewed
Table of Contents
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.