write-func-as-yaml
Write function analysis results as YAML file beside the binary using IDA Pro MCP. Use this skill after completing function identification and signature generation to persist the results in a standardized YAML format. For virtual functions with known vtable index, use write-vfunc-as-yaml instead.
v2026.11.13-dcf20203 installs+3 in 7 days67 StarsMITsynced 12 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install hlnd2t/write-func-as-yamlWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package6c0be4fb…956585a5
6c0be4fb5505…fcd5956585a51 file · 2.0 KBScanLowno findings
Sourcegithub.com/HLND2T/CS2_VibeSignatures/tree/main/.claude/skills/write-func-as-yaml@dcf2020
On this page
Persist function analysis results to a YAML file beside the binary using IDA Pro MCP.
Prerequisites
Before using this skill, you should have:
- Identified and renamed the target function
- Generated a unique signature using
/generate-signature-for-function - An IDA Pro MCP session, resolved per mcp-ida-session.md:
idb_list→idb_open(script fallback only if the endpoint is unreachable). Honor its IDB save discipline — an idle-TTL self-exit does not save.
Required Parameters
| Parameter | Description | Example |
|---|---|---|
func_name |
Name of the function | CBaseModelEntity_SetModel |
func_addr |
Virtual address of the function | 0x180A8CA10 |
func_sig |
Unique byte signature | 41 B8 80 00 00 00 48 8D 99 10 05 00 00 |
Method
An optional artifact_name selects the stable filename stem independently of
func_name. Honor the corresponding preprocessor's OUTPUT_NAME_MAP when
present: use its key for artifact_name and value for the semantic func_name.
mcp__ida-pro-mcp__py_eval code="""
import idaapi
import os
import yaml
# === REQUIRED: Replace these values ===
func_name = "<func_name>" # e.g., "CBaseModelEntity_SetModel"
artifact_name = func_name # Override with the caller's expected artifact stem if different.
func_addr = <func_addr> # e.g., 0x180A8CA10
func_sig = "<func_sig>" # e.g., "41 B8 80 00 00 00"
# ======================================
# Get function size
func = idaapi.get_func(func_addr)
func_size = func.size() if func else 0
# Get binary path and determine platform
input_file = idaapi.get_input_file_path()
dir_path = os.environ.get('CS2VIBE_ARTIFACT_DIR') or os.path.dirname(input_file)
if input_file.endswith('.dll'):
platform = 'windows'
image_base = idaapi.get_imagebase()
else:
platform = 'linux'
image_base = 0x0
func_rva = func_addr - image_base
data = {
'func_name': func_name,
'func_va': hex(func_addr),
'func_rva': hex(func_rva),
'func_size': hex(func_size),
'func_sig': func_sig,
}
yaml_path = os.path.join(dir_path, f"{artifact_name}.{platform}.yaml")
with open(yaml_path, 'w', encoding='utf-8') as f:
yaml.dump(data, f, default_flow_style=False, sort_keys=False)
print(f"Written to: {yaml_path}")
"""Output File Naming Convention
The output YAML filename follows this pattern:
<artifact_name>.<platform>.yaml(defaults tofunc_name)
Examples:
server.dll→CBaseModelEntity_SetModel.windows.yamllibserver.so/libserver.so→CBaseModelEntity_SetModel.linux.yamlengine2.dll→CServerSideClient_IsHearingClient.windows.yamllibengine2.so→CServerSideClient_IsHearingClient.linux.yaml
Output YAML Format
func_name: CBaseModelEntity_SetModel
func_va: 0x180A8CA10 # Virtual address - changes with game updates
func_rva: 0xA8CA10 # Relative virtual address (VA - image base) - changes with game updates
func_size: 0x3F # Function size in bytes - changes with game updates
func_sig: 41 B8 80 00 00 00 48 8D 99 10 05 00 00 # Unique byte signaturePlatform Detection
The skill automatically detects the platform based on file extension:
.dll→ Windows (usesidaapi.get_imagebase()for image base).so→ Linux (uses0x0as image base)
Trusted finalization
This writer produces a semantic YAML payload at the caller-provided expected artifact path. It does not own final field ordering, scalar spelling, encoding, or line endings. After runtime validation, the trusted analyzer rewrites every successful preprocessor or Agent output through the Source2 central canonicalizer; that canonical rewrite is the only byte-level trust boundary.
Notes
- All values marked "changes with game updates" should be regenerated when analyzing new binary versions
- The YAML file is written to the same directory as the input binary
- func_size is automatically calculated from IDA's function analysis
- func_rva is automatically calculated as
func_va - image_base - For virtual functions with vtable information, use
/write-vfunc-as-yamlinstead
Files in this version
- SKILL.md4.5 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | Yes | Yes |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | Yes | Yes |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-dcf2020 | Nov 13, 2026 | dcf2020 | 6c0be4fb | Signed | – |
More from HLND2T
All from this publisherMore in Reverse engineering and fuzzing
See the categoryAsk anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login