Experiment Report Skill
Create a complete experiment report workflow with frontend visualization and structured markdown report. Supports any experiment type — implementation, interactive frontend, screenshots, and md/docx delivery. Use for 实验报告、experiment report and experiment-related 前端展示 or 可视化报告, with visual confirmation before the final report.
Install
npx skills add lyzbcy/experiment-report-skill --skill experiment-report-skillgit clone --depth 1 https://github.com/lyzbcy/experiment-report-skill.git /tmp/experiment-report-skill
mkdir -p ~/.claude/skills
cp -r /tmp/experiment-report-skill/. ~/.claude/skills/experiment-report-skillPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 实验报告工作流 Skill 一个通用的实验报告生成工作流。你只需要描述实验内容,它帮你完成:实验实现 → 前端可视化 → 截图 → 多轮自检修复 → 实验报告。 ## 何时使用 - 用户要做任何实验报告(强化学习、机器学习、算法对比、数据分析等)。 - 用户要一个能直观展示实验结果的前端页面,而不是只有终端输出。 - 用户要求数据真实、不能编造、要能截图进实验报告。 - 用户明确要求先确认效果,再开始写实验报告。 - 用户希望实验报告贴近 docx 结构,后续还要转 Word、插图、统一标题样式和目录。 ## 工作原则 - 先做计划,再动手实现。 - 先保证实验数据真实,再谈展示和排版。 - 任何图表、数据都必须来自实际运行结果,不许用"看起来合理"的替代品。 - 前端必须先做出来,而且要先给用户确认,再进入最终报告写作。 - 前端优先服务于展示结果,样式要清晰、美观、可截图,截图要能直接放进实验报告。 - 最终报告中的图片优先来自前端实际渲染结果,不允许手工拼图或伪造图表。 - 公式一律优先使用正式公式格式书写(Markdown/KaTeX),不要手工截成图片。 - 用户未确认前端效果前,不要直接写最终版实验报告。 - 始终执行完整报告流程,不由 AI 自动选择简化交付;前端、截图、md/docx 双交付和自检均须完成。 - 报告要写得足够详尽,不能只像任务摘要,要体现出完整实验思路、结果、分析和反思。 - 实验报告中至少要有 4 张真实截图,而且截图要能看出页面确实经过认真排版。 - 最后一章心得感悟要先压掉模板腔、总结腔和 AI 味,再放进报告。 - **交付前必须完成至少 3 轮自检修复循环,直到问题基本清零。**(见"多轮自检修复流程"章节) ## 推荐执行顺序 ### 1. 先做计划 先输出简短计划,明确下面几件事: - **实验内容**:用户要做什么实验?(算法对比、数据分析、系统测试等) - **环境/数据设定**:输入数据、参数空间、评价指标等。 - **算法/方法范围**:需要跑哪些方法,对比什么。 - **交付物**:前端展示页面、实验报告.md、截图等。 - **验收点**:怎样算实验完成。 ### 2. 先实现真实实验 先把实验跑通,再做展示。 - 明确实验环境、输入输出、评价指标。 - 记录原始训练结果,不要只保存一张漂亮图。 - 输出可复查的数据文件。 - 如果需要多次实验,保留每次运行的原始结果,便于后面对比。 ### 3. 再做前端展示 优先做一个能直观看懂的页面,帮助后面截图,这是写最终报告前的必做步骤。 - 页面要清楚展示实验的核心结果(策略图、对比图、曲线图等)。 - 如果有多个实验结果版本,页面要标清楚参数和运行条件。 - 页面完成后先让用户确认,确认通过后再从前端里截图整理进报告。 - 截图优先保留完整页面和关键区域,避免只截局部。 - **前端样式必须遵循"去 AI 味设计规范"**(见下方专门章节)。 ### 4. 截图与报告 用户确认前端效果后,再从前端里截图并写实验报告.md。 - 报告里的图表必须来自前端实际渲染结果。 - 截图时尽量保证字体清晰、布局完整、比例统一。 - 至少保留 4 张真实截图。 - 截图不要只截一小块,尽量保留标题、统计信息、图例和上下文。 - 每张截图都要自检:无白边、无截断、无错位、无滚动条。 - **按截图清单方法论执行**(见下方专门章节)。 - 写报告时尽量靠近 docx 结构:标题层级清楚、图注完整、每张关键图对应一段分析。
Details
- Skill name
experiment-report-skill- Repository
- lyzbcy/experiment-report-skill
- License
- MIT
- Repo updated
- 28 October 2026
FAQ
What does the Experiment Report Skill skill do?
Create a complete experiment report workflow with frontend visualization and structured markdown report. Supports any experiment type — implementation, interactive frontend, screenshots, and md/docx delivery. Use for 实验报告、experiment report and experiment-related 前端展示 or 可视化报告, with visual confirmation before the final report.
How do I install the Experiment Report Skill skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add lyzbcy/experiment-report-skill --skill experiment-report-skill. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Experiment Report Skill popular?
It lives in lyzbcy/experiment-report-skill, which has 12 GitHub stars and 2 forks.
Related skills
Readydesign Skill
14ZethRise/ReadyDesign-Skill
Force UI work onto six ready-to-use libraries only: shadcn/ui, Ant Design, Kokonut UI, Motion (motion.dev), Bklit (bklit.com), and sashimi UI. Web-fetch each official site one-by-one and install the real components from those pages — never invent APIs, class names, colors, or components from memory. Use when building or restyling a UI, scaffolding a frontend, adding components, picking a design system, or when the user says ReadyDesign, ready-to-use components, shadcn, antd, kokonut, motion.dev, framer motion, bklit, sashimi, or runs /readydesign-skill or $readydesign-skill.
Filemaker Layout Xml
15andykear/FileMaker-XMLsnippet-Layout-Claude-Skill
Use this skill whenever the user wants to work with FileMaker layout XML. This includes generating paste-ready layout object XML (fmxmlsnippet type LayoutObjectList) from descriptions, reviewing layout XML for silent paste-handler failures, or analysing Save as XML layout exports. Trigger any time the user mentions FileMaker layouts, layout objects, fields, portals, tab controls, popovers, button bars, web viewers, anchoring or autosizing, or LayoutObjectList. Always perform the theme pre-flight before generating, and set object anchoring deliberately whenever an object must resize with the wi
Netops
12Con-Benksl/NetOps
Route authorized VPS networking and proxy work to onboarding, read-only scanning, building, repair, or fleet management. Use for VPS access, 3x-ui/Xray/VLESS Reality/Hysteria2, DNS/TUN/routing failures, node performance, or ongoing multi-VPS operations. 典型中文请求:VPS 连不上、节点慢或掉线、搭建或修改节点、面板打不开、多台 VPS 统一维护。
Design Tokens
15ilikescience/design-tokens-skill
Expert in design tokens using the DTCG specification. Use this skill when users ask about design tokens, DTCG format, token validation, formatting, transformation, color spaces (sRGB, Display P3, OKLCH), references and aliasing, resolvers, theming with modifiers/contexts, multi-platform design systems, accessibility, or working with tools like jq, jsonata, and terrazzo. Helps with token file creation, resolver configuration, structure, naming conventions, and best practices.
Ship Page
12Zooeyii/ship-page-skill
Create stunning, interactive landing pages for products, startups, and side projects — zero dependencies, single HTML file. Use this skill whenever the user wants to build a landing page, product page, launch page, marketing page, or any promotional web page for their app, tool, SaaS, open-source project, or personal brand. Also triggers when users say "I need a website for my product", "help me launch", "make a page for my app", or want to convert a README into a visual landing page. Works great for Product Hunt launches, GitHub project pages, and indie hacker ship days.
Design Feel Like Your Own Product
15Tiannanzhao/design-feel-like-your-own-product
Learn and replicate a designer's style from Figma files to create new components that feel authentic to their design system. Use this skill whenever a user shares a Figma file and wants to create new components, plugins, or UI elements that match an existing design style — even if they don't explicitly say "learn my style". Trigger when users mention Figma files, design systems, "make it look like my design", "match the style", or ask to extend an existing UI.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.