Router skill for all MCS-MCP chart visualizations. Trigger this skill whenever any mcs-mcp analysis tool result is present in the conversation and the user asks to visualize, chart, plot, or show it. This router maps the tool that produced the result to the correct chart sub-skill. Do NOT attempt to build any chart ad-hoc — always read the sub-skill first. --- # MCS Charts Router This is the sole entry point for all MCS-MCP chart skills. When a chart request arrives, identify which analysis tool produced the data, then read and follow the matching sub-skill before writing any code. --- ## Step 1 — Identify the data source Look at the conversation for the most recent mcs-mcp tool result. Match it to one of the tools in the routing table below. --- ## Step 2 — Routing Table ``` Tool that produced the data Sub-skill path (relative to this file) ──────────────────────────────── ────────────────────────────────────────────── analyze_process_stability analyze_process_stability/s.md analyze_throughput analyze_throughput/s.md analyze_wip_stability analyze_wip_stability/s.md analyze_wip_age_stability analyze_wip_age_stability/s.md analyze_work_item_age analyze_work_item_age/s.md analyze_process_evolution analyze_process_evolution/s.md analyze_residence_time analyze_residence_time/s.md generate_cfd_data generate_cfd_data/s.md analyze_cycle_time analyze_cycle_time/s.md analyze_status_persistence analyze_status_persistence/s.md analyze_flow_debt analyze_flow_debt/s.md analyze_yield analyze_yield/s.md forecast_monte_carlo forecast_monte_carlo/s.md forecast_backtest forecast_backtest/s.md ``` Sub-folder names match the exact tool name as registered in the MCP server. --- ## Step 3 — Read the sub-skill, then build Use the `view` tool to read the matched
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Sort by downloads/likes/comments/updated to find higher-quality skills.
4. Which import methods are supported?
Upload archive: .zip / .skill (recommended)
Upload skills folder
Import from GitHub repository
Note: file size for all methods should be within 10MB.
5. How to use in Claude / Codex?
Typical paths (may vary by local setup):
Claude Code:~/.claude/skills/
Codex CLI:~/.codex/skills/
One SKILL.md can usually be reused across tools.
6. Can one skill be shared across tools?
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
7. Are these skills safe to use?
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
8. Why does it not work after import?
Most common reasons:
Wrong folder path or nested one level too deep
Invalid/incomplete SKILL.md fields or format
Dependencies missing (Python/Node/CLI)
Tool has not reloaded skills yet
9. Does SkillWink include duplicates/low-quality skills?
We try to avoid that. Use ranking + comments to surface better skills: