A template for writing technical reports, architecture decision records, and shorter briefs. An architecture decision record documents an important technical choice, its context, and its consequences.

Use it to create full technical reports, decision records, or concise technical summaries.

It gives technical work a consistent structure for explaining goals, research, options, decisions, implementation, and results. This makes design discussions and decisions easier to review.

report — Skill for Claude Code by lisihao

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add lisihao/Solar --skill report

Clone the repo

git clone --depth 1 https://github.com/lisihao/Solar

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/lisihao/solar/report/github.svg)](https://agentmods.dev/skills/lisihao/solar/report)

Your own site

<a href="https://agentmods.dev/skills/lisihao/solar/report"><img src="https://agentmods.dev/badge/skills/lisihao/solar/report/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/lisihao/solar/report"><img src="https://agentmods.dev/badge/skills/lisihao/solar/report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,620 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00014	$0.01620
Opus 5	$0.00007	$0.00810
Sonnet 5	$0.00003	$0.00324
Haiku 4.5	$0.00001	$0.00162

Measured 7d ago against content hash d2ffd313f168, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

report scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/report/SKILL.md · 289 lines

How it starts

The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/report - 技术报告模板

基于 ADR、MADR 和业界最佳实践。

使用

/report full   完整技术报告
/report adr    架构决策记录 (ADR)
/report brief  精简报告

1. 完整技术报告模板 (`/report full`)

# [项目名称] 技术报告

> 版本: x.x.x | 日期: YYYY-MM-DD | 状态: Draft/Review/Final

---

## Executive Summary

[150-300字概述：目的、方法、关键发现、结论]

---

## 一、背景与愿景

### 1.1 问题陈述
- **业务痛点**: [具体问题描述]
- **技术挑战**: [技术限制/瓶颈]
- **市场机会**: [为什么现在做]

### 1.2 目标与成功标准
| 目标 | 指标 | 基线 | 目标值 |
|------|------|------|--------|
| 性能提升 | 延迟 | 100ms | <50ms |
| ... | ... | ... | ... |

### 1.3 范围与约束
- **In Scope**: ...
- **Out of Scope**: ...
- **约束条件**: 时间/预算/技术栈

---

## 二、技术分析

### 2.1 技术趋势
| 趋势 | 影响 | 机会 |
|------|------|------|
| ... | ... | ... |

### 2.2 业界 SOTA (State of the Art)
| 方案 | 性能 | 优势 | 劣势 |
|------|------|------|------|
| 方案A | ... | ... | ... |
| 方案B | ... | ... | ... |

### 2.3 竞品分析
[关键竞品的技术方案对比]

---

## 三、技术决策 (ADR 格式)

### ADR-001: [决策标题]

**Status**: Accepted | Proposed | Deprecated | Superseded

**Context**:
[决策背景和面临的问题]

**Decision**:
[做出的决策]

**Consequences**:
- ✅ 好处: ...
- ⚠️ 代价: ...
- 📋 后续: ...

### ADR-002: ...

---

## 四、实现历程

### 4.1 技术选型与验证

| 候选 | 测试结果 | 结论 |
|------|----------|------|
| 方案A | 延迟 80ms | ❌ 不满足 |
| 方案B | 延迟 45ms | ✅ 采用 |

### 4.2 关键突破

#### 挑战 1: [问题描述]
- **尝试**: [失败的方案]
- **突破**: [成功的方案]
- **洞见**: [学到了什么]

### 4.3 核心实现

[关键代码/架构图/流程图]


---

## 五、效果评估

### 5.1 性能结果
| 指标 | 基线 | 目标 | 实际 | 状态 |
|------|------|------|------|------|
| 延迟 | 100ms | <50ms | 35ms | ✅ |
| 吞吐 | 1K/s | >5K/s | 8K/s | ✅ |

### 5.2 vs SOTA 对比
| 维度 | SOTA | 我们 | 差异 |
|------|------|------|------|
| ... | ... | ... | +X% |

### 5.3 业务价值
[具体的业务收益/用户价值]

---

## 六、经验与教训

### 6.1 做对了什么
1. ...
2. ...

### 6.2 可以改进的
1. ...
2. ...

### 6.3 踩过的坑
| 坑 | 原因 | 解决 |
|-----|------|------|
| ... | ... | ... |

---

## 七、后续规划

### 短期 (1-3个月)
- [ ] ...

### 中期 (3-6个月)
- [ ] ...

### 长期
- [ ] ...

---

## 附录

- A. 术语表
- B. 参考资料
- C. 变更历史

2. ADR 模板 (`/report adr`)

Read the full file on GitHub · 289 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

7d ago First seen · 289 lines · 14 tokens per session scan A d2ffd313f168

Subscribe to this mod's changes

report is a skill published in the GitHub repository lisihao/Solar (2 stars, last pushed 28d ago), licensed MIT. It adds 14 tokens to every session and 1,620 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Planning Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens