// How to scope, draft, and revise a Markdown report artifact via generate_report
Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Draft an email matching the user's voice, with structured intent and CTA
Structured approach to finding and synthesizing information from the user's knowledge base
Pull together briefing materials before a scheduled meeting
Distill a Slack channel or thread into actionable summary
| name | report-writing |
| description | How to scope, draft, and revise a Markdown report artifact via generate_report |
| allowed-tools | generate_report, search_surfsense_docs, read_file |
The user explicitly requests a deliverable: "write a report on …", "draft a memo", "produce a brief", "expand the previous report". A creation or modification verb pointed at an artifact is required (see generate_report's when-to-call rules).
source_strategy fits:
conversation — substantive Q&A on the topic already in chat.kb_search — fresh topic; supply 1–5 precise search_queries.auto — partial conversation context; let the tool fall back.provided — verbatim source text only.report_style="detailed" unless the user explicitly asks for "brief", "one page", "500 words".parent_report_id and put the change list in user_instructions ("add carbon-capture section", "tighten conclusion").generate_report returns — confirm and let the artifact card render itself.If kb_search/auto returns no results, do not silently switch to general knowledge. Surface the gap in your confirmation message.