# Show Reproduced Repo > Create or refresh a single, minimal HTML showcase for a previously reproduced repository. Use when Codex needs to present verified reproduction results, images, videos, conclusions, current progress, blockers, and concrete next steps in one self-contained white-background, black-text HTML file for a demo, handoff, progress review, or report. - Skill: `songyw2003/show-reproduced-repo` (Agent Skill, multi-file: 5 files) - Install (CLI): `npx skillmds@latest add songyw2003/show-reproduced-repo` - Raw SKILL.md: https://api.skillmd.com/api/skills/songyw2003/show-reproduced-repo/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Web & Frontend - Author: songyw2003 (https://skillmd.com/u/songyw2003) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/songyw2003/show-reproduced-repo --- # Show Reproduced Repo Create an evidence-based project showcase that is easy to open, send, and review. Favor clarity and real artifacts over visual decoration. ## Output contract - Produce one `showcase.html` by default in the target repository root, unless the user chooses another path. - Embed local images and videos into the HTML so the deliverable remains a single file. - Use only a white background, black or gray text, thin borders, and native system fonts. - Do not add frameworks, external fonts, CDNs, gradients, animations, dashboards, decorative icons, or colored status badges. - Include only sections supported by useful evidence. Do not fill empty sections with boilerplate. - Keep repository claims, locally verified results, and inferences clearly distinguishable. - Write the title, subtitle, conclusions, progress, captions, issues, notes, and next steps in concise Chinese by default. Use another language only when the user explicitly requests it. Keep commands, paths, identifiers, proper names, and exact error text unchanged when translation would reduce precision. ## Workflow ### 1. Establish the scope Treat the current working directory as the target repository unless the user names another repository. Treat `showcase.html` in its root as the output unless another path is requested. Use the current conversation, prior reports, and available project memory as leads when the user says "之前复现的项目", but recheck live files before publishing any claim. Set `lang` to `zh-CN` and keep all narrative fields in Chinese unless the user explicitly asks for a different language. Inspect an existing showcase before replacing it. Preserve useful, still-valid content and user-authored wording when refreshing it. ### 2. Collect real evidence Inspect the repository before drafting: - Read the README, reproduction notes, reports, roadmaps, experiment summaries, and relevant source files. - Inspect Git status and recent history when they help establish the implemented scope. - Locate result images, GIFs, videos, logs, metrics, generated models, and other deliverables with `rg --files`. - Open important images and inspect video metadata or representative frames when practical. - Check paths, commands, logs, test output, and timestamps before calling a result locally verified. Do not rerun expensive experiments merely to make the page unless the user also asks for reproduction or fresh verification. Report the latest evidenced state and its date instead. ### 3. Select and label content Build a concise narrative in this order: 1. One-sentence project purpose and overall result. 2. Key conclusions, each with its evidence basis. 3. Current progress as concrete stages and outcomes. 4. A curated set of images and videos with explanatory captions. 5. Verification evidence such as commands, metrics, logs, revisions, or artifact paths. 6. Current issues or reproduction boundaries. 7. Ordered next steps, each with a completion criterion. Use these evidence labels consistently: - `本机已验证`: directly supported by a current local artifact, command, log, or test. - `仓库说明`: stated by repository documentation but not verified locally. - `分析判断`: a reasoned interpretation; state what it is based on. Do not infer completion from file presence alone. Do not present a planned step as completed. Prefer three strong media items over a gallery of repetitive screenshots. ### 4. Build the HTML Read [references/spec-format.md](references/spec-format.md), then create the JSON spec in a temporary directory so the repository is left with only the requested HTML deliverable. Run: ```bash python3 scripts/build_showcase.py \ --spec /tmp/showcase-spec.json \ --base-dir /absolute/path/to/repository \ --output /absolute/path/to/repository/showcase.html ``` Resolve `scripts/build_showcase.py` relative to this skill directory, not the target repository. Local media paths in the spec may be absolute or relative to `--base-dir`. The builder escapes text, embeds media as data URLs, omits empty sections, and fails on missing media rather than silently creating broken output. Use `--allow-remote-media` only when the user accepts a page that depends on network resources. Without that flag, remote media is rejected to preserve the single-file contract. ### 5. Verify the deliverable - Confirm the builder reports a successful output and embedded media count. - Confirm the output is a single `.html` file and every selected media path was embedded. - Open or render the page when a browser is available; otherwise inspect the generated headings and data URLs. - Check that conclusions, progress, issues, and next steps agree with the source evidence. - Report the exact output path and any relevant evidence that was intentionally omitted. ## Resource use - Use [scripts/build_showcase.py](scripts/build_showcase.py) for deterministic generation and safe media embedding. - Use [references/spec-format.md](references/spec-format.md) for the accepted JSON fields and a complete example. - Use [assets/showcase-template.html](assets/showcase-template.html) as the presentation contract; modify it only when the user explicitly asks to change the visual style.