菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Automattic/agentic-analytics --skill clear-configs命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Walk the user through first-time setup of the agentic-analytics plugin. Use when the user asks how to get started, how to set up the plugin, where to put their credentials, what the plugin can do for them, or any variant of "first run" / "onboarding" / "walk me through this."
Run the Journey Report — how far into the site a visit gets and where it ends. Use when the user asks to run the journey report, asks how deep visitors go, where the site loses people, what route visitors take after landing, which pages or sections have the worst loss or exit rate, engagement depth, or how a section of the site performs. Also use for follow-up questions about visit paths, entry points, campaigns or engaged time once a report has been run.
Run the staircase audience-relationship report for a customer. Use when the user asks to run the staircase report, requests it for a specific site, or asks for an audience-tier or relationship-intelligence report.
基于 SOC 职业分类
正在显示 SKILL.md
| name | clear-configs |
| description | 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. |
Removes two things to put the user back at first-run state:
${XDG_CONFIG_HOME:-~/.config}/agentic-analytics/bucket.json – runtime config init writes.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).
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.
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"