Agent skill

Vivado Project Bringup

by mapleleavessssssss-wq in mapleleavessssssss-wq/vivado-mcp

接管或建立 Vivado FPGA 工程,核对源文件、约束、顶层和构建状态,通过 vivado-mcp 完成请求范围内的综合、实现和产物检查。

Apache-2.0Auto-check passedAgent Workflows

Install Vivado Project Bringup

skills CLI
$ npx skills add mapleleavessssssss-wq/vivado-mcp --skill vivado-project-bringup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mapleleavessssssss-wq/vivado-mcp vivado-project-bringup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mapleleavessssssss-wq/vivado-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vivado-project-bringup .claude/skills/vivado-project-bringup && rm -rf skills-src

Use ~/.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/

Facts

Skill name
vivado-project-bringup
GitHub stars
148
Token cost
~571 tokens
SKILL.md length
101 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
Apache-2.0

At a glance

接管或建立 Vivado FPGA 工程,核对源文件、约束、顶层和构建状态,通过 vivado-mcp 完成请求范围内的综合、实现和产物检查。

  • Works in 6 steps: 综合前执行 verilog_compile_check 与… → 有可用 testbench 且请求包含功能验证时,执行… → run_synthesis 后以 get_run_progress… → …
  • 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 Project Bringup is an agent skill from mapleleavessssssss-wq/vivado-mcp. 接管或建立 Vivado FPGA 工程,核对源文件、约束、顶层和构建状态,通过 vivado-mcp 完成请求范围内的综合、实现和产物检查。

Its SKILL.md is about 570 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-project-bringup”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. 综合前执行 verilog_compile_check 与 xdc_lint,核对实际语言、文件集和工具覆盖;这是静态预检,不能替代 Vivado elaboration 或行为验证。
  2. 有可用 testbench 且请求包含功能验证时,执行 compile/elaborate 和有限仿真,记录 assertion/scoreboard、测试完成标志、时长和失败数。没有 testbench 或只请求构建时标记“功能未验证”,按已有授权继续构建,不把它算作仿真…
  3. run_synthesis 后以 get_run_progress 确认实际结果,保留首个错误;有跨域传输时用 get_cdc_report 建立结构检查基线,并核对时钟覆盖。进程结束不等于成功。
  4. 仅在请求范围需要时 run_implementation,检查实际 run 状态。变更后重跑受影响阶段,记录本轮输入和报告来源。
  5. get_timing_report(output_format="json") 与 get_utilization_report 记录新基线;综合数据只能作早期估计。post-route 还需约束覆盖、route、DRC、methodology 和适用…
  6. 请求生成 bitstream 时先 check_bitstream_readiness,与本轮报告一致后才 generate_bitstream。需要时用 parse_bit_header 核对器件;文件存在不证明板上功能正常。

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 Project Bringup loads about 571 tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 101 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~24
When it runs · the whole SKILL.md, loaded when a task matches
~571

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). 101 words, ~571 tokens.

