agentleFS
Sign inStart free
ntaffziintaffzii/Skill-Agents/skills/productivity/markdown-report/SKILL.md

markdown-report

Skill4 starsChanged 2 months agoMITView on GitHub

Create clean Markdown reports, summaries, research briefs, project notes, RCA writeups, meeting summaries, decision records, and handoff documents. Use when the user asks to write, format, summarize, document, report, brief, or create a Markdown deliverable.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

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:

    Create useful Markdown documents with clear structure and practical detail.

    line 8
  2. Distinctive:

    Use only the headings needed for the job.

    line 16
  3. Distinctive:

    Prefer concise sections over heavy templates.

    line 17
  4. Distinctive:

    Put the answer near the top.

    line 20
  5. Distinctive:

    Use clear headings and short paragraphs.

    line 21
  6. Distinctive:

    Use tables only when they improve comparison or scanning.

    line 22
  7. Distinctive:

    Do not over-format simple content.

    line 72
  8. Distinctive:

    Do not bury the useful answer below background.

    line 73
  9. Distinctive:

    Do not include unsupported claims.

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Markdown Report

Create useful Markdown documents with clear structure and practical detail.

Workflow

  1. Identify audience and purpose
    • Decide whether the report is for personal tracking, engineering, leadership, research archive, automation output, or public sharing.
  2. Choose the lightest structure
    • Use only the headings needed for the job.
    • Prefer concise sections over heavy templates.
  3. Write
    • Put the answer near the top.
    • Use clear headings and short paragraphs.
    • Use tables only when they improve comparison or scanning.
    • Make action items explicit.
  4. Verify
    • Confirm the title matches the purpose.
    • Confirm claims are sourced, grounded in files, or clearly labeled as assumptions.
    • Confirm action items are concrete.
    • Confirm Markdown renders cleanly.

Common Templates

Research Brief

# [Title]

## Summary

## Key Findings

## Evidence

## Recommendations

## Action Items

## Sources

Decision Record

# Decision: [Title]

## Context

## Options Considered

## Decision

## Rationale

## Risks

## Follow-ups

Rules

  • Respond in the user's language.
  • Do not over-format simple content.
  • Do not bury the useful answer below background.
  • Do not include unsupported claims.

Download now (ZIP)

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.

Check your setup, free