[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BJSGT9AYW9FDWRSZ9WHQ0E":3,"skill-same:01M7BJSGT9AYW9FDWRSZ9WHQ0E":45},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7BJSGT9AYW9FDWRSZ9WHQ0E","maven-build-lifecycle",null,"Use when reproducing and repairing Maven CI build failures, especially legacy multi-module builds and Maven Invoker integration tests.","linyouxue\u002Fskill-repair-benchmark","linyouxue","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F216151464?v=4","01M7BJEVCXKD74KH6FG9CBVSQB","林宥学","01M7BJEVE02NP217V93BKZFC0J",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fcontrolled-skill-repair-experiments\u002Fresult\u002Fmmg2skill-gpt5.2-xhigh\u002Fcandidates\u002Fsingle-fix-build-google-auto-RI-002\u002Fround-2\u002Fskills\u002Fmaven-build-lifecycle\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: maven-build-lifecycle\ndescription: Use when reproducing and repairing Maven CI build failures, especially legacy multi-module builds and Maven Invoker integration tests.\n---\n\n# Maven Build Lifecycle — Legacy CI Repair Workflow\n\n## Core rule: reproduce the target CI before changing the project\n\nFor build-repair tasks, the first successful local command is not enough. The\nfailure must be reproduced under the toolchain and Maven command used by the\ntarget CI. Read the repository's CI configuration (`.travis.yml`, workflow\nfiles, wrapper scripts, build POMs) before interpreting any compiler or\ndependency error.\n\nRecord at least:\n\n```bash\njava -version\njavac -version\nmvn -version\n```\n\nIf the repository declares a historical JDK and the container's default Java\nis newer, switch to the declared JDK *before* patching project files. A failure\ncaused only by running an old project on a modern JDK is not evidence that the\nproject should be migrated.\n\nFor environments that provide the BugSwarm JDK switcher, a Travis build that\npins an older JDK can be reproduced with (example for JDK 7):\n\n```bash\nsource \u002Fopt\u002Fjdk_switcher\u002Fjdk_switcher.sh\njdk_switcher use openjdk7\nexport TRAVIS_JDK_VERSION=openjdk7\njava -version\n```\n\nThen run the exact CI build command, including any non-default reactor POM:\n\n```bash\nmvn -Dhttps.protocols=TLSv1.2 -B -U -f build-pom.xml verify \\\n  --fail-at-end -Dsource.skip=true -Dmaven.javadoc.skip=true\n```\n\n### Maven Invoker \u002F nested test projects: fix the template POMs, not generated copies\n\nIf the build fails while running Maven Invoker (or any integration test that\nbuilds “nested projects”), treat those nested projects as **real builds with\ntheir own dependency resolution**:\n\n- Identify where the nested projects are sourced from (commonly `src\u002Fit\u002F**`,\n  `src\u002Ftest\u002Fresources\u002F**`, or a dedicated `it\u002F` directory).\n- Identify the failing nested project directory from the Maven output (Invoker\n  commonly runs builds under `target\u002F**`). Then map it back to the **source\n  template** under the repository (e.g., `src\u002Fit\u002F\u003Ccase>\u002Fpom.xml`).\n- Apply dependency\u002Fplugin\u002Fversion fixes to the **source templates** under the\n  repository, not to generated directories under `target\u002F**` (those will be\n  recreated on every run).\n- Before deciding “fix root POM vs nested POM”, inspect the nested project’s\n  `pom.xml` parent chain:\n  - If the nested `pom.xml` **does not inherit** the reactor’s\n    `dependencyManagement\u002FpluginManagement` (no parent relationship to your\n    reactor POM), then fixes must live in the nested template `pom.xml` (or a\n    parent POM *within that template project*), because the invoker build won’t\n    see reactor-managed versions.\n  - If the nested `pom.xml` **does inherit** from a parent POM in the\n    repository, apply fixes to the parent so the nested project resolves the\n    change naturally.\n- If invoker projects fail to resolve artifacts, distinguish **plugin**\n  resolution failures vs normal dependency failures; nested builds may require\n  their own plugin versions\u002Frepositories if they don’t inherit yours.\n\n### Do not modernize away historical-JDK symptoms\n\nWhen CI declares an old JDK (e.g., JDK 7), do **not** respond to a default-JDK-11\nfailure by blindly doing any of the following:\n\n- changing Java source\u002Ftarget solely to make the project compile on Java 11;\n- removing or excluding `com.sun:tools` \u002F `tools.jar` solely because Java 9+\n  no longer ships it;\n- adding replacement annotation APIs solely for `javax.annotation.Generated`;\n- changing production logic because javac's post-Java-8 module model produces\n  different compiler-element behavior.\n\nFirst reproduce on the declared JDK. Only errors that remain under the target\nCI environment should drive the repair. (Conversely, if CI is already on Java 9+,\nthen `tools.jar`\u002Fsystem-scope issues are genuine build breakages to fix.)\n\n## Build-repair artifact contract (must satisfy for evaluation)\n\nThis benchmark requires both a diagnosis artifact and an applicable patch.\nCreate these artifacts early (immediately after you have a reproducible failure),\nnot at the end.\n\n1. Write a non-empty diagnosis + plan to:\n   `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt`\n2. Create at least one non-empty unified diff at:\n   `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\u002Fpatch_1.diff`\n   (increment `patch_{i}.diff` if you need multiple patches)\n   - Prefer generating patches via `git diff > patch_1.diff` so you don’t have to\n     hand-author multi-line diff content.\n3. Ensure the repository working tree actually reflects the patch (not only the\n   patch artifact):\n   - verify with `git status` and `git diff --stat`\n   - if you generated the patch from local edits, prove the patch is usable by\n     resetting tracked files and re-applying it:\n     `git checkout -- .` (or `git reset --hard`) then `git apply patch_1.diff`\n4. Re-run the exact CI verification command (same JDK, same Maven flags, same\n   reactor POM) until it succeeds, including any Maven Invoker integration tests.\n\n## Minimal diagnostic sequence (run each command separately)\n\nThe execution tool in this environment may reject multi-line \u002F multi-command\nblocks; run commands one-at-a-time.\n\n1. Locate and enter the repository’s concrete `\u003Crepo>\u002F\u003Cid>` directory under\n   `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed` (do **not** stop at the org\u002Fnamespace or repo\n   directory; you must reach the final build workspace that contains the POMs):\n   ```bash\n   cd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\n   ```\n   ```bash\n   ls -la\n   ```\n   ```bash\n   ls -la \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Cnamespace-or-owner>\n   ```\n   ```bash\n   ls -la \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Cnamespace-or-owner>\u002F\u003Crepo-name>\n   ```\n   ```bash\n   cd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Cnamespace-or-owner>\u002F\u003Crepo-name>\u002F\u003Cid>\n   ```\n   ```bash\n   pwd\n   ```\n   ```bash\n   ls -la\n   ```\n   (Confirm you’re in the right place by seeing project files such as `.travis.yml`,\n   `pom.xml`, `mvnw`, or module directories.)\n\n2. Inspect CI config to find the real build command and JDK:\n   ```bash\n   sed -n '1,220p' .travis.yml\n   ```\n\n3. Record tool versions (paste these into `failed_reasons.txt`):\n   ```bash\n   java -version\n   ```\n   ```bash\n   javac -version\n   ```\n   ```bash\n   mvn -version\n   ```\n\n4. Reproduce the failure with the CI command. If the environment is offline or\n   dependencies are expected to come from the local cache, also try an offline\n   run to get actionable “missing artifact\u002Fplugin” coordinates:\n   ```bash\n   mvn -o -B -e verify --fail-at-end\n   ```\n\n5. Locate the source of the error:\n   - For missing artifact\u002Fplugin coordinates: check whether it’s a **build plugin**\n     resolution issue vs a normal dependency issue (plugins resolve too).\n   - For “file not found” \u002F `systemPath` breakage: grep the repository for the\n     failing coordinate\u002Fpath string (e.g., `tools.jar`).\n   - If you suspect offline-cache gaps, confirm what is and isn’t present under\n     `~\u002F.m2\u002Frepository\u002F` to narrow the failure.\n   - If the failure happens in a nested\u002FInvoker build under `target\u002F**`, locate\n     the corresponding source template project under `src\u002Fit\u002F**` (or equivalent)\n     and plan to modify that template, not the generated copy.\n\n6. Immediately write\u002Fupdate the required diagnosis+plan file (do this before you\n   start editing files for the fix):\n   - Use a one-liner write so you don’t need multi-line shell blocks:\n     ```bash\n     printf '%s\\n' \\\n       \"Repro command: \u003Cpaste exact mvn command>\" \\\n       \"Observed failure: \u003Cpaste key Maven error lines>\" \\\n       \"Root cause guess: \u003Ccode vs build config?>\" \\\n       \"Plan: \u003Cfiles to change + why>\" \\\n       > \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt\n     ```\n   - Verify it exists and is non-empty:\n     ```bash\n     test -s \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt && echo \"notes ok\"\n     ```\n\n## General Maven lifecycle reminders\n\n- `mvn test` does not imply that `mvn verify` passes. `verify` can execute\n  integration-test and Invoker steps that `test` never reaches.\n- A green command run under the wrong JDK is not sufficient evidence of a\n  valid CI repair.\n","# Maven Build Lifecycle — Legacy CI Repair Workflow\n\n## Core rule: reproduce the target CI before changing the project\n\nFor build-repair tasks, the first successful local command is not enough. The\nfailure must be reproduced under the toolchain and Maven command used by the\ntarget CI. Read the repository's CI configuration (`.travis.yml`, workflow\nfiles, wrapper scripts, build POMs) before interpreting any compiler or\ndependency error.\n\nRecord at least:\n\n```bash\njava -version\njavac -version\nmvn -version\n```\n\nIf the repository declares a historical JDK and the container's default Java\nis newer, switch to the declared JDK *before* patching project files. A failure\ncaused only by running an old project on a modern JDK is not evidence that the\nproject should be migrated.\n\nFor environments that provide the BugSwarm JDK switcher, a Travis build that\npins an older JDK can be reproduced with (example for JDK 7):\n\n```bash\nsource \u002Fopt\u002Fjdk_switcher\u002Fjdk_switcher.sh\njdk_switcher use openjdk7\nexport TRAVIS_JDK_VERSION=openjdk7\njava -version\n```\n\nThen run the exact CI build command, including any non-default reactor POM:\n\n```bash\nmvn -Dhttps.protocols=TLSv1.2 -B -U -f build-pom.xml verify \\\n  --fail-at-end -Dsource.skip=true -Dmaven.javadoc.skip=true\n```\n\n### Maven Invoker \u002F nested test projects: fix the template POMs, not generated copies\n\nIf the build fails while running Maven Invoker (or any integration test that\nbuilds “nested projects”), treat those nested projects as **real builds with\ntheir own dependency resolution**:\n\n- Identify where the nested projects are sourced from (commonly `src\u002Fit\u002F**`,\n  `src\u002Ftest\u002Fresources\u002F**`, or a dedicated `it\u002F` directory).\n- Identify the failing nested project directory from the Maven output (Invoker\n  commonly runs builds under `target\u002F**`). Then map it back to the **source\n  template** under the repository (e.g., `src\u002Fit\u002F\u003Ccase>\u002Fpom.xml`).\n- Apply dependency\u002Fplugin\u002Fversion fixes to the **source templates** under the\n  repository, not to generated directories under `target\u002F**` (those will be\n  recreated on every run).\n- Before deciding “fix root POM vs nested POM”, inspect the nested project’s\n  `pom.xml` parent chain:\n  - If the nested `pom.xml` **does not inherit** the reactor’s\n    `dependencyManagement\u002FpluginManagement` (no parent relationship to your\n    reactor POM), then fixes must live in the nested template `pom.xml` (or a\n    parent POM *within that template project*), because the invoker build won’t\n    see reactor-managed versions.\n  - If the nested `pom.xml` **does inherit** from a parent POM in the\n    repository, apply fixes to the parent so the nested project resolves the\n    change naturally.\n- If invoker projects fail to resolve artifacts, distinguish **plugin**\n  resolution failures vs normal dependency failures; nested builds may require\n  their own plugin versions\u002Frepositories if they don’t inherit yours.\n\n### Do not modernize away historical-JDK symptoms\n\nWhen CI declares an old JDK (e.g., JDK 7), do **not** respond to a default-JDK-11\nfailure by blindly doing any of the following:\n\n- changing Java source\u002Ftarget solely to make the project compile on Java 11;\n- removing or excluding `com.sun:tools` \u002F `tools.jar` solely because Java 9+\n  no longer ships it;\n- adding replacement annotation APIs solely for `javax.annotation.Generated`;\n- changing production logic because javac's post-Java-8 module model produces\n  different compiler-element behavior.\n\nFirst reproduce on the declared JDK. Only errors that remain under the target\nCI environment should drive the repair. (Conversely, if CI is already on Java 9+,\nthen `tools.jar`\u002Fsystem-scope issues are genuine build breakages to fix.)\n\n## Build-repair artifact contract (must satisfy for evaluation)\n\nThis benchmark requires both a diagnosis artifact and an applicable patch.\nCreate these artifacts early (immediately after you have a reproducible failure),\nnot at the end.\n\n1. Write a non-empty diagnosis + plan to:\n   `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt`\n2. Create at least one non-empty unified diff at:\n   `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\u002Fpatch_1.diff`\n   (increment `patch_{i}.diff` if you need multiple patches)\n   - Prefer generating patches via `git diff > patch_1.diff` so you don’t have to\n     hand-author multi-line diff content.\n3. Ensure the repository working tree actually reflects the patch (not only the\n   patch artifact):\n   - verify with `git status` and `git diff --stat`\n   - if you generated the patch from local edits, prove the patch is usable by\n     resetting tracked files and re-applying it:\n     `git checkout -- .` (or `git reset --hard`) then `git apply patch_1.diff`\n4. Re-run the exact CI verification command (same JDK, same Maven flags, same\n   reactor POM) until it succeeds, including any Maven Invoker integration tests.\n\n## Minimal diagnostic sequence (run each command separately)\n\nThe execution tool in this environment may reject multi-line \u002F multi-command\nblocks; run commands one-at-a-time.\n\n1. Locate and enter the repository’s concrete `\u003Crepo>\u002F\u003Cid>` directory under\n   `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed` (do **not** stop at the org\u002Fnamespace or repo\n   directory; you must reach the final build workspace that contains the POMs):\n   ```bash\n   cd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\n   ```\n   ```bash\n   ls -la\n   ```\n   ```bash\n   ls -la \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Cnamespace-or-owner>\n   ```\n   ```bash\n   ls -la \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Cnamespace-or-owner>\u002F\u003Crepo-name>\n   ```\n   ```bash\n   cd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Cnamespace-or-owner>\u002F\u003Crepo-name>\u002F\u003Cid>\n   ```\n   ```bash\n   pwd\n   ```\n   ```bash\n   ls -la\n   ```\n   (Confirm you’re in the right place by seeing project files such as `.travis.yml`,\n   `pom.xml`, `mvnw`, or module directories.)\n\n2. Inspect CI config to find the real build command and JDK:\n   ```bash\n   sed -n '1,220p' .travis.yml\n   ```\n\n3. Record tool versions (paste these into `failed_reasons.txt`):\n   ```bash\n   java -version\n   ```\n   ```bash\n   javac -version\n   ```\n   ```bash\n   mvn -version\n   ```\n\n4. Reproduce the failure with the CI command. If the environment is offline or\n   dependencies are expected to come from the local cache, also try an offline\n   run to get actionable “missing artifact\u002Fplugin” coordinates:\n   ```bash\n   mvn -o -B -e verify --fail-at-end\n   ```\n\n5. Locate the source of the error:\n   - For missing artifact\u002Fplugin coordinates: check whether it’s a **build plugin**\n     resolution issue vs a normal dependency issue (plugins resolve too).\n   - For “file not found” \u002F `systemPath` breakage: grep the repository for the\n     failing coordinate\u002Fpath string (e.g., `tools.jar`).\n   - If you suspect offline-cache gaps, confirm what is and isn’t present under\n     `~\u002F.m2\u002Frepository\u002F` to narrow the failure.\n   - If the failure happens in a nested\u002FInvoker build under `target\u002F**`, locate\n     the corresponding source template project under `src\u002Fit\u002F**` (or equivalent)\n     and plan to modify that template, not the generated copy.\n\n6. Immediately write\u002Fupdate the required diagnosis+plan file (do this before you\n   start editing files for the fix):\n   - Use a one-liner write so you don’t need multi-line shell blocks:\n     ```bash\n     printf '%s\\n' \\\n       \"Repro command: \u003Cpaste exact mvn command>\" \\\n       \"Observed failure: \u003Cpaste key Maven error lines>\" \\\n       \"Root cause guess: \u003Ccode vs build config?>\" \\\n       \"Plan: \u003Cfiles to change + why>\" \\\n       > \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt\n     ```\n   - Verify it exists and is non-empty:\n     ```bash\n     test -s \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt && echo \"notes ok\"\n     ```\n\n## General Maven lifecycle reminders\n\n- `mvn test` does not imply that `mvn verify` passes. `verify` can execute\n  integration-test and Invoker steps that `test` never reaches.\n- A green command run under the wrong JDK is not sufficient evidence of a\n  valid CI repair.\n",{"name":5,"description":7},"main","cdcb6d230f3b15c3c33f8a2bdd16439f43602cbe","controlled-skill-repair-experiments\u002Fresult\u002Fmmg2skill-gpt5.2-xhigh\u002Fcandidates\u002Fsingle-fix-build-google-auto-RI-002\u002Fround-2\u002Fskills\u002Fmaven-build-lifecycle",1,"https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark","https:\u002F\u002Fgithub.com\u002Flinyouxue","2026-11-14 20:28:35",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add linyouxue\u002Fskill-repair-benchmark --skill maven-build-lifecycle",{"tool":37,"command":38},"bunx","bunx skills add linyouxue\u002Fskill-repair-benchmark --skill maven-build-lifecycle",{"tool":40,"command":41},"pnpm","pnpm dlx skills add linyouxue\u002Fskill-repair-benchmark --skill maven-build-lifecycle","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fcontrolled-skill-repair-experiments\u002Fresult\u002Fmmg2skill-gpt5.2-xhigh\u002Fcandidates\u002Fsingle-fix-build-google-auto-RI-002\u002Fround-2\u002Fskills\u002Fmaven-build-lifecycle\u002FSKILL.md",true,[],[46,53,60,67,72,77],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7E1HGVRY73NBJ022CJG13X6","video-frame-extraction","Extract frames from video files and save them as images using OpenCV","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_03\u002Finputs\u002Fskills\u002Fvideo-frame-extraction\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7E1HAG5R7CJ9C8NYJS771MB","openai-vision","Analyze images and multi-frame sequences using OpenAI GPT vision models","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_03\u002Finputs\u002Fskills\u002Fopenai-vision\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7E1H7DADKB6QBWKC2KQ63SZ","image-ocr","Extract text content from images using Tesseract OCR via Python, including structured field extraction from receipts and forms","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_03\u002Finputs\u002Fskills\u002Fimage-ocr\u002FSKILL.md",[],[],{"skillNo":68,"name":48,"nameZh":6,"description":49,"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},"01M7E1H0WBNT43TENGQY7AVZHD","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_02\u002Finputs\u002Fskills\u002Fvideo-frame-extraction\u002FSKILL.md",[],[],{"skillNo":73,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7E1GTC7D4N4Q2EF03875J9E","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_02\u002Finputs\u002Fskills\u002Fopenai-vision\u002FSKILL.md",[],[],{"skillNo":78,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7E1GQ92CWFMGH53KSSE4WER","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_02\u002Finputs\u002Fskills\u002Fimage-ocr\u002FSKILL.md",[],[]]