weekly-digest

Produce the Nuxt Monday digest — traffic, docs feedback, Nuxi quality, and prioritized follow-ups for a recent window.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/nuxt/nuxt.com/weekly-digest
Any agent
npx skills add nuxt/nuxt.com --skill weekly-digest
Clone the repo
git clone --depth 1 https://github.com/nuxt/nuxt.com

Made for: Claude Code, Codex.

Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,898 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00026 $0.01898
Opus 5 $0.00013 $0.00949
Sonnet 5 $0.00005 $0.00380
Haiku 4.5 $0.00003 $0.00190

Measured yesterday against content hash 57ae01fe1dc1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

weekly-digest scanned grade C with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Tells the agent never to refusehighAnti-refusal

Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.

**Slack delivery:** Your reply IS the Slack message — Eve posts it verbatim to this channel. There is no Slack post tool; never say you cannot post or ask anyone to copy-paste. You are Nuxi (:nuxi:) giving the team a wee
layers/nuxi/agent/skills/weekly-digest/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

When producing a digest (scheduled or on request):

Slack delivery: Your reply IS the Slack message — Eve posts it verbatim to this channel. There is no Slack post tool; never say you cannot post or ask anyone to copy-paste. You are Nuxi (:nuxi:) giving the team a weekly pulse. Be concise, linked, and actionable — not a wall of text.

Always write Slack mrkdwn (<url|label>, :emoji:). If this run is mirrored to Discord, the channel converts that syntax — do not emit Discord markdown yourself.

  • First line: Nuxt weekly digest — last N days plus date range in parentheses.
  • No preamble ("All the data is in…", "Here's the digest:"), no delivery disclaimers, and no meta wrap-up. Start with the title line.
  • Use bold section labels — never markdown # headings.
  • ONE message only. Blank line between sections.
  • Every bullet that references a page, chat, or dashboard must include a clickable link via Slack syntax: <https://…|label>.
  • Sparingly use :nuxter: or :nuxt_cool: (0–2 total) when something is worth celebrating or urgent.

Data steps (parallel where possible; Vercel / AI Gateway tools need admin/Slack/schedule-only access):

Traffic (nuxt.com project — always pass teamId/projectId):

  1. vercel-mcp__get_web_analyticsmode=count, dataset=visits for the current window AND the previous window → visitors/pageviews + WoW %.
  2. mode=aggregate, dataset=visits, by=['day'] current window → daily trend (spot spikes/drops).
  3. mode=aggregate, dataset=visits, by=['route'], limit=10 current + previous window → top sections with per-route deltas.
  4. mode=aggregate, dataset=visits, by=['referrerHostname'], limit=8 + by=['country'], limit=5 + by=['deviceType'] → audience snapshot.

Docs feedback: 5. admin-mcp__feedback-statstopPages=5 6. admin-mcp__list-feedbackratings=["not-helpful", "confusing"], limit=30 7. For each worst page from step 5/6: traffic from step 3, or a targeted mode=count, filter="requestPath eq '<path>'" if missing from top routes — weigh urgency by real visits.

AI agent: 8. admin-mcp__agent-usage-stats — web chat counts and vote quality 9. admin-mcp__list-agent-chatshasDownvotes=true, limit=5 10. admin-mcp__list-agent-votesonlyDownvotes=true, limit=15 11. vercel-mcp__list_agent_runs over the window → Slack / Discord / web run split (discover eve project via list_agent_run_projects first). 12. ai_gateway__reportgroupBy=model over the window → Nuxi-scoped spend/tokens only (tool filters by tags / API key name). Asking for a groupBy always forces tag scoping when an API key name is configured — check scope.mode, not scope.matchedRows: whenever scope.mode is "tags" and scope.note names an API key, that result only covers tagged traffic and can undercount the real historical total, even if scope.matchedRows is non-zero. Re-run with no groupBy for the full key-name-scoped total. If that ungrouped report is still unavailable or empty, present the tagged numbers but label them explicitly as partial (tagged traffic only) — never as the complete historical spend. If both come back empty, say spend is not attributable yet — never quote account-wide / other-product totals (no fable, no team-wide $). 13. ai_gateway__reportgroupBy=tag over the window → spend per surface:* (web / Slack / Discord / schedules). Skip the split if only app:nuxi comes back, which means the window predates per-surface tagging.

Link cheat sheet (use real paths/ids from tool output):

  • Docs page: <https://nuxt.com/docs/…|Page title>
  • Chat review: <https://nuxt.com/dashboard/chat/<id>|Open chat>
  • Analytics: <https://vercel.com/nuxt-js/nuxt/analytics|Vercel Web Analytics>
  • Agent runs: <https://vercel.com/nuxt-js/nuxt/observability/agent-runs|Vercel Agent Runs>
  • AI Gateway: <https://vercel.com/nuxt-js/nuxt/ai-gateway|Vercel AI Gateway>

Output template:

Nuxt weekly digest — last 7 days (Jun 23 – Jun 30, 2026)

Read the full file on GitHub · 89 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 89 lines · 26 tokens per session scan C 57ae01fe1dc1

Subscribe to this mod's changes

weekly-digest is a skill published in the GitHub repository nuxt/nuxt.com (456 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 1,898 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.

Related

Other skills, from other repositories

nuxt-ui

Build UIs with @nuxt/ui v4 — 125+ accessible Vue components with Tailwind CSS theming. Use when creating interfaces, customizing themes to match a brand, building forms, or composing layouts like dashboards, docs sites, and chat interfaces.

nuxt/ui · 56 tokens

nuxt-docs

Nuxt 4.x — full-stack Vue.js framework. File-based routing, auto-imports, SSR, Nitro, layers, modules.

pledgeandgrow/pledge-skills · 33 tokens

docs-writer

Creates and edits Dark Sky Conservation policy documentation for Maharashtra government officials and academics. Handles audience-appropriate tone, section-specific content rules (Research/Policy/Pilots), and orchestrates technical validation passes. Use when working on docs/content/ markdown files.

incubrain/foundry · 54 tokens

visual-tester

Perform UI/UX visual reviews and detect layout/styling bugs using annotated snapshots from agent-browser. Use when asked to "review the UI", "check for visual bugs", "screenshot this page", "compare layouts", or "test responsive design".

incubrain/foundry · 55 tokens

slidev

Create and present web-based slidedecks for developers using Slidev with Markdown, Vue components, code highlighting, animations, and interactive features. Use when building technical presentations, conference talks, code walkthroughs, teaching materials, or developer decks.

slidevjs/slidev · 51 tokens

openapi-glossary

Use consistent OpenAPI terminology and definitions when writing documentation, educational material, and tooling guidance.

scalar/scalar · 24 tokens