Configuration

Community

alfredxw

configuration

Use when a Project Agent reads or changes lore indexes and group memberships, managed presets, game modules, automations, Skills, or Agent profiles through config_read and config_apply.

Overview

Publisher	alfredxw
Repository	`denova`
Skill name	`configuration`
Stars	906
Forks	143
Bundled files	10
License	Apache-2.0
Links	Skill source Repository Homepage

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.
10 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by alfredxw on GitHub. Read the source before you install it.

Installation

Install the Configuration 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/alfredxw/denova/tree/master/skills/configuration
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/alfredxw/denova.git /tmp/denova
mkdir -p .claude/skills
cp -r /tmp/denova/skills/configuration .claude/skills/configuration

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

Use it in TypingMind

Enable Configuration 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 Configuration 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 Configuration 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.

Configuration

Manage every supported configuration resource through the stable config_read and config_apply tools. Never edit Denova configuration files or internal JSON storage directly.

Required workflow

For an unfamiliar resource, call config_read with operation=describe. Omit resource to discover all registered kinds, or provide one kind for its contract.
Call config_read(operation=list) to resolve the exact ID and scope. Catalogs use items plus next_cursor; continue with the identical request and returned cursor until truncated=false when the full catalog matters. Before an update or delete, call config_read(operation=get) for the exact ID and retain its latest revision.
Read exactly the relevant reference below with read({"path":"skill://configuration/references/<file>.md"}). Do not infer a value shape from another resource.
Follow that resource's mutation semantics. Call config_apply for exactly one create, update, or delete and use only names returned by describe.
For update and delete, copy the latest revision from config_read; never guess, copy an example placeholder, or reuse a stale revision. Preserve every field or layer section the user did not ask to change.

get accepts any number of IDs. A mixed batch succeeds with existing items, explicit missing_ids, and per-ID failures; an entirely unsuccessful completed batch fails. Large exact reads also return next_cursor. Never treat truncated=true as a complete read. 6. config_apply returns only a compact persistence receipt (resource, operation, id, revision). Read the changed item again and compare the requested fields plus preservation-sensitive fields. Report success only when the effective result matches.

Deletion must be explicitly requested by the user. If a stale-revision conflict occurs, read the current item again, reconcile the requested change with that value, and retry once with the new revision. Do not silently overwrite concurrent changes.

Mutation semantics

Resources	Update behavior
`narrative_style`, `story_director`, `event_package`, `rule_system`, `state_system`, `image_preset`	Complete editable-resource replacement. Start from `get`, change only requested fields, and submit the complete editable value. Omitted arrays and objects are cleared or defaulted.
`automation`	Sparse patch. Omitted fields stay unchanged; a present `triggers` array replaces the whole trigger list. `target` is create-only and immutable.
`agent_profile`	Fixed Agents use sectional layered updates. A `custom_agent` mutation is user-only and replaces its complete independent definition; General SubAgent and custom SubAgent mutations follow the resource reference.
`skill`	Complete replacement of one root `SKILL.md` or one supporting reference file. The root revision covers the whole Skill directory.
`style_reference`	Create writes one document; update replaces its complete Markdown content.
`lore_index`	Workspace singleton `index`. Update replaces the complete guide: introduction, ordered custom groups and automatic-group detail overrides. Removing a group backs up the collection and clears only its associations.
`lore_index_membership`	One existing lore item by ID. Update replaces only its complete `index_memberships` array; `[]` restores automatic grouping. Apply independently per item, preserving unrelated associations.

Fields returned for inspection such as path, custom, builtin_overridden, invalid, error, timestamps, resolved snapshots, run history, and secrets are host-owned unless the resource reference explicitly says otherwise. Never add an unknown field: configuration values reject unknown keys.

Examples use REVISION_FROM_GET as a visible placeholder. Always replace it with the exact current revision returned for the same resource, ID, and scope.

Reference routing

style_reference → skill://configuration/references/style-reference.md
narrative_style → skill://configuration/references/narrative-style.md
story_director → skill://configuration/references/story-director.md
event_package → skill://configuration/references/event-package.md
rule_system → skill://configuration/references/rule-system.md
state_system → skill://configuration/references/state-system.md
image_preset → skill://configuration/references/image-preset.md
automation → skill://configuration/references/automation.md
skill → skill://configuration/references/skill.md
agent_profile → skill://configuration/references/agent-profile.md
lore_index, lore_index_membership → skill://configuration/references/lore-index.md

For lore index organization, use these configuration resources. For creating or editing lore bodies, use query_lore_items with detail=full and write_lore_items when available. Do not pass index fields to write_lore_items or edit the backing JSON directly. Index management applies to the current project in both writing and game configuration pages; it does not enable configuration mutations during game play.

These are references, not sub-Skills. Do not pass a sub_skill argument or invoke another Skill name.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Configuration AI skill do?

Use when a Project Agent reads or changes lore indexes and group memberships, managed presets, game modules, automations, Skills, or Agent profiles through config_read and config_apply.

Why use Configuration on TypingMind?

Because you install it once and use it with any model. Configuration 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 Configuration in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/alfredxw/denova/tree/master/skills/configuration. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Configuration?

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 Configuration?

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

Is the Configuration AI skill free?

Yes. It is published on GitHub by alfredxw under the Apache-2.0 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

Apple Reminders

openclaw

OrganizationPopular

List, add, edit, complete, or delete Apple Reminders and reminder lists via remindctl.

Clawhub

Search ClawHub for skills when a requested capability is not already available; install, verify, update, uninstall, publish, or sync skills.

Diagnosing Superpowers

obra

CommunityPopular

Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so…

Brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Configuration

Required workflow

Mutation semantics

Reference routing

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now