Agent skill · software engineering · sickn33
markstream-migration
Audit and migrate an existing Markdown renderer to Markstream while preserving custom renderers, security policy, streaming behavior, and explicit parity gaps.
Why this skill is useful
Provides specific migration patterns and security practices for transitioning to Markstream that the AI wouldn't reliably generate on its own.
What it needs
Requires markstream-react installed locally. About 1k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Markstream Migration Overview Replace an existing Markdown renderer without silently dropping transforms, custom components, URL policy, raw-HTML behavior, or streaming semantics. Read references/adoption-checklist.md first. When to Use Use when replacing react-markdown, markdown-it, marked, or another renderer; migrating node renderers; or choosing between Markstream content, smooth streaming, and nodes. Workflow Before changing dependencies or source files, inspect the existing package manager and project conventions, preview the intended edits, and obtain explicit user approval. 1. Inventory renderer imports, call sites, plugins, HTML policy, URL transforms, allowlists, custom renderers, CSS, and tests. 2. Classify the migration as direct, renderer-custom, plugin-heavy, or security-heavy. 3. Install the framework package and explicit CSS. Preserve visible behavior before optional features. 4. Map built-ins to scoped overrides; in React prefer renderer-local component maps. 5. Use trusted custom tags only for trusted content and reserve parse transforms for irreducible token/AST requirements. 6. Keep content with smooth streaming for ordinary token streams. Use nodes only for worker parsing, shared AST ownership, or structural transforms. 7. Preserve safe HTML and strict Mermaid defaults; scope and document any trusted legacy exception. 8. Run relevant builds and behavior tests. Report mappings, intentional differences, and unresolved review. Example Limitations Markstream cannot reproduce every remark, rehype, or markdown-it plugin automatically. Visual parity does not prove security or URL-policy parity. Large migrations may require staged conversion. Security & Safety Notes Do not weaken sanitization for screenshot parity. Review dependencies, raw HTML, URL transforms, and trust boundaries explicitly.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/markstream-migration--888a1b