generate-reference-yaml
starsforks
How to install generate-reference-yaml?
hlnd2t/cs2_vibesignatures/generate-reference-yaml
$npx -y skills add HLND2T/CS2_VibeSignatures --skill generate-reference-yamlGenerate reference YAML via project CLI into ida_preprocessor_scripts/references/<module>/<func_name>.<platform>.yaml
SKILL.md
| 1 | # Generate Reference YAML |
| 2 | |
| 3 | Use this skill as the unified backend entrypoint through project CLI. |
| 4 | |
| 5 | Do not call IDA API directly in this skill. Always run `generate_reference_yaml.py`. |
| 6 | |
| 7 | ## Required parameters |
| 8 | |
| 9 | - `func_name` |
| 10 | - `gamever` (Obtain from dll path via ida-pro-mcp if not specified) |
| 11 | - `module` (Obtain from dll path via ida-pro-mcp if not specified) |
| 12 | - `platform` (Obtain from dll path via ida-pro-mcp if not specified) |
| 13 | |
| 14 | ## Command examples |
| 15 | |
| 16 | ### 1) Attach to existing MCP (should be used when there is an existing ida-pro-mcp connection) |
| 17 | |
| 18 | ```bash |
| 19 | uv run generate_reference_yaml.py -gamever 14141 -module engine -platform windows -func_name CNetworkGameClient_RecordEntityBandwidth -mcp_host 127.0.0.1 -mcp_port 13337 |
| 20 | ``` |
| 21 | |
| 22 | ### 2) Auto-start `idalib-mcp` with binary (fallback when no MCP is attached) |
| 23 | |
| 24 | ```bash |
| 25 | # Windows -- always pass -platform windows explicitly |
| 26 | uv run generate_reference_yaml.py -func_name {FUNC_NAME} -auto_start_mcp -binary "bin/{gamever}/{module}/{binary_name}.dll" -platform windows -debug |
| 27 | |
| 28 | # Linux -- always pass -platform linux explicitly |
| 29 | uv run generate_reference_yaml.py -func_name {FUNC_NAME} -auto_start_mcp -binary "bin/{gamever}/{module}/lib{module}.so" -platform linux -debug |
| 30 | ``` |
| 31 | |
| 32 | where `{gamever}` can be obtained from `.env` -> `CS2VIBE_GAMEVER`. |
| 33 | |
| 34 | **IMPORTANT -- Always pass `-platform` explicitly.** While `-platform` can theoretically be inferred from the binary extension (`.dll` -> windows, `.so` -> linux), auto-inference is unreliable and may produce the wrong platform's reference YAML. Always pass `-platform windows` or `-platform linux` explicitly. |
| 35 | |
| 36 | ### 3) Custom output name |
| 37 | |
| 38 | Use `-output_filename` when the reference YAML file name should differ from the default `<func_name>.<platform>.yaml`: |
| 39 | |
| 40 | ```bash |
| 41 | uv run generate_reference_yaml.py -gamever 14141 -module engine -platform windows -func_name CNetworkGameClient_RecordEntityBandwidth -output_filename CNetworkGameClient_RecordEntityBandwidthReference.windows.yaml -mcp_host 127.0.0.1 -mcp_port 13337 |
| 42 | ``` |
| 43 | |
| 44 | `-output_filename` accepts a file name ending in `.yaml`, not a path. The file is still written under `ida_preprocessor_scripts/references/<module>/`. The YAML payload's `func_name` remains the value passed to `-func_name`. |
| 45 | |
| 46 | **IMPORTANT -- Run `generate_reference_yaml.py` sequentially, NOT in parallel.** All invocations share the same IDA MCP connection. Running them in parallel will cause connection conflicts and failures. Run one command at a time, waiting for each to complete before starting the next. |
| 47 | |
| 48 | ## Output path |
| 49 | |
| 50 | - Default: `ida_preprocessor_scripts/references/<module>/<func_name>.<platform>.yaml` |
| 51 | - With `-output_filename <name>.yaml`: `ida_preprocessor_scripts/references/<module>/<name>.yaml` |
| 52 | |
| 53 | ## Manual checks after generation |
| 54 | |
| 55 | 1. `func_va` is credible for current binary/version. |
| 56 | 2. `disasm_code` is non-empty and matches target function semantics. |
| 57 | 3. `procedure` matches expected semantics when available; it can be an empty string when Hex-Rays is unavailable. |
| 58 | 4. `func_name` only confirms the output file targets your requested canonical name; it does not prove address resolution correctness. |
| 59 | |
| 60 | ## `LLM_DECOMPILE` path wiring |
| 61 | |
| 62 | - Generated file path in repository: |
| 63 | - `ida_preprocessor_scripts/references/<module>/<func_name>.<platform>.yaml` |
| 64 | - In target `find-*.py`, when `LLM_DECOMPILE` uses relative paths, write: |
| 65 | - `references/<module>/<func_name>.<platform>.yaml` |
| 66 | - Example tuple: |
| 67 | - `("CNetworkMessages_FindNetworkGroup", "prompt/call_llm_decompile.md", "references/engine/CNetworkGameClient_RecordEntityBandwidth.windows.yaml")` |
People who liked this also viewed
6 picksType
- grill-with-docsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.SkillsJul 2026
- lark-minutes飞书妙记：搜索妙记、查看妙记基础信息、下载/上传音视频、读取或编辑妙记的产物内容、改标题、替换说话人/关键词、申请妙记查看/编辑权限。当给出minute_token、本地音视频文件，要查/改/转妙记产物，或用户明确要主动申请妙记权限时使用；本地音视频转纪要/逐字稿优先走本 skill，不要用 ffmpeg/whisper 本地转写。不负责：获取会议关联妙记，或仅按自然语言标题定位纪要SkillsJul 2026
- lark-markdown飞书 Markdown：查看、创建、上传、编辑和比较 Markdown 文件。当用户需要创建或编辑 Markdown 文件、读取、修改、局部 patch 或比较差异时使用。不负责将 Markdown 导入为飞书在线文档，也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。SkillsJul 2026
- docxUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', SkillsJul 2026
- edit-articleSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- lark-note飞书会议纪要（Note）直查：已知 note_id 时查询纪要详情、展示类型、关联文档 token，并读取 unified 原始逐字记录。当用户已持有 note_id，或从文档显式 vc-node-id 获得 note_id 时使用。不负责会议/日程/妙记定位、文档标题搜索或 Docx 正文读取。SkillsJul 2026
