MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
使用 vivado-mcp 分析 Vivado setup、hold 和脉宽时序，比较保存的基线并按证据迭代修复；支持离线报告分析，不将摘要指标视为完整签核。
Install Vivado Timing Closure
$ npx skills add mapleleavessssssss-wq/vivado-mcp --skill vivado-timing-closure -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mapleleavessssssss-wq/vivado-mcp vivado-timing-closure --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mapleleavessssssss-wq/vivado-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vivado-timing-closure .claude/skills/vivado-timing-closure && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vivado-timing-closure" agent skill from https://github.com/mapleleavessssssss-wq/vivado-mcp/tree/main/skills/vivado-timing-closure into .claude/skills/vivado-timing-closure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vivado-timing-closure", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mapleleavessssssss-wq/vivado-mcp/tree/main/skills/vivado-timing-closureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mapleleavessssssss-wq/vivado-mcp --skill vivado-timing-closure -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mapleleavessssssss-wq/vivado-mcp vivado-timing-closure --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mapleleavessssssss-wq/vivado-mcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/vivado-timing-closure .agents/skills/vivado-timing-closure && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vivado-timing-closure" agent skill from https://github.com/mapleleavessssssss-wq/vivado-mcp/tree/main/skills/vivado-timing-closure into .agents/skills/vivado-timing-closure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vivado-timing-closure", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mapleleavessssssss-wq/vivado-mcp --skill vivado-timing-closure -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mapleleavessssssss-wq/vivado-mcp vivado-timing-closure --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mapleleavessssssss-wq/vivado-mcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/vivado-timing-closure .cursor/skills/vivado-timing-closure && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vivado-timing-closure" agent skill from https://github.com/mapleleavessssssss-wq/vivado-mcp/tree/main/skills/vivado-timing-closure into .cursor/skills/vivado-timing-closure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vivado-timing-closure", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mapleleavessssssss-wq/vivado-mcp.git --path skills/vivado-timing-closure--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mapleleavessssssss-wq/vivado-mcp --skill vivado-timing-closure -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mapleleavessssssss-wq/vivado-mcp vivado-timing-closure --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mapleleavessssssss-wq/vivado-mcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/vivado-timing-closure .gemini/skills/vivado-timing-closure && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vivado-timing-closure" agent skill from https://github.com/mapleleavessssssss-wq/vivado-mcp/tree/main/skills/vivado-timing-closure into .gemini/skills/vivado-timing-closure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vivado-timing-closure", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mapleleavessssssss-wq/vivado-mcp vivado-timing-closureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mapleleavessssssss-wq/vivado-mcp --skill vivado-timing-closure -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mapleleavessssssss-wq/vivado-mcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/vivado-timing-closure .github/skills/vivado-timing-closure && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vivado-timing-closure" agent skill from https://github.com/mapleleavessssssss-wq/vivado-mcp/tree/main/skills/vivado-timing-closure into .github/skills/vivado-timing-closure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vivado-timing-closure", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mapleleavessssssss-wq/vivado-mcp --skill vivado-timing-closure -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mapleleavessssssss-wq/vivado-mcp vivado-timing-closure --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mapleleavessssssss-wq/vivado-mcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/vivado-timing-closure .opencode/skills/vivado-timing-closure && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vivado-timing-closure" agent skill from https://github.com/mapleleavessssssss-wq/vivado-mcp/tree/main/skills/vivado-timing-closure into .opencode/skills/vivado-timing-closure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vivado-timing-closure", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vivado-timing-closure- GitHub stars
- 148
- Token cost
- ~548 tokens
- SKILL.md length
- 89 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
使用 vivado-mcp 分析 Vivado setup、hold 和脉宽时序，比较保存的基线并按证据迭代修复；支持离线报告分析，不将摘要指标视为完整签核。
- Tasks that involve MCP servers
- SKILL.md covers 记录可比较的基线, 分类后修复 and 同条件复测
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Vivado Timing Closure is an agent skill from mapleleavessssssss-wq/vivado-mcp. 使用 vivado-mcp 分析 Vivado setup、hold 和脉宽时序，比较保存的基线并按证据迭代修复；支持离线报告分析，不将摘要指标视为完整签核。
Its SKILL.md is about 550 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol. The repository describes itself as: Vivado MCP server — 让 Claude Code / Cursor / Codex 驱动本地 FPGA 全流程。30 个精选工具、8 个证据驱动 Prompt、doctor 环境自检、GUI/Tcl/attach 会话，以及时序和 CRITICAL WARNING 中文诊断。 The licence is Apache-2.0.
When your agent uses it
- Tasks that involve MCP servers
Example prompts
- “/vivado-timing-closure”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 41745b2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are python).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vivado Timing Closure loads about 548 tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 89 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mapleleavessssssss-wq/vivado-mcp at commit 41745b2, republished under its Apache-2.0 licence (© mapleleavessssssss-wq). 89 words, ~548 tokens.
Download SKILL.mdSave it as
.claude/skills/vivado-timing-closure/SKILL.md (or your agent's skills folder).- name
- vivado-timing-closure
- description
- 使用 vivado-mcp 分析 Vivado setup、hold 和脉宽时序，比较保存的基线并按证据迭代修复；支持离线报告分析，不将摘要指标视为完整签核。
Vivado 时序收敛
可用入口：get_project_info、get_timing_report、get_utilization_report、get_critical_warnings、get_cdc_report、run_tcl、safe_tcl。
只分析时不启动构建；用户要求优化时继续完成已授权的 RTL/XDC/策略修复。保持接口、目标频率和功能语义；改变这些条件需要对应授权。此流程不包含硬件编程。
记录可比较的基线
现场用 get_project_info 确认工程、器件与 run；报告必须对应当前 source/XDC。离线输入不需要 Vivado 会话，但结论只覆盖所给文件。
get_timing_report(session_id="design", output_format="json")
get_timing_report(output_format="json", report_file="/work/reports/before.rpt")记录 provenance、stage、context、parse_status、metrics 和 verdict。setup、hold、pulse_width 的缺失值是 null，不能当作零。met_observed_checks 只说明已观察指标满足；verdict.signoff 为 false，不等于完整签核。
需要比较时，用宿主文件工具把返回的完整 JSON 正文原样保存为新基线文件，包含 schema、来源和上下文；不要只存 metrics，也不要把原始 Tcl 文本传给 baseline_file。MCP 不会自动写入报告。
分类后修复
- 先核对时钟与约束覆盖，再解释最差路径。有现场会话时用
run_tcl获取report_clock_interaction -return_string、report_methodology -return_string；离线缺少旁证时列为未验证。CDC 嫌疑需要结构与协议证据。 - 用返回路径与可用资源/告警报告区分逻辑深度、扇出/布线、拥塞、I/O 约束和时钟问题；现场可调用
get_utilization_report、get_critical_warnings。布局策略不能修复逻辑协议错误。 - 一次只验证一个根因假设。保留 baseline 和最佳候选，记录具体 RTL/XDC/策略变更。用户输入的路径/对象通过
safe_tcl，不要拼入原始 Tcl。 set_false_path和 multicycle 不是性能优化手段；它们与 waiver 只能依据真实功能关系，不能用于消除真实违例。没有协议证据时报告不确定性，继续不依赖该例外的分析。- CDC 嫌疑通过
get_cdc_report与实际同步结构核对。set_clock_groups会覆盖重叠路径的set_max_delay -datapath_only；用report_exceptions核实生效范围。set_bus_skew需用独立report_bus_skew检查，不能从 WNS 推断。
同条件复测
重跑受影响阶段后读取新报告，或对新保存的原始报告进行离线比较：
get_timing_report(session_id="design", output_format="json", baseline_file="/work/reports/baseline.json")
get_timing_report(output_format="json", report_file="/work/reports/after.rpt", baseline_file="/work/reports/baseline.json")先读 comparison.status 与 reasons，再解释 deltas。不同/未知设计或阶段不能比较；即使 design/device/stage 相同，约束身份未知时差值仅为观察，不证明优化效果。该接口的比较 authoritative 为 false，须用独立的输入、约束和路径覆盖记录说明可比性。
收敛验收需同一当前 post-route 设计的 setup/hold/pulse-width、完整约束覆盖、route、DRC/methodology 和适用 CDC 检查。仅 WNS 改善或摘要非负不够。达到目标后交付证据；连续两轮无实质改善时保留最佳结果并重新归因，受总预算限制停止，不把停滞称成功。报告数值变化、可比性、变更、剩余违例和未验证检查。
© mapleleavessssssss-wq, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/vivado-timing-closure of mapleleavessssssss-wq/vivado-mcp.
Open the folder on GitHubat commit 41745b2
Compare with similar skills
Vivado Timing Closure next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vivado Timing Closure this skillmapleleavessssssss-wq/vivado-mcp | 148 | — | ~548 | Automated safety check: Pass | Apache-2.0 | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 4 repos | ~1.2k | Automated safety check: Pass | MIT | |
| MCP Integration for Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Context Mode Output Sandboxmksglu/context-mode | 26k | — | ~4.1k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
MCP Server Builder
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
- Official
MCP Integration for Plugins
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
Crush Configuration
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
Context Mode Output Sandbox
mksglu/context-mode
Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.
Warp GUI to Agent CLI Migration
warpdotdev/warp
Migrates the compatible subset of settings and global file-based MCP servers from the Warp desktop app into Warp Agent CLI without exposing credentials or state.
More from mapleleavessssssss-wq/vivado-mcp
Vivado Cdc Audit
mapleleavessssssss-wq/vivado-mcp
使用 vivado-mcp 结构化读取 Vivado CDC 报告，核对跨时钟域的同步结构、协议和约束；支持离线报告审查，不把空报告或零严重项当作完整签核。
Vivado Constraints Authoring
mapleleavessssssss-wq/vivado-mcp
为 Vivado 工程建立或审查 XDC 时钟、I/O 延迟和时序例外，依据板级与接口参数验证对象和约束覆盖；不猜引脚、频率或外设时序，不用例外掩盖违例。
Vivado Project Bringup
mapleleavessssssss-wq/vivado-mcp
接管或建立 Vivado FPGA 工程，核对源文件、约束、顶层和构建状态，通过 vivado-mcp 完成请求范围内的综合、实现和产物检查。
Vivado Waveform Debug
mapleleavessssssss-wq/vivado-mcp
使用 vivado-mcp 离线查询 VCD 波形，定位复位、X/Z、信号变化和握手问题；需要新证据时从已选 XSim 仿真导出有限窗口，不把波形查询当测试判定。
Related
Works with
Categories
Questions about Vivado Timing Closure
What does Vivado Timing Closure do?
使用 vivado-mcp 分析 Vivado setup、hold 和脉宽时序，比较保存的基线并按证据迭代修复；支持离线报告分析，不将摘要指标视为完整签核。. Vivado Timing Closure is an agent skill from mapleleavessssssss-wq/vivado-mcp.
When should I use Vivado Timing Closure?
Vivado Timing Closure fits situations like: tasks that involve MCP servers.
How do I install Vivado Timing Closure in Claude Code?
Run `npx skills add mapleleavessssssss-wq/vivado-mcp --skill vivado-timing-closure -a claude-code`. Or copy the skill folder (skills/vivado-timing-closure in mapleleavessssssss-wq/vivado-mcp) into .claude/skills/vivado-timing-closure in your project. Claude Code loads it when a task matches its description.
How do I install Vivado Timing Closure in Codex?
Run `npx skills add mapleleavessssssss-wq/vivado-mcp --skill vivado-timing-closure -a codex`. Or copy the skill folder (skills/vivado-timing-closure in mapleleavessssssss-wq/vivado-mcp) into .agents/skills/vivado-timing-closure in your project. Codex loads it when a task matches its description.
Can I use Vivado Timing Closure in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mapleleavessssssss-wq/vivado-mcp --skill vivado-timing-closure -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vivado-timing-closure, .gemini/skills/vivado-timing-closure, .github/skills/vivado-timing-closure and .opencode/skills/vivado-timing-closure in your project.
What does Vivado Timing Closure need to run?
SKILL.md names no scripts, command-line tools or credentials: Vivado Timing Closure is instructions for the agent only. Our summary lists: Python 3.
Does Vivado Timing Closure access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Vivado Timing Closure safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vivado Timing Closure use?
Vivado Timing Closure is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vivado Timing Closure use?
About 548 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vivado Timing Closure?
Skills that share tags, products or a category with Vivado Timing Closure: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Crush Configuration (charmbracelet/crush, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vivado Timing Closure?
mapleleavessssssss-wq (a GitHub user) maintains it in mapleleavessssssss-wq/vivado-mcp, which has 148 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 22, 2026.
Source: mapleleavessssssss-wq/vivado-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.