Render Workspace Html

Community

ShaishavMaisuria

render-workspace-html

Renders the paper-workspace (outputs + lifecycle progress) into a single self-contained HTML dashboard the author can open in a browser, and refreshes it on request. Use when a researcher says "show me an HTML view", "give me a dashboard", "can I see my progress in a browser", "visualize what's been done", "make an HTML report", or "update the dashboard". Offered as an option whenever a visual overview would help (it is opt-in, not generated unprompted), and re-run after each significant change so the page stays current. The output is one local dashboard.html with inline CSS — no network, no external assets, light/dark aware — listing every generated artifact by stage with clickable links and a recent-activity timeline. Trigger words - html, dashboard, browser view, visualize progress, html report, update the html.

Overview

Publisher	ShaishavMaisuria
Repository	`research-paper-lifecycle-skills`
Skill name	`render-workspace-html`
Stars	59
Forks	22
Bundled files	1
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by ShaishavMaisuria on GitHub. Read the source before you install it.

Installation

Install the Render Workspace Html AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/ShaishavMaisuria/research-paper-lifecycle-skills/tree/main/skills/render-workspace-html
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/ShaishavMaisuria/research-paper-lifecycle-skills/tree/main/skills/render-workspace-html

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/ShaishavMaisuria/research-paper-lifecycle-skills.git /tmp/research-paper-lifecycle-skills
mkdir -p .claude/skills
cp -r /tmp/research-paper-lifecycle-skills/skills/render-workspace-html .claude/skills/render-workspace-html

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Render Workspace Html in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Render Workspace Html on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Render Workspace Html is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Render Workspace HTML

Turns the paper-workspace/ directory into a dashboard the author can open in a browser — lifecycle progress, every generated artifact grouped by stage with clickable links, and a recent-activity timeline. It's the visual "where am I / what's been done" view on top of the files the other skills produce.

This is opt-in: offer it when a visual overview would genuinely help (after a batch of work, or when the author asks), not on every turn. When the author wants it kept live, refresh it after each significant change so it never goes stale.

When to use

The author asks for an HTML view / dashboard / browser-readable summary of progress.
After several skills have run and the workspace has enough in it to be worth a glance.
The author says "keep the HTML updated" — then regenerate it at the end of each request that changed the workspace.

Process

Offer, don't impose. If the author hasn't asked, ask once: "Want an HTML dashboard of your progress? I can refresh it after each change." Generate only on yes.
Generate (deterministic):
```
python3 scripts/build_dashboard.py --workspace paper-workspace
```
It reads paper-workspace/INDEX.md and the stage folders (and .paper-memory/profile.yml for the title/venue if present) and writes paper-workspace/dashboard.html — one self-contained file, inline CSS, no network or external assets, light/dark aware. Exit 1 only if there is no workspace yet.
Point the author to it (open paper-workspace/dashboard.html). Summarize what it shows.
Refresh on request. If the author asked to keep it live, re-run step 2 at the end of any request that wrote new artifacts, and say you refreshed it. Otherwise regenerate only when asked again.

Output

paper-workspace/dashboard.html — a stage-by-stage progress bar, artifact cards with links to each output, and a recent-activity timeline from INDEX.md. Opens offline in any browser.

Richer reports

This skill is built for speed and zero dependencies: one self-contained dashboard.html that works offline and can be refreshed repeatedly. If the author asks for a more designed or interactive report, and the current agent runtime has a separate web artifact, frontend, or report-building skill installed, offer to hand the workspace summary to that tool. Keep this dashboard as the default status view; use richer builders only when the author asks for presentation-grade HTML.

Guardrails

Local only. The dashboard is a local file built from local artifacts; never upload it, host it, or copy it into this skills repo. No third-party paper content is rendered (only the author's own outputs).
Self-contained, no tracking. Inline CSS only — no external scripts, fonts, images, or analytics.
Opt-in. Don't generate the dashboard unprompted on every turn; offer it, then refresh per the author's preference.
It only displays what other skills produced; it never edits artifacts, scores, or the paper.

Memory

Uses the shared .paper-memory/ convention (paper-memory-convention.md).

At start: read profile.yml for the paper title/venue to label the dashboard; check whether the author opted into auto-refresh.
At end: record the auto-refresh preference (date · render-workspace-html · auto-refresh on/off) so later runs honor it without re-asking.
Create .paper-memory/ on demand; local-only, never uploaded.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

scripts/build_dashboard.py6 KB

Frequently asked questions

What does the Render Workspace Html AI skill do?

Why use Render Workspace Html on TypingMind?

Because you install it once and use it with any model. Render Workspace Html is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Render Workspace Html in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ShaishavMaisuria/research-paper-lifecycle-skills/tree/main/skills/render-workspace-html. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Render Workspace Html?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Render Workspace Html?

As many as you like. As long as a model supports skills, you can use Render Workspace Html with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Render Workspace Html AI skill free?

Yes. It is published on GitHub by ShaishavMaisuria under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Serving Llms Vllm

NousResearch

OrganizationPopular

vLLM: high-throughput LLM serving, OpenAI API, quantization.

Huggingface Hub

HuggingFace hf CLI: search/download/upload models, datasets.

Pytorch Lightning

Clean training loops with built-in distributed support.

Troubleshoot

Investigate unexpected behavior in the current Copilot agent session by analyzing its event log. Use when the user asks why something happened, why a request was slow, why a tool was or was not used,…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Render Workspace HTML

When to use

Process

Output

Richer reports

Guardrails

Memory

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now