Download SKILL.mdSave it as .claude/skills/vivado-project-bringup/SKILL.md (or your agent's skills folder).
name
vivado-project-bringup
description
接管或建立 Vivado FPGA 工程,核对源文件、约束、顶层和构建状态,通过 vivado-mcp 完成请求范围内的综合、实现和产物检查。

Vivado 工程 Bring-up

可用入口:list_sessions、start_session、get_project_info、get_critical_warnings、verilog_compile_check、xdc_lint、get_cdc_report、get_timing_report、get_utilization_report、run_synthesis、run_implementation、get_run_progress、check_bitstream_readiness、generate_bitstream、parse_bit_header、run_tcl、safe_tcl。

使用已连接的 vivado-mcp。先区分用户要接管已有工程、创建工程还是只查看报告;分析请求不自动启动构建。复用已有授权完成常规修复,不因切换诊断工具重复确认。只有明确请求才编程硬件。

确定工程与基线

  • 用 list_sessions 找到目标会话,必要时才 start_session;后续所有现场工具携带同一 session_id,不要并行修改同一工程。
  • 用 get_project_info 核对工程、器件、top 和 run 状态;再经 run_tcl 查询 source/constraint/simulation fileset。不能从工程文件名猜测器件或板卡引脚。
  • 缺少器件、接口约束或期望行为时,指出哪些步骤受阻,继续源文件、日志等可做的检查。保留已有源文件和用户改动。
  • 用 get_critical_warnings 定位首个根因。综合尚未完成时,设计报告不可用是阶段限制,不是无问题。

建立或修复

创建工程只在用户要求时进行。路径、实例名和用户输入经 safe_tcl 参数转义;固定的查询命令可用 run_tcl。以下是 MCP 调用示例,需替换为已核对路径和会话:

python
safe_tcl(template="open_project {0}", args=["/work/design/design.xpr"], session_id="design")
safe_tcl(template="add_files -fileset constrs_1 {0}", args=["/work/design/board.xdc"], session_id="design")

PL 工程先核对 source/top 与 XDC 的端口对应关系。BD 工程须核对时钟、复位、接口和地址,完成 validate_bd_design、生成 output products 与 wrapper,再进入综合。不要为单个缺失 IP 产物批量升级所有 IP。

构建、复测和交付

  1. 综合前执行 verilog_compile_check 与 xdc_lint,核对实际语言、文件集和工具覆盖;这是静态预检,不能替代 Vivado elaboration 或行为验证。
  2. 有可用 testbench 且请求包含功能验证时,执行 compile/elaborate 和有限仿真,记录 assertion/scoreboard、测试完成标志、时长和失败数。没有 testbench 或只请求构建时标记“功能未验证”,按已有授权继续构建,不把它算作仿真 PASS;真实失败不得被下游成功掩盖。
  3. run_synthesis 后以 get_run_progress 确认实际结果,保留首个错误;有跨域传输时用 get_cdc_report 建立结构检查基线,并核对时钟覆盖。进程结束不等于成功。
  4. 仅在请求范围需要时 run_implementation,检查实际 run 状态。变更后重跑受影响阶段,记录本轮输入和报告来源。
  5. get_timing_report(output_format="json") 与 get_utilization_report 记录新基线;综合数据只能作早期估计。post-route 还需约束覆盖、route、DRC、methodology 和适用 CDC/bus-skew 证据。
  6. 请求生成 bitstream 时先 check_bitstream_readiness,与本轮报告一致后才 generate_bitstream。需要时用 parse_bit_header 核对器件;文件存在不证明板上功能正常。

按阶段列出“执行/未执行、PASS/FAIL/未验证、证据来源、阻塞原因”。构建成功与功能验证分开报告,不能把缺测试的阶段补成 PASS。

每次修复记录“原问题 → 最小变更 → 相同条件复测”。达到请求结果即停止;连续两轮无改善则保留最佳结果并重新分析,不能循环重建或放宽约束制造通过。交付工程/器件、完成阶段、实际产物路径、关键报告与未验证项。未请求硬件下载时,到构建和产物验证为止。

© 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-project-bringup of mapleleavessssssss-wq/vivado-mcp.

Open the folder on GitHubat commit 41745b2

Compare with similar skills

Vivado Project Bringup 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.

Vivado Project Bringup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vivado Project Bringup this skillmapleleavessssssss-wq/vivado-mcp148—~571Automated safety check: PassApache-2.0
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k4 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
Crush Configurationcharmbracelet/crush29k—~3.7kAutomated safety check: PassCustom licence
Context Mode Output Sandboxmksglu/context-mode26k—~4.1kAutomated safety check: PassCustom licence

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • 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.

    78k GitHub starsUsed in 4 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    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.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed
  • 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.

    29k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • 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.

    26k GitHub stars~4.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • 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.

    65k GitHub starsUsed in 1 repo~2.1k tokens
    Agent WorkflowsAuto-check passed

More from mapleleavessssssss-wq/vivado-mcp

  • Vivado Cdc Audit

    mapleleavessssssss-wq/vivado-mcp

    使用 vivado-mcp 结构化读取 Vivado CDC 报告,核对跨时钟域的同步结构、协议和约束;支持离线报告审查,不把空报告或零严重项当作完整签核。

    148 GitHub stars~528 tokensUpdated 19 days ago
    Auto-check passed
  • Vivado Constraints Authoring

    mapleleavessssssss-wq/vivado-mcp

    为 Vivado 工程建立或审查 XDC 时钟、I/O 延迟和时序例外,依据板级与接口参数验证对象和约束覆盖;不猜引脚、频率或外设时序,不用例外掩盖违例。

    148 GitHub stars~518 tokensUpdated 19 days ago
    Auto-check passed
  • Vivado Timing Closure

    mapleleavessssssss-wq/vivado-mcp

    使用 vivado-mcp 分析 Vivado setup、hold 和脉宽时序,比较保存的基线并按证据迭代修复;支持离线报告分析,不将摘要指标视为完整签核。

    148 GitHub stars~548 tokensUpdated 19 days ago
    Auto-check passed
  • Vivado Waveform Debug

    mapleleavessssssss-wq/vivado-mcp

    使用 vivado-mcp 离线查询 VCD 波形,定位复位、X/Z、信号变化和握手问题;需要新证据时从已选 XSim 仿真导出有限窗口,不把波形查询当测试判定。

    148 GitHub stars~588 tokensUpdated 19 days ago
    Auto-check passed

Categories

Questions about Vivado Project Bringup

What does Vivado Project Bringup do?

接管或建立 Vivado FPGA 工程,核对源文件、约束、顶层和构建状态,通过 vivado-mcp 完成请求范围内的综合、实现和产物检查。. Vivado Project Bringup is an agent skill from mapleleavessssssss-wq/vivado-mcp.

When should I use Vivado Project Bringup?

Vivado Project Bringup fits situations like: tasks that involve MCP servers.

How do I install Vivado Project Bringup in Claude Code?

Run `npx skills add mapleleavessssssss-wq/vivado-mcp --skill vivado-project-bringup -a claude-code`. Or copy the skill folder (skills/vivado-project-bringup in mapleleavessssssss-wq/vivado-mcp) into .claude/skills/vivado-project-bringup in your project. Claude Code loads it when a task matches its description.

How do I install Vivado Project Bringup in Codex?

Run `npx skills add mapleleavessssssss-wq/vivado-mcp --skill vivado-project-bringup -a codex`. Or copy the skill folder (skills/vivado-project-bringup in mapleleavessssssss-wq/vivado-mcp) into .agents/skills/vivado-project-bringup in your project. Codex loads it when a task matches its description.

Can I use Vivado Project Bringup 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-project-bringup -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-project-bringup, .gemini/skills/vivado-project-bringup, .github/skills/vivado-project-bringup and .opencode/skills/vivado-project-bringup in your project.

What does Vivado Project Bringup need to run?

SKILL.md names no scripts, command-line tools or credentials: Vivado Project Bringup is instructions for the agent only. Our summary lists: Python 3.

Does Vivado Project Bringup 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 Project Bringup 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 Project Bringup use?

Vivado Project Bringup 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 Project Bringup use?

About 571 tokens (SKILL.md is roughly 2.3k 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 Project Bringup?

Skills that share tags, products or a category with Vivado Project Bringup: 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 Project Bringup?

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.