HeroUI v2 to v3 migration guide for agents. Use when migrating HeroUI v2 apps to v3, upgrading components, or accessing migration documentation. Keywords: HeroUI migration, v2 to v3, migration guide, upgrade HeroUI.
68
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Low
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The runtime workflow for this skill ingests free text from externally hosted (potentially user-manipulated) migration guide MDX fetched over HTTP (e.g., `scripts/get_migration_guide.mjs`, `scripts/get_component_migration_guides.mjs`, `scripts/get_hooks_migration_guide.mjs`, `scripts/get_styling_migration_guide.mjs`), so outsider-authored content can be read at runtime.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The runtime scripts fetch MDX migration guides from https://heroui-git-docs-migration-heroui.vercel.app/docs/react/migration (and SKILL.md also suggests executing a remote install script via curl -fsSL https://heroui.com/install | bash), so remote content is fetched during execution and can directly control agent instructions or execute code.
2abad42
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.