agentleFS
genspark-aigenspark-ai/genoffice/skills/recommended/business-report/SKILL.md

business-report

Skill11k starsChanged 3 months agoApache-2.0View on GitHub

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.

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read every attached or referenced file in full before drafting.

    line 20
  2. Distinctive:

    Write the one-sentence conclusion first.

    line 23
  3. Distinctive:

    Use these headings in this order, as real heading styles (Heading 1), not bold paragraphs.

    line 28
  4. Distinctive:

    Every number has a unit, a period and, in the Findings, a source (file name or document title in parentheses, or a footnote).

    line 54
  5. Distinctive:

    No hedging stacks ("it may perhaps be possible").

    line 56
  6. Distinctive:

    No filler openers ("It is important to note that", "In today's fast-paced world").

    line 58
  7. Distinctive:

    Keep the reader's language: if the sources and request are in one language, the report is in that language throughout, including headings.

    line 60
  8. Distinctive:

    No decorative elements, colors or images unless the user asks.

    line 72
  9. Distinctive:

    Every figure in the summary appears again in Findings with its source.

    line 78

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about genspark-ai/genoffice

The biggest 5 of 66 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 66

Talked about on GitHub, YouTube, Bluesky, the web and Hacker News (66 times).

On GitHub · 31

26 more on GitHub

On YouTube · 23

18 more on YouTube

On Bluesky · 5

On the web · 4

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.