markstream-migration
Migrate Markdown Rendering Safely
Replacing a Markdown renderer can break rendering, streaming, and HTML safety rules. This skill creates a migration plan that preserves behavior and documents remaining gaps.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "markstream-migration" from https://skillstore.io/skills/simon-he95-markstream-migration.md and its manifest at https://skillstore.io/api/skills/simon-he95-markstream-migration/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "markstream-migration". Audit a project that uses react-markdown with custom code blocks.
Expected outcome:
- Migration class: renderer-custom.
- Direct mapping: standard Markdown content.
- Review needed: custom code block rendering and raw HTML policy.
Using "markstream-migration". Review a Vue 3 chat that streams Markdown content.
Expected outcome:
- Use chat mode for the active chat row.
- Keep smooth streaming enabled when only output pacing is needed.
- Validate completed history with streaming disabled.
Security Audit
SafeAll 20 external-command alerts are false positives caused by Markdown inline-code formatting in SKILL.md. The system-reconnaissance alert is also a false positive because it directs a security review of renderer behavior. No prompt injection, exfiltration intent, or executable command was found.
Risk Factors
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/simon-he95-markstream-migration/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/simon-he95-markstream-migration?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/simon-he95-markstream-migration?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/simon-he95-markstream-migration/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/simon-he95-markstream-migration.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
simon-he95. (2026). markstream-migration security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/simon-he95-markstream-migration/audits/1BibTeX citation
@techreport{simon-he95-simon-he95-markstream-migration-2026,
author = {simon-he95},
title = {markstream-migration security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/simon-he95-markstream-migration/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "markstream-migration security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "simon-he95"
date-released: "2026-07-19"
url: "https://skillstore.io/skills/simon-he95-markstream-migration/audits/1"
identifiers:
- type: other
value: "skillstore:simon-he95-markstream-migration:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Replace a simple renderer
Identify a low-risk renderer swap and preserve existing user-visible Markdown behavior.
Migrate a customized chat UI
Review custom renderers and streaming settings before moving an AI chat interface to Markstream.
Assess complex Markdown pipelines
Document plugin, sanitization, and HTML gaps before deciding whether a migration is appropriate.
Try These Prompts
Audit this repository for its current Markdown renderer. List every call site and classify the migration risk.
Create a Markstream migration plan for the current Markdown renderer. Preserve styles and visible behavior first.
Map the custom Markdown renderers in this project to scoped Markstream component overrides. List any unsupported behavior.
Review this chat Markdown migration for streaming, raw HTML, URL policy, and Mermaid risks. Recommend safe Markstream settings and validation steps.
Best Practices
- Audit call sites and security settings before replacing the renderer.
- Preserve current behavior before adding Markstream-specific features.
- Run the smallest relevant test or build after each migration stage.
Avoid
- Do not claim full parity before reviewing plugins and custom renderers.
- Do not enable trusted HTML globally to match one legacy call site.
- Do not move to nodes streaming when content streaming is sufficient.
Frequently Asked Questions
What does this skill audit?
Does it migrate code automatically?
When is a migration direct?
How does it handle custom renderers?
Does it review HTML safety?
When should nodes streaming be used?
Developer Details
Author
simon-he95License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
aeb1814252a7125c8b732442bf1e7f2cd1f686c1
Maintenance freshness
7/19/2026
Usage
0 downloads ยท 0 views
File structure