gitea/skills/html-export/SKILL.md

---

name: html-export description: Export one Gitea wiki page or issue as a single self-contained HTML file. Parse the link with tools/gitea-link.sh, resolve that kind's layout and style through tools/html-style.sh (kind, then DEFAULT, then the built-in report/minimal), then render with tools/html-render.sh, which puts the markdown through Gitea's own renderer and inlines every asset. A request without a wiki or issue link stops the skill immediately: never guess the repository, the page or the issue number. Use when a page or issue has to leave Gitea as a document; not for choosing which template a kind uses - that is jsc-gitea:html-style.

html-export — a wiki page or issue becomes one HTML file

The link is the only input. The output is one file that opens anywhere, with no external asset.

Steps

1. Link gate. Run tools/gitea-link.sh parse {url}. Exit 3 or no link in the request: stop and report it. Never fall back to the working directory's remote or to a page name the user mentioned in passing. Completion condition: kind is wiki or issue, and repo plus page or index are known.

2. Work out the kind key — it decides which template applies:

   • wiki page → WIKI:{prefix}, where the prefix is the page name up to the first underscore (ANALYZE_D3F1A2B0 → WIKI:ANALYZE; a page with no underscore uses the whole name).
   • issue → run tools/issue.sh labels-of {repo} {index} and try ISSUE:{label} for each label in order; the first one tools/html-style.sh get answers with source project or global wins. No label matches: use ISSUE:DEFAULT.

   Completion condition: exactly one kind key is chosen, and you can say which label or prefix produced it.

3. Run tools/html-style.sh get {key}. It always prints layout<TAB>style<TAB>source. Read the third column and report it: project or global means the user configured this kind; default means it fell back to the DEFAULT row; builtin means nothing is configured at all and report/minimal was used. For default and builtin, tell the user in one line that jsc-gitea:html-style can set this kind's own template. Completion condition: layout, style and source are reported before anything is rendered.

4. Fetch the content: jsc-gitea:wiki wiki-get for a page, or tools/issue.sh title plus tools/issue.sh body for an issue. Exit 4 (page missing) or an API failure stops the skill with the page name or issue number in the report. Completion condition: the markdown and the document title are in hand.

5. Prepare the markdown — this step MUST run as a sub agent. Convert [[display|page]] wiki links to absolute URLs from wiki-url; the renderer does not resolve them, so they would ship as literal brackets. Strip personal data — an exported file travels further than the page it came from. Leave everything else exactly as written; this step never rewrites the content. Completion condition: no [[...]] remains, and the diff against the source is limited to link conversion and personal-data removal.

6. Ask per jsc-ask:ask rules where the file goes, proposing ./.jsc/html/{page-or-issue}.html. State the impact scope: a path inside a repository gets committed unless it is ignored. Completion condition: the user has confirmed one output path.

7. Render: tools/html-render.sh --markdown {file} --title {title} --layout {layout} --style {style} --source-url {absolute URL} --out {path}. Exit 1 means Gitea's renderer failed — report it and stop, with no half-rendered file left behind. Completion condition: the file exists, and the report names its path, the layout, the style and where that pair came from.

Rules

• One link, one file. Batch export is a loop the caller runs, not something this skill decides on its own.
• The rendered file inlines CSS and scripts on purpose: it is usually sent to someone outside Gitea, and an external asset breaks on their machine.
• The layout and style are never chosen by inspecting the content. The configuration decides, and jsc-gitea:html-style owns the configuration.