markstream-migration
Audit and migrate an existing Markdown renderer to Markstream while preserving custom renderers, security policy, streaming behavior, and explicit parity gaps.
Profile →npx skills add sickn33/agentic-awesome-skills --skill markstream-migration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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](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 s
- Overview
- When to Use
- Workflow
- Example
- Limitations
- Security & Safety Notes
What does the markstream-migration skill do?
Audit and migrate an existing Markdown renderer to Markstream while preserving custom renderers, security policy, streaming behavior, and explicit parity gaps.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill markstream-migration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.