使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill web-analytics開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Web Analytics Intelligence
Overview
Turn portfolio analytics into a decision-ready report by collecting a bounded dataset, preserving the comparison window, separating observed facts from hypotheses, and routing deeper requests through specialist agents. This is a push-based analysis workflow, not a dashboard replacement.
Read the operating contract before making authenticated requests or delivering a report.
Prerequisites
- Configure sites and thresholds in
${CLAUDE_PLUGIN_ROOT}/references/site-registry.md. - Store Umami credentials in the operator's approved secret store; this installation uses
UMAMI_PASSWORD from ~/.env.
- Confirm
/emailor/slackindependently before requesting those delivery channels. - Use
${CLAUDE_PLUGIN_ROOT}/references/reporting-tiers.mdand
${CLAUDE_PLUGIN_ROOT}/references/interpretation-guide.md for medium and full reports.
Authentication and Safety
- Confirm the analytics base URL is the expected operator-controlled host before sending a
credential.
- Load
UMAMI_PASSWORDonly for the command that needs it. Never print, log, persist, or pass
the password or bearer token to a specialist agent.
- Use
curl --fail-with-body --silent --show-error; stop if authentication fails or the token
is empty.
- Treat email and Slack delivery as external side effects. Preview the destination and report,
and obtain confirmation when the user has not explicitly requested delivery.
- Never send messages, modify analytics configuration, or write baseline state during a read-only
request. A full-tier memory update requires an explicit writable scope.
Workflow
1. Parse the Request
| Parameter | Default | Accepted values |
|---|---|---|
| Tier | mini | mini, medium, full |
| Site | all | Registry name or all |
| Period | 7d | today, yesterday, 7d, 30d, mtd, qtd |
| Delivery | console | console, email, slack, all |
| Compare | prior equivalent | An explicit comparison window |
Use defaults when they preserve the user's intent. Ask before continuing if the site, time window, or external destination would materially change the result.
2. Load Configuration
Read only the files needed for the selected tier:
${CLAUDE_PLUGIN_ROOT}/references/site-registry.mdfor site IDs, baselines, and thresholds.${CLAUDE_PLUGIN_ROOT}/references/mcp-tool-reference.mdfor supported data operations.${CLAUDE_PLUGIN_ROOT}/references/reporting-tiers.mdfor output contracts.${CLAUDE_PLUGIN_ROOT}/references/interpretation-guide.mdfor evidence language.
3. Collect the Minimum Dataset
For direct Umami access, authenticate and fail closed:
set -euo pipefail
source ~/.env
analytics_url="https://analytics.intentsolutions.io"
token=$(curl --fail-with-body --silent --show-error "${analytics_url}/api/auth/login" \
-X POST -H "Content-Type: application/json" \
-d '{"username":"admin","password":"'"${UMAMI_PASSWORD}"'"}' | \
python3 -c "import json,sys; print(json.load(sys.stdin).get('token',''))")
test -n "${token}" || { printf 'Umami authentication returned no token\n' >&2; exit 1; }
curl --fail-with-body --silent --show-error \
"${analytics_url}/api/websites/<site-id>/stats?startAt=<start-ms>&endAt=<end-ms>&compare=prev" \
-H "Authorization: Bearer ${token}"
unset token UMAMI_PASSWORDRecord the source, site, timezone, exact start and end timestamps, comparison window, and any missing endpoint. Do not infer missing values as zero.
4. Route by Tier
- Mini: Collect aggregate stats and active visitors inline. Return totals, per-site metrics,
comparison deltas, and one material signal in at most 15 lines.
- Medium: Use
Agentto rundata-collector; after it returns, runtraffic-intelligence,
content-seo, and anomaly-detector concurrently. Give reporting-narrative their outputs, the exact period, and the requested delivery format.
- Full: Run
data-collectorfor aggregate, event, technology, and geography data. Then run all
five analysis specialists concurrently, pass their claims to verification-agent, and compile only verified or explicitly qualified findings with reporting-narrative.
Agent definitions live under ${CLAUDE_PLUGIN_ROOT}/agents/. Give agents collected results, not credentials. Bound every assignment to the requested sites and period. If an agent fails, report that coverage gap and continue only when the remaining evidence can support the requested output.
5. Verify and Deliver
Before delivery, apply the operating contract:
- Recalculate headline deltas from the raw totals.
- Label each statement as observation, comparison, hypothesis, or recommendation.
- Check anomaly claims against baselines and low-volume noise.
- Name unavailable sources and incomplete windows.
- Preview external destinations, then invoke
/emailor/slackonly when authorized.
For a full-tier report, run memory-agent only if the user authorized baseline-state updates. Persist the period, source, and evidence receipt so a later report can reproduce the comparison.
Error Handling
Stop without exposing secret material when authentication fails. For partial endpoint, site, agent, or delivery failures, retain successful evidence, name the exact coverage gap, and avoid complete- portfolio or trend claims that the remaining data cannot support. The operating contract defines the required fallback for each failure class.
Output
Return the tier, sites, exact period, comparison window, sources consulted, coverage gaps, and delivery result. Lead with the strongest verified signal, show the supporting metrics, distinguish hypotheses from facts, and end with prioritized actions that each have an owner or next check.
Examples
/analytics --period=todayproduces a mini console pulse for every configured site./analytics medium --site=tonsofskills --period=7dexplains material traffic and content shifts./analytics full --period=30d --emailpreviews an evidence-checked deep dive before email delivery.
Resources
- Operating contract — auth, evidence, failure, and delivery gates.
${CLAUDE_PLUGIN_ROOT}/references/site-registry.md— configured properties and thresholds.${CLAUDE_PLUGIN_ROOT}/references/reporting-tiers.md— detailed report schemas.${CLAUDE_PLUGIN_ROOT}/references/interpretation-guide.md— analytical voice and caveats.${CLAUDE_PLUGIN_ROOT}/references/delivery-channels.md— email and Slack adapters.