Guide · Agent skill
How to use the Project Settings Viewer agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The settings skill is an agent skill for Claude Code that shows or changes the configuration of a project in the Claude Code Game Studios framework. It reads the team-wide project.yaml and the per-developer project.local.yaml, so you can check a value or change one without editing YAML by hand. This guide explains what the skill does, how to install it, how to ask for it in plain language, and what to watch for before it writes anything.
Project Settings ViewerDonchitos/Claude-Code-Game-Studios · MIT Download the skill Quick start
- 1Download and unzip. Download the ZIP from this page and unzip it so the settings folder is available.
- 2Place the skill. Copy the settings folder into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder.
- 3Confirm prerequisites. Make sure the project has a project.yaml from /start and the yaml-helper.sh hook in .claude/hooks/.
- 4View your settings. Run /settings to see effective values and where each one comes from.
- 5Change a personal value. Use /settings --local key=value to write a per-developer override in project.local.yaml.
- 6Change a team value. Use /settings key=value to write to project.yaml, then review the key and confirm the write.
What is an agent skill, and what does the settings skill do?
An agent skill is a folder containing a SKILL.md file that gives an AI agent specific instructions and permissions for one task. The agent loads the skill when it is invoked or when a request matches it.
When this skill runs, the agent can show the current project configuration or change a single setting. project.yaml holds team-wide settings, and project.local.yaml holds per-developer overrides. The skill validates values against allowed options, reports which settings are effective after merging the two files, and warns when a setting is documented but no part of the project reads it, so it does not appear to work when it has no effect.
- View all settings, or view one key by its dotted path, such as modes.review_mode.
- Set a value in project.yaml (team-wide) or with the --local form in project.local.yaml (personal).
- Warn when a setting has no effect in the project.
- Refuse nothing silently: a write to a reserved key is stored, but the skill reports that nothing reads it.
Install the settings skill
Download the ZIP file from this page and unzip it. Then place the settings folder in one of two locations. For a personal install available to all your projects, use ~/.claude/skills/. For a single project, use the .claude/skills/ folder inside that project.
If you use the Claude apps instead, open Settings, go to Capabilities, and upload the skill under Skills.
- Personal install: ~/.claude/skills/settings/
- Project install: .claude/skills/settings/ inside your project folder
- Claude apps: Settings → Capabilities → Skills, then upload the skill
Check the requirements before you use it
The skill is built for the Claude Code Game Studios framework. It needs a project.yaml created by the framework's /start skill, and it needs the yaml-helper.sh script at .claude/hooks/yaml-helper.sh. If that hook is missing, the skill reports that this is not a CCGS project and stops.
It also needs Claude Code, or another SKILL.md-compatible agent, and a Bash shell for the yaml-helper.sh and config-set.sh scripts.
- Claude Code, or a SKILL.md-compatible agent
- A Bash shell available to the agent
- An existing project.yaml created by /start
- The framework's yaml-helper.sh hook in .claude/hooks/
How to trigger the skill with natural requests
The skill accepts four forms of argument. You can type them as a slash command, and the argument hint shows the options: [key | key=value | --local key=value]. Plain requests such as asking the agent to show your settings should also work when the skill matches the request.
A key is a dotted YAML path such as modes.review_mode or testing.strict.logic. A set command uses key=value. The --local prefix writes to project.local.yaml instead of project.yaml.
- /settings — show all effective values
- /settings modes.review_mode — show one value
- /settings modes.review_mode=full — change the team-wide value in project.yaml
- /settings --local modes.review_mode=lean — set a personal override in project.local.yaml
/settings
/settings modes.review_mode
/settings modes.review_mode=full
/settings --local modes.review_mode=leanRead the output: effective values and overrides
In view-all mode, each setting is shown with its effective value and its source. If a personal override in project.local.yaml shadows a value in project.yaml, the output labels it as a local override and shows the yaml value it hides.
Some settings are locked, so a local override is not allowed for them. The skill checks this for each key. Validation errors are reported with the file they came from, so you can tell project.yaml and project.local.yaml problems apart.
- LOCAL OVERRIDE: the personal file is changing the team value.
- Source in brackets, such as (project.yaml), shows where the value came from.
- Validation errors are tagged with their file name.
Safety notes: scripts and writes
The skill runs scripts: yaml-helper.sh and config-set.sh. It does not use the network. Its allowed commands are limited to the listed helper functions, and it is set to run the plain form of each helper call.
Writes to project.yaml are a schema_changes decision, so the skill asks for confirmation before changing team-wide config, even in autonomous mode unless you have removed schema_changes from your always-ask list. Review which key is being changed before you confirm. Changing the wrong key in a shared file affects the whole team.
- Scripts run: yes. Network use: no.
- Writes to project.yaml ask for confirmation.
- Use --local for personal experiments so the shared file is not touched.
- Review the key name before confirming a write.
Tips for using the settings skill well
Start with a view-all run before changing anything, so you can see the effective value and its source. Use --local when you want a personal change, and leave project.yaml for decisions the team agrees on.
If a setting shows no effect after you change it, check the reserved-setting warning. The skill reports settings that no skill or hook reads, so a successful save does not always mean the behaviour changes.
- View first, then change.
- Use --local for personal preferences.
- Pay attention to reserved-setting warnings.
- Keep an eye on which file a validation error comes from.
What people use it for
- Checking which review mode a project is using before a session.
- Setting a shared team value in project.yaml that everyone inherits.
- Keeping a personal override in project.local.yaml without changing the shared file.
- Finding out whether a documented setting actually has an effect before relying on it.
Frequently asked questions
How do I install the settings agent skill?
Download the ZIP from this page and unzip it. Place the settings folder in ~/.claude/skills/ for personal use or in your project's .claude/skills/ folder, or upload it in the Claude apps under Settings → Capabilities → Skills.
What do I need to use it?
You need Claude Code or another SKILL.md-compatible agent, a Bash shell, and a project created with the Claude Code Game Studios framework that has a project.yaml from /start. The yaml-helper.sh hook must be present, or the skill stops.
Is the settings skill free, and what is its licence?
The source repository for this skill is listed under the MIT licence. This page does not state any price, so check the directory listing for current terms.
Does the settings skill use the internet?
No. The skill is listed as not using the network, but it does run scripts, namely yaml-helper.sh and config-set.sh.
What is the difference between project.yaml and project.local.yaml?
project.yaml holds team-wide settings and is committed to the repository. project.local.yaml holds per-developer overrides and is gitignored, so each developer can set personal values.
Why did my setting save but nothing changed?
Some documented settings are not read by any skill or hook, so setting them has no effect. The skill warns about these settings, but the value is still stored.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits developers and team leads using the Claude Code Game Studios framework who want to view or adjust project.yaml settings without hand-editing YAML. It is not suitable for projects outside that framework, or for anyone who wants to change settings without reviewing the key they are changing.
Download the skill