菜单
Write a new LEAPP artifact module, or substantially rework an existing one. Use when adding support for an app or data source in iLEAPP, ALEAPP, RLEAPP, VLEAPP or DLEAPP, when asked to "add an artifact" or "parse <app>", or when a module needs new output types, media or a conversation view.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/abrignoni/iLEAPP --skill leapp-new-artifact命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Wire up how an artifact renders in LAVA, end to end across the producer and the viewer. Use when adding a conversation view to an artifact, when a view renders wrong or not at all, when adding a field to the LAVA schema or manifest, or when asked to "add a module to the LAVA schema".
Run a LEAPP tool end to end against a real extraction to validate artifact changes and produce a handoff. Use when verifying new or changed artifacts before a PR, when asked to "run it against a real image" or "check the report", or when confirming recorded sample_data row counts.
After fixing an artifact in one LEAPP core, find and fix the same defect in the sibling cores. Use when a fix has just landed or is about to, when asked to "level" a change across cores, or when checking whether a defect found in one tool exists in the others.
基于 SOC 职业分类
正在显示 SKILL.md
| name | leapp-new-artifact |
| description | Write a new LEAPP artifact module, or substantially rework an existing one. Use when adding support for an app or data source in iLEAPP, ALEAPP, RLEAPP, VLEAPP or DLEAPP, when asked to "add an artifact" or "parse <app>", or when a module needs new output types, media or a conversation view. |
admin/docs/artifact_info_block.md in the iLEAPP repo is the authority on every field of
the __artifacts_v2__ block. Read it first. This skill is the order of operations around it.
Locate the app's files in a real extraction and confirm what is actually there. Do not start from the app's documentation or from another tool's output.
Open the database or file read-only and look at the schema. Note which tables carry timestamps, which carry identifiers, and which are empty in your sample. An empty table in one image is not evidence the feature is unused.
Grep the other cores for the same app name and bundle or package identifier. If a copy
exists, read it. You may be fixing a known problem, or inheriting one. See the
leapp-cross-core rule.
One file under scripts/artifacts/. The key in __artifacts_v2__ must exactly match the
processing function's name, or the loader will not associate them.
Get these right, because they are the ones most often wrong:
paths is fnmatch, not glob. * crosses /. Matching is case-sensitive off
Windows. See the leapp-artifact-paths rule and validate before committing.author is unversioned: @YourHandle, or @YourHandle, Claude if an agent helped.description and notes are examiner-facing and reach the report and the LAVA
manifest. Say only what the data proves. See the leapp-claims rule.output_types: "standard" for the usual fan-out, "all" to add KML when the
artifact has coordinates, "lava_only" for a producer another module reads.open_sqlite_db_readonly(), and
attach_sqlite_db_readonly() if you attach. See the leapp-evidence-readonly rule.If the app has attachments, surface the media itself rather than its filename. See the
lava-media rule.
A module that imports cleanly has not been tested. Run the tool against an extraction that contains the app and confirm the row count, the column alignment, and that timestamps land in the right column with the right epoch.
Build a focused profile containing only the artifacts you changed so the run is fast.
Record what you verified in sample_data as "<corpus key>": "<OS> <ver> | <n> rows".
Record zero-row corpora too: that a corpus was checked and had none is useful.
name values are rejected at load and nothing
else catches it.leapp-ci rule.