agentleFS
Sign inStart free
thefrederiksenthefrederiksen/cc-director/.claude/skills/cc-settings-api/SKILL.md

cc-settings-api

Skill96 starsChanged 16 days agoMITView on GitHub

RETIRED - the Director's Control API no longer exists (the remove-the-network-port mission deleted the listener), so settings can no longer be driven over local HTTP. Kept only to say where settings editing lives now.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If a task genuinely needs a settings capability the Gateway path does not offer, that is a gap to report on the thefrederiksen/devthrottle …

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CC Director Settings API Skill - retired

This skill drove a running Director's GET /settings and PUT /settings loopback routes. The remove-the-network-port mission (phase 5, 2026-08-03) deleted the Director's HTTP listener entirely, so those routes - and the loopback port they lived on - no longer exist on any current build. The configure_settings.py script in this directory cannot work against a current Director and must not be reached for.

Where settings editing lives now:

  • A person: the desktop application's Settings dialog (in process, no network). Gateway changes made there re-apply live, with no restart.
  • An agent on the same machine: cc-devthrottle settings get <key> / cc-devthrottle settings set <key> <value>, which read and write this machine's config.json directly on disk. Note the difference from the old API: a file edit does not tell the running Director to re-apply its Gateway connection - a gateway change made this way lands at the next Director start, so prefer the Settings dialog for connection changes on a running Director.
  • Remote configuration rides the Gateway's tunnel verbs (the same cores the old routes ran), driven from the Cockpit.

If a task genuinely needs a settings capability the Gateway path does not offer, that is a gap to report on the thefrederiksen/devthrottle repository, not a reason to resurrect a local port.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free