Markdown report

Skill ntaffzii/Skill-Agents/skills/productivity/markdown-report

Personal AI-agent skills, workflows, prompts, and setup guides for local LLMs and MCP-powered assistants.

Install

npx -y skills add ntaffzii/Skill-Agents --skill markdown-report

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

4 stars4 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 author says it does

Copied from the file, not written here

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.

SKILL.md

1.6 KB, as published. Nobody here has run it

Markdown Report

Create useful Markdown documents with clear structure and practical detail.

Workflow

Identify audience and purpose
- Decide whether the report is for personal tracking, engineering, leadership, research archive, automation output, or public sharing.
Choose the lightest structure
- Use only the headings needed for the job.
- Prefer concise sections over heavy templates.
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.
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.