Hi @nsmith β really enjoyed using this skill; I published a multi-section technical report through ht-ml.app and it worked beautifully. π
I noticed the repo doesn't yet have contributor scaffolding, and since it's young and clearly built to be installed/extended by others, I'd love to add some. Proposed, all additive (no changes to SKILL.md, templates, or behavior):
CONTRIBUTING.md β documents the existing flow: mise install / mise run validate, the self-contained-template convention (inline all CSS/JS/SVG, <!-- REPLACE --> placeholders, add a catalog row in assets/templates/README.mdand the table in SKILL.md), and the eval setup in evals/..github/ISSUE_TEMPLATE/ β a bug report, a "new template request" form, and a config..github/PULL_REQUEST_TEMPLATE.md β a short checklist (validated, self-contained, catalog updated).
Happy to open the PR right away if you're open to it β and equally happy to adjust the scope to whatever fits your vision. Thanks for building this!
Hi @nsmith β really enjoyed using this skill; I published a multi-section technical report through ht-ml.app and it worked beautifully. π
I noticed the repo doesn't yet have contributor scaffolding, and since it's young and clearly built to be installed/extended by others, I'd love to add some. Proposed, all additive (no changes to
SKILL.md, templates, or behavior):CONTRIBUTING.mdβ documents the existing flow:mise install/mise run validate, the self-contained-template convention (inline all CSS/JS/SVG,<!-- REPLACE -->placeholders, add a catalog row inassets/templates/README.mdand the table inSKILL.md), and the eval setup inevals/..github/ISSUE_TEMPLATE/β a bug report, a "new template request" form, and a config..github/PULL_REQUEST_TEMPLATE.mdβ a short checklist (validated, self-contained, catalog updated).Happy to open the PR right away if you're open to it β and equally happy to adjust the scope to whatever fits your vision. Thanks for building this!