Skip to content
cccskills
FreePublished on GitHub

business-report

Turn notes, data, and source documents into a structured Word business report. An executive summary, evidence-based findings, actionable recommendations, and open questions give readers a clear conclusion, with consistent wording and sources for the figures.

OriginalShow the original description

Write a business report in Word with a fixed structure (executive summary, background, analysis, recommendations, appendix), sourced numbers and a consistent voice. Use when the user asks for a report, memo, review, assessment or analysis document, or to turn notes or data into one.

Run score Not tested

See how to install

Good for

  • Turning notes and data into a business report
  • Writing an assessment to support a decision
  • Preparing a sourced report for a client
  • Connecting findings to recommended actions

Files included (1)

  • SKILL.md3.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Business report

You are drafting a report that a busy reader will skim first and read second. Structure carries the argument; prose fills it in.

Before writing

  1. Pin down four things from the request and the attached files. Ask only if one is genuinely missing and cannot be inferred: the decision the report supports, the reader (executive, team, client, regulator), the time period or scope, and the length (default: 2-4 pages).
  2. Read every attached or referenced file in full before drafting. Numbers, names and dates come from those sources, never from memory. If a source is silent, say so in the report rather than inventing a figure.
  3. Write the one-sentence conclusion first. If you cannot state it in one sentence, you are not ready to write.

Structure

Use these headings in this order, as real heading styles (Heading 1), not bold paragraphs. Drop a section only when the request rules it out.

  1. Executive summary — 3-6 sentences. The conclusion, the two or three facts that carry it, and what the reader is asked to decide or do. No background, no methodology.
  2. Background — Why the question exists now. Scope and period. What was examined and what was left out, in one short paragraph each.
  3. Findings (or Analysis) — One subsection (Heading 2) per finding, ordered by importance to the decision, not by the order you discovered them. Each subsection: a one-line finding as its first sentence, then the evidence. Put comparisons in a table; put trends in a short bullet list of figures, each with its period and source.
  4. Recommendations — Numbered. Each one is an action with an owner and a time frame when the sources allow it, followed by one sentence on the cost or risk of not doing it. Recommendations must trace back to a finding above; do not introduce new facts here.
  5. Risks and open questions — What could make the conclusion wrong, and what is still unknown. Short bullets.
  6. Appendix — Source list, data tables too large for the body, definitions. Only when there is something to put here.

Voice

  • Plain, declarative sentences. One idea per sentence. Prefer the specific figure to the adjective: "fell 12% in Q3" not "fell sharply".
  • Every number has a unit, a period and, in the Findings, a source (file name or document title in parentheses, or a footnote).
  • No hedging stacks ("it may perhaps be possible"). State the confidence once, where it matters.
  • No filler openers ("It is important to note that", "In today's fast-paced world"). Start with the point.
  • Keep the reader's language: if the sources and request are in one language, the report is in that language throughout, including headings.

Formatting in the document

  • Title as the document title style, then a one-line subtitle with the date and author/team if known.
  • Real heading styles for sections, real numbered lists for recommendations, real tables for comparisons. Never fake structure with tabs, manual numbers or bold-only lines.
  • Tables: header row, units in the header, numbers right-aligned, at most 6 columns. Add a one-line caption above each table.
  • No decorative elements, colors or images unless the user asks.

Before you say done

  • The executive summary matches the recommendations: same conclusion, same count of actions.
  • Every figure in the summary appears again in Findings with its source.
  • Headings are heading styles; lists are list styles.
  • Re-read the first and last paragraphs: they should make sense alone.
  • Tell the user the structure you used and anything you could not source.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

brand-copy

FreeSummary

Use product facts and audience information to create ten tagline options, benefit statements backed by evidence, and brand stories for websites and social media. Compare alternatives in a Markdown document with recommendations and tone guidance.

  • Compare tagline options for a product
  • Rewrite product features as customer benefits
  • Create brand stories for a website and social media
genspark-ai/genoffice10.7KUpdated Oct 24, 2026

budget-planner

FreeSummary

Turn a business plan or project spending details into an Excel budget workbook. Organize monthly costs, account and quarterly summaries, confirmed assumptions, and a change log, with formulas that update calculations when assumptions change.

  • Build an annual department budget from a business plan
  • Organize project spending into a monthly budget
  • Compare budget totals with previous-year results
genspark-ai/genoffice10.7KUpdated Oct 24, 2026

business-plan

FreeSummary

Turn a project idea or unfinished draft into a Word business plan for fundraising or internal approval, covering customers, market size, competitors, revenue model, team, and three-year financial projections with clearly stated assumptions.

  • Prepare a business plan for fundraising
  • Develop a proposal for internal project approval
  • Complete financial projections and competitor analysis
genspark-ai/genoffice10.7KUpdated Oct 24, 2026

campaign-planner

FreeSummary

Turn campaign goals, audience details, timing, and budget into a Word plan for review. Develop theme options, schedules, promotion channels, materials, cost breakdowns, measurable targets, contingency plans, and a template for reviewing results.

  • Plan a product launch event
  • Design a seasonal sales promotion within a budget
  • Map participation and conversion steps for an online campaign
genspark-ai/genoffice10.7KUpdated Oct 24, 2026

contract-drafter

FreeSummary

Prepare a reference contract draft in Word from the parties, scope, payment terms, and other agreement details. Include a pre-signing checklist explaining unfavorable clauses and unresolved negotiation points, with a reminder to obtain licensed legal review.

  • Drafting a services outsourcing contract
  • Identifying risks in an agreement before signing
  • Listing unresolved contract negotiation points
genspark-ai/genoffice10.7KUpdated Oct 24, 2026

course-slides

FreeSummary

Turn a handout or lesson plan into a PowerPoint teaching deck after reviewing its outline. Slides present concise learning points, while speaker notes provide explanations, transitions, timing, and guidance for questions or exercises when included.

  • Turning a lesson plan into classroom slides
  • Building training slides from a handout
  • Preparing a teaching script with timing
genspark-ai/genoffice10.7KUpdated Oct 24, 2026

See all skills by genspark-ai

Report a problem with this skill