AGENT SKILL

suggest-follow-ups

Suggest high-leverage incident follow-up actions from established root cause and incident context. Activate when asked for follow-ups, action items, preventive measures, or "what should we do so this doesn't happen again" after an incident.

License 许可
Apache-2.0
所属仓库
vercel/eve
最近更新
2026-11-15
Stars
★ 5.9k
Forks
656

01 前言 Front Matter

name
suggest-follow-ups
description
Suggest high-leverage incident follow-up actions from established root cause and incident context. Activate when asked for follow-ups, action items, preventive measures, or "what should we do so this doesn't happen again" after an incident.

03 SKILL.md 正文

Suggest Follow-ups

Turn an incident's root cause, timeline, and blast radius into a short, ranked list of high-leverage follow-up actions. Suggest only; do not file follow-ups.

Prefer an established root cause. If root cause is unknown, do not investigate to invent one. Suggest only what available context supports, state that prevention-level follow-ups are premature, and recommend deep-investigation first if deeper follow-ups are wanted.

Procedure

Step 1: Gather what went wrong

From the incident channel and supporting evidence, identify:

  • Root cause — the underlying fragility, not just the trigger
  • Timeline — detection, diagnosis, and mitigation speed
  • Blast radius — services, endpoints, or users affected, and severity
  • Issues that made the timeline slow or blast radius large

If these facts are not already in the thread, read the incident thread with Slack tools. Do not run new Datadog or GitHub queries to expand the investigation.

Step 2: Load existing follow-ups

Scan the thread for follow-ups that people already named. Do not duplicate those items. If this is a repeat incident, raise priority and note that earlier mitigation did not hold.

Step 3: Map to categories

Weight toward where this incident actually hurt:

  • Prevent — eliminate the cause or class of cause
  • Detect faster (MTTD) — close a genuine detection gap
  • Mitigate faster (MTTR) — rollback automation, kill switch, missing runbook, missing dashboard
  • Limit blast radius — rate limiting, load shedding, circuit breaker, isolation, graceful degradation

If detection was already fast but recovery was slow, prefer mitigation over more alerts.

Step 4: Apply a high bar

A follow-up qualifies only if it is durable/systemic, targets the failure class, is worth the cost, and is verifiable. Drop process-vigilance items ("be careful", "add review", "remind").

A proposed alert must also be symptom-based, actionable, page-worthy only if urgent, threshold-tuned, and prefer fixing/consolidating an existing monitor over adding a new one.

Step 5: Rank

Order survivors by leverage — cheap, high-impact, fast-to-land first. Typically one to three items. If nothing clears the bar, say so rather than inventing low-value items.

Result

A short ranked list of suggested follow-ups, each with priority, action, and one sentence on why it matters tied to evidence.

Boundaries

  • Suggest only. Do not file follow-ups in an external system.
  • Do not investigate or run new observability/code queries to manufacture a root cause.
  • Do not assign owners.

04 同仓库更多 Skills

vercel
vercel/eve

writing-quality

The review rubric: writing-quality rules and reference lists for judging a content draft, covering AI-sounding phrasing, bloated wording, structure, and web-content specs. Load at the start of every review.

★ 5.9k
vercel
vercel/eve

writing-quality

Writing-quality guardrails for any prose the agent drafts or edits: blog posts, page copy, Notion drafts, release notes, marketing text. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or structural CMS work.

★ 5.9k
vercel
vercel/eve

seo-aeo-best-practices

SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces. Use this skill when implementing page SEO, technical SEO, schema markup, international SEO, AI-overview readiness, or improving content for Google, ChatGPT, Perplexity, and similar assistants.

★ 5.9k
vercel
vercel/eve

sanity-best-practices

Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this skill whenever working with Sanity schemas, defineType or defineField, GROQ or defineQuery, content modeling, Presentation or preview setups, Sanity-powered frontend integrations, Sanity Functions, documentEventHandler, defineDocumentFunction, defineMediaLibraryAssetFunction, @sanity/functions, @sanity/blueprints, sanity.blueprint.ts, event-driven content automation, or when reviewing and fixing a Sanity codebase.

★ 5.9k
vercel
vercel/eve

portable-text-serialization

Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.

★ 5.9k
vercel
vercel/eve

portable-text-conversion

Convert HTML and Markdown content into Portable Text blocks for Sanity. Use when migrating content from legacy CMSs, importing HTML or Markdown into Sanity, building content pipelines that ingest external content, converting rich text between formats, or programmatically creating Portable Text documents. Covers @portabletext/markdown (markdownToPortableText), @portabletext/block-tools (htmlToBlocks), custom deserializers, and the Portable Text specification for manual block construction.

★ 5.9k