Agent Builder
shareAI-lab/learn-claude-code
Design and build AI agents for any domain. An agent skill from shareAI-lab/learn-claude-code.
A skill your agent uses when adding, renaming, removing, validating, or exposing mesh-llm config settings, including built-in settings, plugin config schemas, owner-control apply behavior, CLI…
$ npx skills add Mesh-LLM/mesh-llm --skill config-settings-management -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Mesh-LLM/mesh-llm config-settings-management --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Mesh-LLM/mesh-llm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/config-settings-management .claude/skills/config-settings-management && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "config-settings-management" agent skill from https://github.com/Mesh-LLM/mesh-llm/tree/main/.agents/skills/config-settings-management into .claude/skills/config-settings-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "config-settings-management", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Mesh-LLM/mesh-llm/tree/main/.agents/skills/config-settings-managementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Mesh-LLM/mesh-llm --skill config-settings-management -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Mesh-LLM/mesh-llm config-settings-management --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mesh-LLM/mesh-llm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/config-settings-management .agents/skills/config-settings-management && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "config-settings-management" agent skill from https://github.com/Mesh-LLM/mesh-llm/tree/main/.agents/skills/config-settings-management into .agents/skills/config-settings-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "config-settings-management", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Mesh-LLM/mesh-llm --skill config-settings-management -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Mesh-LLM/mesh-llm config-settings-management --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mesh-LLM/mesh-llm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/config-settings-management .cursor/skills/config-settings-management && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "config-settings-management" agent skill from https://github.com/Mesh-LLM/mesh-llm/tree/main/.agents/skills/config-settings-management into .cursor/skills/config-settings-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "config-settings-management", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Mesh-LLM/mesh-llm.git --path .agents/skills/config-settings-management--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Mesh-LLM/mesh-llm --skill config-settings-management -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Mesh-LLM/mesh-llm config-settings-management --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mesh-LLM/mesh-llm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/config-settings-management .gemini/skills/config-settings-management && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "config-settings-management" agent skill from https://github.com/Mesh-LLM/mesh-llm/tree/main/.agents/skills/config-settings-management into .gemini/skills/config-settings-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "config-settings-management", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Mesh-LLM/mesh-llm config-settings-managementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Mesh-LLM/mesh-llm --skill config-settings-management -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Mesh-LLM/mesh-llm.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/config-settings-management .github/skills/config-settings-management && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "config-settings-management" agent skill from https://github.com/Mesh-LLM/mesh-llm/tree/main/.agents/skills/config-settings-management into .github/skills/config-settings-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "config-settings-management", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Mesh-LLM/mesh-llm --skill config-settings-management -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Mesh-LLM/mesh-llm config-settings-management --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mesh-LLM/mesh-llm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/config-settings-management .opencode/skills/config-settings-management && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "config-settings-management" agent skill from https://github.com/Mesh-LLM/mesh-llm/tree/main/.agents/skills/config-settings-management into .opencode/skills/config-settings-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "config-settings-management", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
config-settings-managementA skill your agent uses when adding, renaming, removing, validating, or exposing mesh-llm config settings, including built-in settings, plugin config schemas, owner-control apply behavior, CLI…
Config Settings Management is an agent skill from Mesh-LLM/mesh-llm. Use this skill when adding, renaming, removing, validating, or exposing mesh-llm config settings, including built-in settings, plugin config schemas, owner-control apply behavior, CLI validation, and UI configuration surfaces.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in AI & LLM Engineering. The repository describes itself as: Distributed AI/LLM for the people. Share compute privately or publicly to power your agents and chat. The licence is Apache-2.0.
Read from SKILL.md and the folder at commit 43ddd24. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
cargonpmjustFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Config Settings Management loads about 1.4k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 468 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from Mesh-LLM/mesh-llm at commit 43ddd24, republished under its Apache-2.0 licence (© Mesh-LLM). 468 words, ~1,382 tokens.
.claude/skills/config-settings-management/SKILL.md (or your agent's skills folder).Use this skill before changing any setting that appears in
~/.mesh-llm/config.toml, the owner-control configuration API, the runtime
configuration UI, or an installed plugin's config_schema.
Config settings are not just struct fields. A complete setting has:
mesh/crates/mesh-llm-config/src/model.rs.mesh/crates/mesh-llm-config/src/authoring.rs when
code needs to create or mutate it.mesh/crates/mesh-llm-config/src/model/built_in_schema.rs when it is a core
mesh-llm setting.mesh/crates/mesh-llm-config/src/validate.rs, with
stable ConfigPath and canonical path metadata.mesh/crates/mesh-llm-host-runtime/src/config_schema.rs.mesh/crates/mesh-llm-host-runtime/src/runtime/config_state.rs when it can be
changed dynamically.mesh/crates/mesh-llm-host-runtime/src/api/,
mesh/crates/mesh-llm-host-runtime/src/protocol/, and
mesh/crates/mesh-llm-protocol/proto/node.proto when it crosses process or node
boundaries.mesh/crates/mesh-llm-ui/src/features/configuration/ and
mesh/crates/mesh-llm-host-runtime/tests/fixtures/.When adding or removing a built-in setting:
MeshConfig or the owning nested config struct in
mesh/crates/mesh-llm-config/src/model.rs.authoring.rs if generated configs,
tests, or command flows need to write the setting.model/built_in_schema.rs. Include owner, value schema, support state,
control surfaces, apply mode, restart scope, visibility, constraints, aliases,
and description.validate.rs. Prefer structured ConfigDiagnostic
helpers over plain string errors.version = 1 bumps for actual incompatible
persisted config format changes.mesh-llm config validate --config-path <fixture> --json for at least one
valid and one invalid representative file.Plugin settings are install-time schemas, not hard-coded built-in settings.
config_schema in
mesh/crates/mesh-llm-plugin/src/manifest.rs and
mesh/crates/mesh-llm-plugin/proto/plugin.proto.schema_version at
mesh_llm_config::SUPPORTED_PLUGIN_CONFIG_SCHEMA_VERSION unless the schema
format itself becomes incompatible. Tightening validation of existing v1
fields such as required, type, enum, object, array, or constraints does not
by itself require a schema version bump.mesh/crates/mesh-llm-host-runtime/src/plugin/config.rs and
mesh/crates/mesh-llm-config/src/plugin_validation.rs.[plugin.settings] is
absent.allow_unvalidated_config should produce warnings, not silently drop
diagnostics from success responses.mesh/crates/mesh-llm-host-runtime/src/runtime/config_state.rs.mesh/crates/mesh-llm-host-runtime/tests/fixtures/ are the
cross-check between Rust schema export and the TypeScript adapter.Run cargo commands serially. For config-surface changes, start with:
cargo test -p mesh-llm-config --lib
cargo test -p mesh-llm-host-runtime --lib schema_export
cargo test -p mesh-llm-host-runtime --lib runtime_config
cargo test -p mesh-llm-host-runtime --lib plugin_config
cargo test -p mesh-llm-plugin --lib
cargo test -p mesh-llm-plugin-manager --lib
cargo test -p mesh-llm-cli config_validate --lib
cargo test -p mesh-llm config_validate --lib
cargo check -p mesh-llm
cargo clippy -p mesh-llm-config -p mesh-llm-plugin -p mesh-llm-plugin-manager -p mesh-llm-host-runtime -p mesh-llm-cli -p mesh-llm --all-targets -- -D warningsAlso run the UI checks when the schema export or adapter changes:
cd mesh/crates/mesh-llm-ui
npm test -- --run src/features/configuration/api/config-adapter.test.ts
npm run typecheckUse the repo build gate before publishing broad changes:
just build© Mesh-LLM, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/config-settings-management of Mesh-LLM/mesh-llm.
Open the folder on GitHubat commit 43ddd24
Config Settings Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Config Settings Management this skillMesh-LLM/mesh-llm | 3.5k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Agent BuildershareAI-lab/learn-claude-code | 78k | 4 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Add Uint Supportpytorch/pytorch | 104k | 2 repos | ~2.3k | Automated safety check: Pass | Custom licence | |
| LLM Benchmarking with lm-evaluation-harnessOrchestra-Research/AI-Research-SKILLs | 13k | 8 repos | ~3k | Automated safety check: Pass | MIT | |
| Segment Anything Model GuideOrchestra-Research/AI-Research-SKILLs | 13k | 8 repos | ~3.3k | Automated safety check: Pass | MIT | |
| 1passwordtrpc-group/trpc-agent-go | 1.9k | 14 repos | ~656 | Automated safety check: Pass | Apache-2.0 |
shareAI-lab/learn-claude-code
Design and build AI agents for any domain. An agent skill from shareAI-lab/learn-claude-code.
pytorch/pytorch
Add unsigned integer (uint) type support to PyTorch operators by updating ATDISPATCH macros.
Orchestra-Research/AI-Research-SKILLs
Runs lm-evaluation-harness to benchmark language models on academic suites such as MMLU, GSM8K and HumanEval, compare models and track training checkpoints.
Orchestra-Research/AI-Research-SKILLs
Guide to using Meta's Segment Anything Model for zero-shot image segmentation with point, box or mask prompts, or automatic mask generation.
trpc-group/trpc-agent-go
Set up and use 1Password CLI (op). An agent skill from trpc-group/trpc-agent-go.
jarrodwatts/claude-code-config
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage.
Mesh-LLM/mesh-llm
A skill your agent uses when validating a MeshLLM release candidate or current HEAD against the last GitHub release, assembling the canonical feature/fix/modification inventory, testing locally…
Mesh-LLM/mesh-llm
A skill your agent uses when running, debugging, interpreting, or documenting mesh-llm benchmark tune model-serving throughput trials, including choosing…
Mesh-LLM/mesh-llm
A skill your agent uses when connecting agent tools or OpenAI clients to mesh-llm — launching or configuring Goose, Claude Code, OpenCode, Pi, curl, or any OpenAI-compatible client against a local…
Mesh-LLM/mesh-llm
A skill your agent uses when converting Hugging Face SafeTensors checkpoints into split BF16 GGUF model repos with skippy-quantize on Hugging Face Jobs or a local machine, then publishing the…
Mesh-LLM/mesh-llm
A skill your agent uses when creating, monitoring, validating, or documenting low-memory Hugging Face Jobs or local runs that quantize split BF16/FP16 GGUF model repos into custom quant GGUF repos…
Mesh-LLM/mesh-llm
A skill your agent uses when changing mesh-llm automation or CLI flows that discover Hugging Face GGUF models, plan CPU Hugging Face Jobs for layer-package splitting, estimate max cost, or publish…
Categories
A skill your agent uses when adding, renaming, removing, validating, or exposing mesh-llm config settings, including built-in settings, plugin config schemas, owner-control apply behavior, CLI…. Config Settings Management is an agent skill from Mesh-LLM/mesh-llm. Use this skill when adding, renaming, removing, validating, or exposing mesh-llm config settings, including built-in settings, plugin config schemas, owner-control apply behavior, CLI validation, and UI configuration surfaces.
Config Settings Management fits situations like: exposing mesh-llm config settings; including built-in settings; plugin config schemas; owner-control apply behavior.
Run `npx skills add Mesh-LLM/mesh-llm --skill config-settings-management -a claude-code`. Or copy the skill folder (.agents/skills/config-settings-management in Mesh-LLM/mesh-llm) into .claude/skills/config-settings-management in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Mesh-LLM/mesh-llm --skill config-settings-management -a codex`. Or copy the skill folder (.agents/skills/config-settings-management in Mesh-LLM/mesh-llm) into .agents/skills/config-settings-management in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Mesh-LLM/mesh-llm --skill config-settings-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/config-settings-management, .gemini/skills/config-settings-management, .github/skills/config-settings-management and .opencode/skills/config-settings-management in your project.
Going by SKILL.md and its folder, Config Settings Management needs the command-line tools its instructions call (cargo, npm and just).
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Config Settings Management is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Config Settings Management: Agent Builder (shareAI-lab/learn-claude-code, 78k stars), Add Uint Support (pytorch/pytorch, 104k stars), LLM Benchmarking with lm-evaluation-harness (Orchestra-Research/AI-Research-SKILLs, 13k stars) and Segment Anything Model Guide (Orchestra-Research/AI-Research-SKILLs, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Mesh-LLM (a GitHub organization) maintains it in Mesh-LLM/mesh-llm, which has 3,489 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 10, 2026.
Source: Mesh-LLM/mesh-llm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.