skill-sarveshtalele-mcp-skills-registry-ui-modernization · by Install
$ agentstack add skill-sarveshtalele-mcp-skills-registry-ui-modernization ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-sarveshtalele-mcp-skills-registry-ui-modernization) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
ui-modernization
Plan a legacy UI migration to a modern component framework (React by default): component inventory, target tree, and starter stubs.
When to use
When modernizing a front end. Triggers: modernize UI, convert to React, UI migration, frontend modernization.
Inputs
screens(array of strings, required) — legacy screen/page names.framework(string, optional, defaultreact).
Outputs
plan_markdown— inventory, target tree, approach, definition of done.components— derived component names.sample_component— a starter component stub.
How it works
Derives PascalCase component names from screen names, builds a target tree, and emits a strangler migration approach with a per-screen DoD.
User stories
- As a front-end lead, I get a component map and a sample to start porting.
Edge cases
- A single screen passed as a string is accepted.
- Empty screen list → clear error (nothing to plan).
- Messy names with punctuation → sanitised into valid component identifiers.
Files
See [DOCS.md](DOCS.md). Figma mapping guidance lives in figma/.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: sarveshtalele
- Source: sarveshtalele/mcp-skills-registry
- License: MIT
- Homepage: https://sarveshtalele-mcp-skills-registry.hf.space
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.