How do I install the Source Ranking Roi Selector skill?

Run npx skillmds add srednoff888-art/source-ranking-roi-selector in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Source Ranking Roi Selector safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Source Ranking Roi Selector?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Source Ranking Roi Selector free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Source Ranking Roi Selector?

srednoff888-art (@srednoff888-art) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Source Ranking Roi Selector by srednoff888-art

Name: Source Ranking Roi Selector
Rating: 4.2 (5 reviews)
Author: srednoff888-art

Source Ranking Roi Selector

Rank UI kit, design system, component registry, design connector, 3D library, 3D asset, texture, model, and optimizer sources by project fit, license/provenance risk, dependency cost, validation burden, and token ROI. Use for UI/UX, web design, 3D web design, 3D assets, source selection, component marketplace comparison, 21st.dev/Magic, shadcn, Astryx, Figma, Canva, Three.js, R3F, model-viewer, Babylon.js, glTF, Sketchfab, Poly Haven, ambientCG, and similar source decisions.

srednoff888-art e8dc62b 2 files · 2.6 KB Updated Sep 9, 2026 1 repo stars

File contents

Source Ranking ROI Selector

Use this skill to choose external sources without spending context on every option.

Workflow

Run the source ranker:

powershell -ExecutionPolicy Bypass -File "$HOME\.codex\scripts\srednoff-os-source-ranker.ps1" -ProjectPath "<project-path>" -Brief "<task>" -Json

Prefer the highest-ranked source only when it matches the project stack and validation budget.
For medium/high-risk sources, verify license, provenance, dependency weight, accessibility, performance, and copied-code risk before use.
For UI sources, prefer local design system and shadcn-compatible copy-adapt workflows before heavy animated libraries. Consider Astryx only for React 19 projects that justify a cohesive pre-1.0 design system plus StyleX peer dependency.
For 3D sources, prefer model-viewer for simple product display, R3F/Three.js for React custom scenes, and glTF Transform for optimization.
In TURBO, compare more sources, but keep the same safety and license gates.

Checklist

Source fits stack, visual goal, and maintenance budget.
License/provenance is known before copying code or assets.
Dependency and asset-size cost is justified.
Accessibility, responsive behavior, visual QA, and performance gates are defined.
Only selected source details are loaded into context.

Guardrails

Do not copy third-party code or assets without license/provenance review.
Do not use marketplace assets with unclear licenses in production.
Do not choose a visually impressive source if it harms maintainability, accessibility, or performance without a clear payoff.
Do not adopt pre-1.0 design systems or their lab/canary packages without an explicit upgrade, dependency, accessibility, and rollback plan.

---name: source-ranking-roi-selectordescription: Rank UI kit, design system, component registry, design connector, 3D library, 3D asset, texture, model, and optimizer sources by project fit, license/provenance risk, dependency cost, validation burden, and token ROI. Use for UI/UX, web design, 3D web design, 3D assets, source selection, component marketplace comparison, 21st.dev/Magic, shadcn, Astryx, Figma, Canva, Three.js, R3F, model-viewer, Babylon.js, glTF, Sketchfab, Poly Haven, ambientCG, and similar source decisions.--- # Source Ranking ROI Selector Use this skill to choose external sources without spending context on every option. ## Workflow 1. Run the source ranker: ```powershell powershell -ExecutionPolicy Bypass -File "$HOME\.codex\scripts\srednoff-os-source-ranker.ps1" -ProjectPath "<project-path>" -Brief "<task>" -Json ``` 2. Prefer the highest-ranked source only when it matches the project stack and validation budget. 3. For medium/high-risk sources, verify license, provenance, dependency weight, accessibility, performance, and copied-code risk before use. 4. For UI sources, prefer local design system and shadcn-compatible copy-adapt workflows before heavy animated libraries. Consider Astryx only for React 19 projects that justify a cohesive pre-1.0 design system plus StyleX peer dependency. 5. For 3D sources, prefer `model-viewer` for simple product display, R3F/Three.js for React custom scenes, and glTF Transform for optimization. 6. In TURBO, compare more sources, but keep the same safety and license gates. ## Checklist - Source fits stack, visual goal, and maintenance budget. - License/provenance is known before copying code or assets. - Dependency and asset-size cost is justified. - Accessibility, responsive behavior, visual QA, and performance gates are defined. - Only selected source details are loaded into context. ## Guardrails - Do not copy third-party code or assets without license/provenance review. - Do not use marketplace assets with unclear licenses in production. - Do not choose a visually impressive source if it harms maintainability, accessibility, or performance without a clear payoff. - Do not adopt pre-1.0 design systems or their lab/canary packages without an explicit upgrade, dependency, accessibility, and rollback plan.

Frequently asked questions