agentsclimarketplace
Sign in

Report writer

Skill 264Gaurav/DeepAgents/deepagents/skills/report-writer

Report writing skill that should be applied AFTER answering any user query. Whenever the deep agent produces a final answer, use this skill to also write a structured markdown report of the interaction (question, approach, findings, answer, sources) and save it as a file using the write_file tool. Use for every substantive answer, and especially when the user asks for a report, summary document, or saved output.From its SKILL.md

Install
npx -y skills add 264Gaurav/DeepAgents --skill report-writer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.0 KB, 347 tokens by cl100k_base, as published. Nobody here has run it

Report Writer Skill

This is a post-answer skill: after you finish answering ANY substantive user query, generate a structured report of what was asked, what you did, and what you concluded — and save it to a file with the write_file tool.

When to Use

  • ALWAYS after producing a final answer to a substantive question
  • When the user explicitly asks for a report, summary document, or saved output
  • After research tasks, code generation tasks, or multi-step workflows
  • Skip only for trivial exchanges (greetings, clarifying questions)

Supporting Files (read these for deeper context)

  • instructions.md — the exact report template, file-naming rules, and writing standards
  • examples.md — sample reports showing the expected quality and structure

Core Workflow

  1. Answer the user's question first, as normal (possibly using other skills).
  2. Read instructions.md in this skill folder for the report template.
  3. Fill in the template: title, date, question, approach, key findings, answer, sources.
  4. Save the report with write_file to /reports/<topic-slug>-report.md.
  5. Tell the user the report was saved and where.

Quick Standards

  • Reports are markdown files saved under /reports/
  • File name: kebab-case topic slug + -report.md (e.g., /reports/lambda-cost-report.md)
  • Always include: Question, Approach, Key Findings, Answer, Sources/Tools Used
  • Keep the report self-contained — readable without the chat transcript
  • Be factual; do not add claims to the report that were not in your answer

What ships with it: 2 files

6.1 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,835. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.