Desktop report
Report and proposal writing — work summaries, analysis reports, feasibility studies, project proposals with structured templates.
install
source · Clone the upstream repo
git clone https://github.com/openyak/openyak
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openyak/openyak "$T" && mkdir -p ~/.claude/skills && cp -r "$T/backend/app/data/skills/report" ~/.claude/skills/openyak-desktop-report && rm -rf "$T"
manifest:
backend/app/data/skills/report/SKILL.mdsource content
Report and Proposal Writing
When the user asks you to write a report, proposal, or summary, follow this workflow:
1. Identify the report type
| Type | Typical use | Key elements |
|---|---|---|
| Work summary | Weekly/monthly/annual review | Accomplishments + metrics + next steps |
| Analysis report | Market/competitor/data analysis | Current state + analysis + conclusions + recommendations |
| Feasibility study | New project/initiative | Background + options + cost-benefit + risks |
| Project proposal | Pitch/bid | Objectives + approach + timeline + budget |
| Briefing | Meeting presentation | Key points + data support + clear conclusions |
2. Standard report structure
Universal framework
- Title page: Report name, date, author/department
- Executive summary: 1-3 paragraphs capturing the core conclusions (readers should get the gist from this alone)
- Background and purpose: Why this report exists, what problem it addresses
- Main body (varies by type): Data, analysis, comparisons, arguments
- Conclusions and recommendations: Clear takeaways + actionable next steps
- Appendix (optional): Detailed data tables, references
3. Writing principles
- Lead with conclusions: Put the most important finding first (pyramid principle)
- Use data, not adjectives: "Revenue grew 35%" instead of "revenue grew significantly"
- Clear structure: Use numbered headings, tables, and bullet points
- Reader-aware: Adjust depth and technicality based on the audience
- Actionable recommendations: Be specific — who does what, by when
4. Formatting
- Use Markdown format
- Present key data in tables
- Bold critical conclusions
- Prefer numbered lists over unordered lists
- Keep paragraphs short (3-5 sentences)
5. Quality checklist
- Can the executive summary stand alone?
- Are all numbers consistent throughout?
- Are recommendations specific and actionable?
- Is the length appropriate (not too long, nothing missing)?