How do I install the Clear Configs skill?

Run npx skillmds@latest add automattic/clear-configs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Clear Configs safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Clear Configs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Clear Configs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Clear Configs?

Automattic (@automattic) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Clear Configs by automattic — Agent Skill

Name: Clear Configs
Author: Automattic

Clear Configs

Remove the local config files written by first-time setup (bucket.json and the agentic-analytics AWS profile). Leaves the events cache alone. Use when the user wants to start setup over, entered the wrong bucket name, or asks to reset/clear the plugin's configuration.

Automattic faeac3b 2.2 KB Updated Sep 17, 2026

File contents

Clear local configs

Removes two things to put the user back at first-run state:

${XDG_CONFIG_HOME:-~/.config}/agentic-analytics/bucket.json – runtime config init writes.
The agentic-analytics profile in ~/.aws/credentials and ~/.aws/config – the AWS creds the user set up via aws configure.

Leaves the data lake at ${AGENTIC_ANALYTICS_DATA_DIR:-~/.local/share/agentic-analytics}/ (DPL parquet + catalog.duckdb, and the plugin's venv/) alone. Re-pulling DPL is slow; the lake is data, not config. To rebuild it, run /agentic-analytics:refresh-cache instead.

After running this, the init flow walks the user through setup again from scratch (asks for the bucket, walks them through aws configure).

Output discipline

This is a one-shot housekeeping flow. Output the verbatim line below at the start, run the script, then stop. Don't narrate the script output.

Steps

Resolve the plugin root. The snippet below assumes $plugin_root is set in that shell invocation:
```
plugin_root="${CLAUDE_PLUGIN_ROOT:-${CURSOR_PLUGIN_ROOT:-<plugin-root>}}"
plugin_python="${AGENTIC_ANALYTICS_VENV:-${AGENTIC_ANALYTICS_DATA_DIR:-$HOME/.local/share/agentic-analytics}/venv}/bin/python"
[ -x "$plugin_python" ] || plugin_python="python3"
```
<plugin-root> is the plugin's install directory – the directory two levels above this SKILL.md file. In a dev checkout of the source repo that's plugin/. $plugin_python is the plugin's isolated venv (created by the init flow at $AGENTIC_ANALYTICS_DATA_DIR/venv, default ~/.local/share/agentic-analytics/venv); it falls back to python3 if the venv doesn't exist yet.
Announce. Output verbatim:

Clearing local agentic-analytics configs. Events cache stays put.
Run the script. It prints what was cleared (or (nothing to clear) if everything was already gone):
```
"$plugin_python" "$plugin_root/scripts/clear_configs.py"
```

---name: clear-configsdescription: Remove the local config files written by first-time setup (bucket.json and the agentic-analytics AWS profile). Leaves the events cache alone. Use when the user wants to start setup over, entered the wrong bucket name, or asks to reset/clear the plugin's configuration.---# Clear local configsRemoves two things to put the user back at first-run state:- `${XDG_CONFIG_HOME:-~/.config}/agentic-analytics/bucket.json` – runtime config init writes.- The `agentic-analytics` profile in `~/.aws/credentials` and `~/.aws/config` – the AWS creds the user set up via `aws configure`.Leaves the data lake at `${AGENTIC_ANALYTICS_DATA_DIR:-~/.local/share/agentic-analytics}/` (DPL parquet + `catalog.duckdb`, and the plugin's `venv/`) alone. Re-pulling DPL is slow; the lake is data, not config. To rebuild it, run `/agentic-analytics:refresh-cache` instead.After running this, the init flow walks the user through setup again from scratch (asks for the bucket, walks them through `aws configure`).## Output disciplineThis is a one-shot housekeeping flow. Output the verbatim line below at the start, run the script, then stop. Don't narrate the script output.## Steps0. **Resolve the plugin root.** The snippet below assumes `$plugin_root` is set in that shell invocation: ```bash plugin_root="${CLAUDE_PLUGIN_ROOT:-${CURSOR_PLUGIN_ROOT:-<plugin-root>}}" plugin_python="${AGENTIC_ANALYTICS_VENV:-${AGENTIC_ANALYTICS_DATA_DIR:-$HOME/.local/share/agentic-analytics}/venv}/bin/python" [ -x "$plugin_python" ] || plugin_python="python3" ``` `<plugin-root>` is the plugin's install directory – the directory two levels above this SKILL.md file. In a dev checkout of the source repo that's `plugin/`. `$plugin_python` is the plugin's isolated venv (created by the init flow at `$AGENTIC_ANALYTICS_DATA_DIR/venv`, default `~/.local/share/agentic-analytics/venv`); it falls back to `python3` if the venv doesn't exist yet.1. **Announce.** Output verbatim: > Clearing local agentic-analytics configs. Events cache stays put.2. **Run the script.** It prints what was cleared (or `(nothing to clear)` if everything was already gone): ```bash "$plugin_python" "$plugin_root/scripts/clear_configs.py" ```

Frequently asked questions