[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASFSK7S17VSR958DVF3CCH":3,"skill-same:01M7ASFSK7S17VSR958DVF3CCH":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7ASFSK7S17VSR958DVF3CCH","re-android-crypto",null,"Android 加密体系审计（crypto audit）：AndroidKeyStore 密钥体系分析（别名\u002F算法\u002F用途\u002F硬件背书）、 Cipher\u002FKeyInfo 审计、加密调用点 hook（Frida 拦截密钥别名与用途）。 触发词：Keystore、AndroidKeyStore、Cipher、KeyInfo、StrongBox、加密审计、crypto hook、密钥别名。","dslsdzc\u002Frev-skills","dslsdzc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F150430440?v=4","01M7ASEW5AKHWCFR1TXPAXQ237","DslsDZC","01M7ASEW5WJZ3GGBCCT12KHAQZ",243,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fre-android-crypto\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: re-android-crypto\ntype: atomic\ndescription: >\n  Android 加密体系审计（crypto audit）：AndroidKeyStore 密钥体系分析（别名\u002F算法\u002F用途\u002F硬件背书）、\n  Cipher\u002FKeyInfo 审计、加密调用点 hook（Frida 拦截密钥别名与用途）。\n  触发词：Keystore、AndroidKeyStore、Cipher、KeyInfo、StrongBox、加密审计、crypto hook、密钥别名。\ncapabilities: [crypto-identification, key-extraction]\n---\n\n# Android 加密体系审计（crypto audit）\n\n## 任务分类器（intent → 路径）\n\n| 用户目的 | 路径 |\n|---|---|\n| 密钥来自 AndroidKeyStore \u002F 硬件背书密钥 | → **Keystore 审计**（步骤 1） |\n| 定位加密调用点 \u002F 拦截密文与明文 | → **crypto hook**（步骤 2） |\n| 分析第三方加密库（BoringSSL \u002F OpenSSL \u002F Tink \u002F libsodium 等） | → **库分析**（步骤 3） |\n\n## 何时使用 \u002F 何时不用\n\n- 用：Android 应用加密体系审计——密钥体系（Keystore）、加解密调用链、库选型还原\n- 用：`getEncoded()` 不可用的硬件背书密钥（须走审计而非提取密钥字节）\n- 用：加密拦截时需记录密钥别名与用途（不记录密钥字节——安全边界）\n- 不用：JNI\u002Fso 原生逻辑逆向（走 [[re-android-native]]）；通用加密算法识别（走 [[re-crypto-id]]）；通用密钥提取（[[re-crypto-keys]]，Keystore 硬件密钥除外）\n- 不用：非 Android 平台（走通用 crypto 域 [[re-protocol]] 分支）\n- 边界：本技能承接 Android crypto audit 全谱——Keystore\u002FCipher\u002FKeyInfo\u002Fhook 为起点，BoringSSL\u002FOpenSSL\u002FTink\u002Flibsodium 等第三方库分析归入本技能（步骤 3），不塞入 re-android-native\n\n## 工具准备\n\n所有工具先验证再使用。动态 hook 默认沙箱（[[re-analyze\u002Fplatform-tips]] 最高原则）；静态审计可免沙箱。\n\n### frida（[[re-frida]]）—— crypto hook 主力\n\n- 安装与验证见 [[re-frida]] 工具准备；脚本模板见 [[re-frida\u002Ffrida-scripts]]\n- 验证: `frida --version`\n\n### python3 \u002F jadx —— 静态定位加密调用点\n\n- python3 安装与验证见 [[re-python]] 工具准备\n- jadx 安装与验证见 [[re-apk]] 工具准备\n\n### 设备侧命令（[[re-apk]] adb 章节）\n\n- `adb shell` 取应用运行态（KeyStore 枚举需应用进程内执行）\n\n## 操作步骤\n\n1. **Keystore 审计**（AndroidKeyStore 密钥体系）：\n   ```java\n   \u002F\u002F 应用进程内枚举（frida 注入或 jadx 反编译定位调用点）\n   KeyStore ks = KeyStore.getInstance(\"AndroidKeyStore\");\n   ks.load(null);\n   java.util.Enumeration\u003CString> aliases = ks.aliases();\n   ```\n   - **遍历**：`aliases()` 枚举全部条目（密钥别名 = 应用内引用键）\n   - **条目属性**：算法（AES\u002FRSA\u002FEC）、用途（encrypt\u002Fdecrypt\u002Fsign\u002Fverify）、来源——`KeyInfo.getSecurityLevel()`（API 31+，返回 SOFTWARE \u002F TRUSTED_ENVIRONMENT(TEE) \u002F STRONGBOX 三档）；API 23–30 只有 `isInsideSecureHardware()`（布尔，TEE 与 StrongBox 同为 true，分不开）\n   - **生物绑定**：`setUserAuthenticationRequired` 的密钥在认证失败时不可用（绕过与检测见 [[re-analyze\u002Fanti-dynamic-workflow]]）\n   - 产出：别名 → 算法\u002F用途\u002F硬件背书 清单（不记录密钥字节）\n\n2. **crypto hook**（加密调用点拦截）：\n   ```js\n   \u002F\u002F frida：拦截加密调用点，记录算法\u002F模式\u002F密钥别名\n   \u002F\u002F 别名来源：Key 对象本身不携带别名（KeyStore 无 getKeyAlias），须在 getKey 处记录\n   const KeyStore = Java.use('java.security.KeyStore');\n   KeyStore.getKey.overload('java.lang.String', '[C').implementation = function (alias, password) {\n     console.log('KeyStore.getKey', alias);\n     return this.getKey(alias, password);\n   };\n   const Cipher = Java.use('javax.crypto.Cipher');\n   Cipher.init.overload('int', 'java.security.Key', 'java.security.spec.AlgorithmParameterSpec').implementation =\n     function (opmode, key, params) {\n       console.log('Cipher.init', opmode, key.getClass().getName(), params);  \u002F\u002F 对应别名见上方 getKey 输出\n       return this.init(opmode, key, params);\n     };\n   \u002F\u002F 另路取回别名：SecretKeyFactory.getInstance(key.getAlgorithm(), 'AndroidKeyStore')\n   \u002F\u002F   .getKeySpec(key, KeyInfo.class) → KeyInfo.getKeystoreAlias()\n   ```\n   - hook 目标：`Cipher.init` 系列（算法\u002F模式\u002FIV 来源）、`KeyStore.getKey` \u002F `getEntry`（别名与用途）、`Signature`\u002F`Mac` 初始化（验签\u002F校验链）\n   - 记录：别名与用途，**不记录密钥字节**（安全边界，见坑 2）\n   - 静态定位辅助：jadx 搜 `AndroidKeyStore` \u002F `KeyStore.getInstance` \u002F `Cipher.getInstance` 调用点，与 hook 结果互证\n\n3. **第三方加密库分析**（BoringSSL \u002F OpenSSL \u002F Tink \u002F libsodium 等）：\n   - 识别：导入表\u002F符号（`SSL_*`\u002F`EVP_*`\u002F`crypto_*`\u002F`sodium_*` 前缀）+ jadx 依赖声明\n   - 定位调用点：库 API 的 xref（静态）或 hook 库导出函数（动态）\n   - 与 [[re-android-native]] 衔接：库以 .so 形态存在 → 其 JNI\u002F内部逻辑走 [[re-android-native]]，本技能管加密语义（算法\u002F密钥来源\u002F用途）\n\n4. **产出与存证**：密钥体系图（别名\u002F算法\u002F用途\u002F背书来源）+ 加密调用点清单 + hook 脚本，sha256 存档供 [[re-ioc]] 引用\n\n## 跨域联合\n\n- [[re-android-native]]：JNI\u002Fso 原生逻辑逆向（本技能的 .so 库内部逻辑承接方；Keystore 审计自其转出）\n- [[re-frida]]：hook 执行层（[[re-frida\u002Ffrida-scripts]] 模板）\n- [[re-crypto-id]] \u002F [[re-crypto-keys]]：算法识别与通用密钥提取（Keystore 硬件密钥除外——走本技能审计）\n- [[re-apk]]：应用静态定位（jadx 调用点）\n- [[re-mobile]]：工作流移动分支（加密审计子路径）\n\n## 常见坑与陷阱\n\n- **把 Keystore 当普通密钥提取**：现象——`getEncoded()` 拿不到密钥字节，误判「密钥不存在」；原因——AndroidKeyStore 硬件背书密钥不可导出，这是设计而非缺失；对策——改走审计（步骤 1：别名\u002F算法\u002F用途\u002F背书），不追求密钥字节\n- **TEE 与 StrongBox 混为一谈**：现象——`isInsideSecureHardware` 为 true 就断言 StrongBox；原因——Secure Hardware 含 TEE 与 StrongBox 两级，该接口是布尔、分不开（`isStrongBoxBacked` 在 `KeyGenParameterSpec` 上，只管生成侧，`KeyInfo` 没有）；对策——API 31+ 用 `KeyInfo.getSecurityLevel()` 取 SOFTWARE \u002F TEE \u002F STRONGBOX 三档；API 23–30 无法细分，结论按「secure hardware（TEE 或 StrongBox）」标注层级\n- **记录密钥字节**：现象——hook 脚本把 Keystore 密钥内容打印\u002F落盘；原因——把审计当提取，越过安全边界；对策——只记录别名与用途，密钥字节不落盘（见步骤 2 注）\n- **库语义当 JNI 逻辑分析**：现象——第三方加密库的 .so 被按 native 逻辑深挖而忽略加密语义；原因——域不清；对策——库 API 的加密语义（算法\u002F密钥来源\u002F用途）归本技能，内部实现细节才走 [[re-android-native]]\n","# Android 加密体系审计（crypto audit）\n\n## 任务分类器（intent → 路径）\n\n| 用户目的 | 路径 |\n|---|---|\n| 密钥来自 AndroidKeyStore \u002F 硬件背书密钥 | → **Keystore 审计**（步骤 1） |\n| 定位加密调用点 \u002F 拦截密文与明文 | → **crypto hook**（步骤 2） |\n| 分析第三方加密库（BoringSSL \u002F OpenSSL \u002F Tink \u002F libsodium 等） | → **库分析**（步骤 3） |\n\n## 何时使用 \u002F 何时不用\n\n- 用：Android 应用加密体系审计——密钥体系（Keystore）、加解密调用链、库选型还原\n- 用：`getEncoded()` 不可用的硬件背书密钥（须走审计而非提取密钥字节）\n- 用：加密拦截时需记录密钥别名与用途（不记录密钥字节——安全边界）\n- 不用：JNI\u002Fso 原生逻辑逆向（走 [[re-android-native]]）；通用加密算法识别（走 [[re-crypto-id]]）；通用密钥提取（[[re-crypto-keys]]，Keystore 硬件密钥除外）\n- 不用：非 Android 平台（走通用 crypto 域 [[re-protocol]] 分支）\n- 边界：本技能承接 Android crypto audit 全谱——Keystore\u002FCipher\u002FKeyInfo\u002Fhook 为起点，BoringSSL\u002FOpenSSL\u002FTink\u002Flibsodium 等第三方库分析归入本技能（步骤 3），不塞入 re-android-native\n\n## 工具准备\n\n所有工具先验证再使用。动态 hook 默认沙箱（[[re-analyze\u002Fplatform-tips]] 最高原则）；静态审计可免沙箱。\n\n### frida（[[re-frida]]）—— crypto hook 主力\n\n- 安装与验证见 [[re-frida]] 工具准备；脚本模板见 [[re-frida\u002Ffrida-scripts]]\n- 验证: `frida --version`\n\n### python3 \u002F jadx —— 静态定位加密调用点\n\n- python3 安装与验证见 [[re-python]] 工具准备\n- jadx 安装与验证见 [[re-apk]] 工具准备\n\n### 设备侧命令（[[re-apk]] adb 章节）\n\n- `adb shell` 取应用运行态（KeyStore 枚举需应用进程内执行）\n\n## 操作步骤\n\n1. **Keystore 审计**（AndroidKeyStore 密钥体系）：\n   ```java\n   \u002F\u002F 应用进程内枚举（frida 注入或 jadx 反编译定位调用点）\n   KeyStore ks = KeyStore.getInstance(\"AndroidKeyStore\");\n   ks.load(null);\n   java.util.Enumeration\u003CString> aliases = ks.aliases();\n   ```\n   - **遍历**：`aliases()` 枚举全部条目（密钥别名 = 应用内引用键）\n   - **条目属性**：算法（AES\u002FRSA\u002FEC）、用途（encrypt\u002Fdecrypt\u002Fsign\u002Fverify）、来源——`KeyInfo.getSecurityLevel()`（API 31+，返回 SOFTWARE \u002F TRUSTED_ENVIRONMENT(TEE) \u002F STRONGBOX 三档）；API 23–30 只有 `isInsideSecureHardware()`（布尔，TEE 与 StrongBox 同为 true，分不开）\n   - **生物绑定**：`setUserAuthenticationRequired` 的密钥在认证失败时不可用（绕过与检测见 [[re-analyze\u002Fanti-dynamic-workflow]]）\n   - 产出：别名 → 算法\u002F用途\u002F硬件背书 清单（不记录密钥字节）\n\n2. **crypto hook**（加密调用点拦截）：\n   ```js\n   \u002F\u002F frida：拦截加密调用点，记录算法\u002F模式\u002F密钥别名\n   \u002F\u002F 别名来源：Key 对象本身不携带别名（KeyStore 无 getKeyAlias），须在 getKey 处记录\n   const KeyStore = Java.use('java.security.KeyStore');\n   KeyStore.getKey.overload('java.lang.String', '[C').implementation = function (alias, password) {\n     console.log('KeyStore.getKey', alias);\n     return this.getKey(alias, password);\n   };\n   const Cipher = Java.use('javax.crypto.Cipher');\n   Cipher.init.overload('int', 'java.security.Key', 'java.security.spec.AlgorithmParameterSpec').implementation =\n     function (opmode, key, params) {\n       console.log('Cipher.init', opmode, key.getClass().getName(), params);  \u002F\u002F 对应别名见上方 getKey 输出\n       return this.init(opmode, key, params);\n     };\n   \u002F\u002F 另路取回别名：SecretKeyFactory.getInstance(key.getAlgorithm(), 'AndroidKeyStore')\n   \u002F\u002F   .getKeySpec(key, KeyInfo.class) → KeyInfo.getKeystoreAlias()\n   ```\n   - hook 目标：`Cipher.init` 系列（算法\u002F模式\u002FIV 来源）、`KeyStore.getKey` \u002F `getEntry`（别名与用途）、`Signature`\u002F`Mac` 初始化（验签\u002F校验链）\n   - 记录：别名与用途，**不记录密钥字节**（安全边界，见坑 2）\n   - 静态定位辅助：jadx 搜 `AndroidKeyStore` \u002F `KeyStore.getInstance` \u002F `Cipher.getInstance` 调用点，与 hook 结果互证\n\n3. **第三方加密库分析**（BoringSSL \u002F OpenSSL \u002F Tink \u002F libsodium 等）：\n   - 识别：导入表\u002F符号（`SSL_*`\u002F`EVP_*`\u002F`crypto_*`\u002F`sodium_*` 前缀）+ jadx 依赖声明\n   - 定位调用点：库 API 的 xref（静态）或 hook 库导出函数（动态）\n   - 与 [[re-android-native]] 衔接：库以 .so 形态存在 → 其 JNI\u002F内部逻辑走 [[re-android-native]]，本技能管加密语义（算法\u002F密钥来源\u002F用途）\n\n4. **产出与存证**：密钥体系图（别名\u002F算法\u002F用途\u002F背书来源）+ 加密调用点清单 + hook 脚本，sha256 存档供 [[re-ioc]] 引用\n\n## 跨域联合\n\n- [[re-android-native]]：JNI\u002Fso 原生逻辑逆向（本技能的 .so 库内部逻辑承接方；Keystore 审计自其转出）\n- [[re-frida]]：hook 执行层（[[re-frida\u002Ffrida-scripts]] 模板）\n- [[re-crypto-id]] \u002F [[re-crypto-keys]]：算法识别与通用密钥提取（Keystore 硬件密钥除外——走本技能审计）\n- [[re-apk]]：应用静态定位（jadx 调用点）\n- [[re-mobile]]：工作流移动分支（加密审计子路径）\n\n## 常见坑与陷阱\n\n- **把 Keystore 当普通密钥提取**：现象——`getEncoded()` 拿不到密钥字节，误判「密钥不存在」；原因——AndroidKeyStore 硬件背书密钥不可导出，这是设计而非缺失；对策——改走审计（步骤 1：别名\u002F算法\u002F用途\u002F背书），不追求密钥字节\n- **TEE 与 StrongBox 混为一谈**：现象——`isInsideSecureHardware` 为 true 就断言 StrongBox；原因——Secure Hardware 含 TEE 与 StrongBox 两级，该接口是布尔、分不开（`isStrongBoxBacked` 在 `KeyGenParameterSpec` 上，只管生成侧，`KeyInfo` 没有）；对策——API 31+ 用 `KeyInfo.getSecurityLevel()` 取 SOFTWARE \u002F TEE \u002F STRONGBOX 三档；API 23–30 无法细分，结论按「secure hardware（TEE 或 StrongBox）」标注层级\n- **记录密钥字节**：现象——hook 脚本把 Keystore 密钥内容打印\u002F落盘；原因——把审计当提取，越过安全边界；对策——只记录别名与用途，密钥字节不落盘（见步骤 2 注）\n- **库语义当 JNI 逻辑分析**：现象——第三方加密库的 .so 被按 native 逻辑深挖而忽略加密语义；原因——域不清；对策——库 API 的加密语义（算法\u002F密钥来源\u002F用途）归本技能，内部实现细节才走 [[re-android-native]]\n",{"name":5,"type":24,"description":25,"capabilities":26},"atomic","Android 加密体系审计（crypto audit）：AndroidKeyStore 密钥体系分析（别名\u002F算法\u002F用途\u002F硬件背书）、 Cipher\u002FKeyInfo 审计、加密调用点 hook（Frida 拦截密钥别名与用途）。 触发词：Keystore、AndroidKeyStore、Cipher、KeyInfo、StrongBox、加密审计、crypto hook、密钥别名。\n",[27,28],"crypto-identification","key-extraction","main","1977504515d3f5fa8889da43974feb7a0f4eaab9",".claude\u002Fskills\u002Fre-android-crypto",43,"https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills","https:\u002F\u002Fgithub.com\u002Fdslsdzc","Building systems from scratch","2026-10-12 04:15:49",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add dslsdzc\u002Frev-skills --skill re-android-crypto",{"tool":43,"command":44},"bunx","bunx skills add dslsdzc\u002Frev-skills --skill re-android-crypto",{"tool":46,"command":47},"pnpm","pnpm dlx skills add dslsdzc\u002Frev-skills --skill re-android-crypto","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fre-android-crypto\u002FSKILL.md",true,[],[52,59,65,72,79,86],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7AT3SFGN6KTM2DBN8TCNC4K","no-tools","缺工具准备章节。missing tools section.","https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-tools\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7AT3PY0QVB4A4WGAZHY43WP","good-skill","https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgood-skill\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7AT3NJ1PG8DR115AMJC1Q1C","gateway-skill","网关型技能，无工具准备章节。gateway skill.","https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgateway-skill\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7AT3KCJGZV60PKJX244V8Z4","broken-link","含死链接与合法 references 链接。broken link.","https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbroken-link\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7AT3HMVTA2MR66A5FMATVFQ","wrong-name","名字与目录不符。name mismatch.","https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-name\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7AT3F4K5ES6N62092Y8TRNG","bad-frontmatter","https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-frontmatter\u002FSKILL.md",[],[]]