Edit Config

Community

Mizoreww

edit-config

Inspect, add, change, remove, repair, or update Claude and Codex configuration from Mizoreww/awesome-agent-config on main. Use for configuration queries and edits, installed skills/plugins/rules/MCP, and changes to this repository's configuration templates or catalogue.

Overview

Publisher	Mizoreww
Repository	`awesome-agent-config`
Skill name	`edit-config`
Stars	260
Forks	38
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Mizoreww on GitHub. Read the source before you install it.

Installation

Install the Edit Config AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Mizoreww/awesome-agent-config/tree/main/skills/edit-config
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Mizoreww/awesome-agent-config.git /tmp/awesome-agent-config
mkdir -p .claude/skills
cp -r /tmp/awesome-agent-config/skills/edit-config .claude/skills/edit-config

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Edit Config in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Edit Config on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Edit Config is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Edit agent configuration

This skill serves both Claude and Codex and tracks one repository branch:

Repository: https://github.com/Mizoreww/awesome-agent-config.git
Branch: main

1. Identify the request and target

Distinguish inspection from modification, and repository edits from changes to an installed agent. Default to the current conversation's agent; target both only when requested. Resolve the actual CLAUDE_CONFIG_DIR, CODEX_HOME, or user-selected home. Read relevant configuration, agent-config/selection.json, and agent-config/files.json when present; use native lists to verify installed state. Redact credentials.

For inspection, report current values, selected content, sources, differences, and pending items directly in the conversation as relevant. Export a document only when requested. Reading configuration does not authorize writing receipts, changing settings, installing dependencies, or disabling imports. Stop when the query is answered unless the user also requested a change.

Completion: the operation, target, existing state, and authorization are clear.

2. Resolve the branch for changes

Fetch the branch above into a fresh temporary checkout and resolve its full commit SHA. Use files from that same SHA throughout an installation/update operation. Preserve existing user checkouts and local edits. A missing branch or incompatible layout is an error; report it without substituting another branch or the remote default.

For installed configuration, compare the receipt's repository URL and update policy with this target. Read repository identity and migration from the resolved source: equivalent HTTPS/SSH URLs and the documented repository rename identify the same source. Matching branch records can proceed; a default-branch policy can proceed when the remote default resolves to main, preserving that policy. Missing source metadata uses this skill's explicit target without inventing installation ownership. A conflicting fork, branch (including agent-config-for-agents), pinned commit, or local source remains unchanged until the user chooses migration; reuse an already explicit migration request instead of asking again. Record the previous source when migrating, and keep all selections, hashes, and backups.

For repository edits, use the user's designated checkout on main or their chosen work branch, verify its repository and branch, and read its current MAINTAIN.md. Preserve authorized uncommitted changes and work with them. Installation changes still use a single resolved source as described above.

Completion: the source, revision, and any source migration are established.

3. Apply the requested operation

Installed configuration: read INSTALL.md, catalog.md, and the target platform's README from the resolved source. Follow their native plugin/MCP, protected file, and verification procedures. Default to recorded selections. For additions or changed selections, follow INSTALL.md's choose-options procedure: show the target agent's complete supported catalogue directly in the conversation, with category grouping, continuous item numbers, useful descriptions, author recommendations and installed status. Prefer a real multi-select question tool when available; otherwise accept multiple numbers or names in chat. Export a selection document only when requested. Reuse explicit choices; wait for an actual response when choices are missing. Recommendations do not authorize installation.
Repository configuration: follow MAINTAIN.md for templates, skills, catalogue entries, recommendations, and documentation. Editing repository files does not modify an agent home.

Handle retired or renamed IDs using docs/migration.md. Omitted selections remain installed. Removal requires an explicit request and ownership checks. Preserve upstream revision constraints, local customizations, credentials, hooks, memory databases, and each agent's real lessons. Continue within the user's existing authorization.

Completion: each requested change has an actual result, including failures and pending steps.

4. Verify and record

Verify the changed files or native resources. For installed changes, record the canonical repository.url, actual repository.revision, and the policy established in step 2: repository.update = {"kind":"branch","ref":"main"} for the explicit target, or the retained {"kind":"default-branch"} policy. Preserve previous source metadata when normalizing the renamed URL, plus per-item revisions and provenance. Repository edits follow their own commit and validation workflow. A repository version alone does not establish installation success.

Report what changed and what remains pending. Keep the two agent homes and their records independent. The old update-config / update_config names migrate to this skill through the repository's migration instructions.

Frequently asked questions

What does the Edit Config AI skill do?

Why use Edit Config on TypingMind?

Because you install it once and use it with any model. Edit Config is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Edit Config in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Mizoreww/awesome-agent-config/tree/main/skills/edit-config. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Edit Config?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Edit Config?

As many as you like. As long as a model supports skills, you can use Edit Config with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Edit Config AI skill free?

Yes. It is published on GitHub by Mizoreww under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Algorithmic Art

anthropics

OrganizationPopular

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or…

Doc Coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This…

Authoring Skills

How to create and maintain agent skills in .agents/skills/. Use when creating a new SKILL.md, writing skill descriptions, choosing frontmatter fields, or deciding what content belongs in a skill vs…

Dce Edge

DCE-safe require() patterns and edge runtime constraints. Use when writing conditional require() calls, guarding Node-only imports (node:stream etc.), or editing define-env-plugin.ts / app-render /…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Edit agent configuration

1. Identify the request and target

2. Resolve the branch for changes

3. Apply the requested operation

4. Verify and record

Frequently asked questions

Related AI Skills

Set up your own AI workspace now