[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BP6MZKDP5MBTGJAYRW3ESG":3,"skill-same:01M7BP6MZKDP5MBTGJAYRW3ESG":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},"01M7BP6MZKDP5MBTGJAYRW3ESG","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\u002Fwml-claude4.7\u002Fexperiments\u002Frepair\u002Fsingle-fix-build-google-auto-RI-002\u002Frun\u002Finputs\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 JDK 7 Travis build\ncan be reproduced with:\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### Do not modernize away historical-JDK symptoms\n\nWhen CI declares JDK 7, do **not** respond to a default-JDK-11 failure by\nblindly 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.\n\n## Classifying the failure locus: parent reactor vs nested Invoker child\n\nBefore proposing any edit, decide whether the failure surfaces in the main\nreactor module or inside a nested build driven by `maven-invoker-plugin`\n(a common pattern for annotation-processor projects such as AutoValue \u002F\nAutoService, where `src\u002Fit\u002F\u003Ccase>\u002F` holds self-contained Maven test projects\nthat the parent build invokes). The patch target depends entirely on this\nclassification, and getting it wrong wastes the repair budget on the wrong\nfile.\n\n### How to detect a nested Invoker failure\n\nIn the CI log, look for any of the following signals:\n\n- `[INFO] Building: \u003Ccase>\u002Fpom.xml` emitted by `maven-invoker-plugin` (as\n  opposed to the standard reactor banner `[INFO] Building \u003Cartifact> \u003Cver>`);\n- a `BUILD FAILURE` whose stack trace or `BUILD LOG` section references a path\n  under `src\u002Fit\u002F\u003Ccase>\u002F` or under `target\u002Fit\u002F\u003Ccase>\u002F`;\n- goal `invoker:install`, `invoker:integration-test`, or `invoker:verify`\n  being the step that reports the failure;\n- a message pointing at a `build.log` file inside the invoked project\n  directory, e.g. `target\u002Fit\u002F\u003Ccase>\u002Fbuild.log`.\n\nIn the repository, confirm by inspecting the invoker configuration in the\nfailing module's `pom.xml` (typical keys: `projectsDirectory` — usually\n`src\u002Fit` — `localRepositoryPath` — usually `target\u002Fit-repo` or\n`target\u002Flocal-repo` — and `settingsFile`).\n\n### How the invoked child resolves dependencies\n\nA nested Invoker project is a *separate* Maven build. It does **not**\nautomatically see the parent's `\u003CdependencyManagement>` or `\u003Cdependencies>`.\nIts dependency resolution rules are:\n\n1. The child reads its own `pom.xml` under `src\u002Fit\u002F\u003Ccase>\u002Fpom.xml`\n   (often filtered through `${project.version}` style tokens from the\n   invoker configuration).\n2. The child resolves artifacts from the **invoker-provided local repository**\n   (the `localRepositoryPath` above), which the parent populates during\n   `invoker:install` with the just-built artifacts of the reactor.\n3. Per-case overrides live in `src\u002Fit\u002F\u003Ccase>\u002Finvoker.properties`\n   (e.g. `invoker.goals`, `invoker.mavenOpts`, `invoker.java.version`,\n   `invoker.buildResult`).\n4. Anything the child needs that the parent did not install into the invoker\n   local repo must be declared in the child's own `pom.xml` or injected via\n   `invoker.properties` \u002F the invoker `settingsFile`.\n\nConsequently, a repair for an Invoker-level failure typically edits files\n**inside the nested test project**, not the parent module:\n\n- missing\u002Fincorrect dependency, plugin version, or `\u003Cbuild>` configuration →\n  edit `src\u002Fit\u002F\u003Ccase>\u002Fpom.xml`;\n- wrong goals, JDK gate, or expected outcome → edit\n  `src\u002Fit\u002F\u003Ccase>\u002Finvoker.properties`;\n- missing or outdated expected source\u002Fresource → edit files under\n  `src\u002Fit\u002F\u003Ccase>\u002Fsrc\u002F...`.\n\nOnly edit the parent module when the failure is clearly in the parent build\n(e.g. the artifact installed into the invoker local repo is itself wrong, or\nthe invoker-plugin configuration in the parent `pom.xml` is misdeclared).\n\nThis nested-project triage still runs **under the declared historical JDK**;\nthe JDK switcher step above is a prerequisite, not an alternative.\n\n## Build-repair artifact contract\n\nThis benchmark requires both a diagnosis artifact and an applicable patch.\nBefore finishing:\n\n1. Classify the failure locus using the section above (parent reactor vs\n   nested Invoker child) and record that classification in\n   `failed_reasons.txt`.\n2. Create at least one non-empty standard unified diff at\n   `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\u002Fpatch_1.diff` (use the actual repo\n   path given by the task, e.g. `...\u002Fgoogle\u002Fauto\u002Fpatch_1.diff`). The diff's\n   `a\u002F` and `b\u002F` paths — and the files it actually touches — must correspond\n   to the failing unit:\n   - parent-reactor failure → files under the parent module\n     (`pom.xml`, `src\u002Fmain\u002F...`, `src\u002Ftest\u002F...`, `build-pom.xml`, etc.);\n   - nested Invoker failure → files inside the nested test project\n     (`\u003Cmodule>\u002Fsrc\u002Fit\u002F\u003Ccase>\u002Fpom.xml`,\n     `\u003Cmodule>\u002Fsrc\u002Fit\u002F\u003Ccase>\u002Finvoker.properties`,\n     `\u003Cmodule>\u002Fsrc\u002Fit\u002F\u003Ccase>\u002Fsrc\u002F...`), **not** the parent module by default.\n   Do not default to the repository root just because that is where the diff\n   artifact lives.\n3. Apply that patch to the failed repository.\n4. Check `git diff`\u002F`git status` and ensure the intended project file — at the\n   correct scope identified in step 1, not only the patch artifact — was\n   changed.\n5. Re-run the exact historical CI verification command under the declared JDK\n   (e.g. JDK 7).\n6. Do not finish until the full reactor, including Maven Invoker integration\n   tests, succeeds.\n\n## Minimal diagnostic sequence\n\n```bash\ncd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Fgoogle\u002Fauto\n\n# 1. Establish target CI and toolchain.\nsed -n '1,220p' .travis.yml\nsource \u002Fopt\u002Fjdk_switcher\u002Fjdk_switcher.sh\njdk_switcher use openjdk7\nexport TRAVIS_JDK_VERSION=openjdk7\njava -version\nmvn -version\n\n# 2. Reproduce the real CI command.\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\n### Nested Invoker test projects — targeted diagnostics\n\nWhen the step above fails inside `maven-invoker-plugin`, add:\n\n```bash\n# a. Identify the failing module and inspect its invoker configuration.\ngrep -R --include=pom.xml -n 'maven-invoker-plugin' .\n\n# b. List nested integration-test projects and their per-case overrides.\nls -1 \u003Cmodule>\u002Fsrc\u002Fit\nfind \u003Cmodule>\u002Fsrc\u002Fit -maxdepth 2 -name pom.xml -o -name invoker.properties\n\n# c. Read the invoked child's own build log — this is the authoritative error,\n#    not the parent reactor summary.\nsed -n '1,400p' \u003Cmodule>\u002Ftarget\u002Fit\u002F\u003Ccase>\u002Fbuild.log\n\n# d. Inspect the invoker-provided local repository used by the child build.\nls \u003Cmodule>\u002Ftarget\u002Fit-repo 2>\u002Fdev\u002Fnull || ls \u003Cmodule>\u002Ftarget\u002Flocal-repo 2>\u002Fdev\u002Fnull\n```\n\nUse the child `build.log` to decide whether the fix belongs in the nested\n`pom.xml`, the nested `invoker.properties`, nested sources, or (less often)\nthe parent configuration that installs artifacts into the invoker local repo.\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- A nested Invoker child build has its own POM, its own local repository, and\n  its own effective settings; do not assume the parent reactor's dependency\n  graph covers it.\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 JDK 7 Travis build\ncan be reproduced with:\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### Do not modernize away historical-JDK symptoms\n\nWhen CI declares JDK 7, do **not** respond to a default-JDK-11 failure by\nblindly 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.\n\n## Classifying the failure locus: parent reactor vs nested Invoker child\n\nBefore proposing any edit, decide whether the failure surfaces in the main\nreactor module or inside a nested build driven by `maven-invoker-plugin`\n(a common pattern for annotation-processor projects such as AutoValue \u002F\nAutoService, where `src\u002Fit\u002F\u003Ccase>\u002F` holds self-contained Maven test projects\nthat the parent build invokes). The patch target depends entirely on this\nclassification, and getting it wrong wastes the repair budget on the wrong\nfile.\n\n### How to detect a nested Invoker failure\n\nIn the CI log, look for any of the following signals:\n\n- `[INFO] Building: \u003Ccase>\u002Fpom.xml` emitted by `maven-invoker-plugin` (as\n  opposed to the standard reactor banner `[INFO] Building \u003Cartifact> \u003Cver>`);\n- a `BUILD FAILURE` whose stack trace or `BUILD LOG` section references a path\n  under `src\u002Fit\u002F\u003Ccase>\u002F` or under `target\u002Fit\u002F\u003Ccase>\u002F`;\n- goal `invoker:install`, `invoker:integration-test`, or `invoker:verify`\n  being the step that reports the failure;\n- a message pointing at a `build.log` file inside the invoked project\n  directory, e.g. `target\u002Fit\u002F\u003Ccase>\u002Fbuild.log`.\n\nIn the repository, confirm by inspecting the invoker configuration in the\nfailing module's `pom.xml` (typical keys: `projectsDirectory` — usually\n`src\u002Fit` — `localRepositoryPath` — usually `target\u002Fit-repo` or\n`target\u002Flocal-repo` — and `settingsFile`).\n\n### How the invoked child resolves dependencies\n\nA nested Invoker project is a *separate* Maven build. It does **not**\nautomatically see the parent's `\u003CdependencyManagement>` or `\u003Cdependencies>`.\nIts dependency resolution rules are:\n\n1. The child reads its own `pom.xml` under `src\u002Fit\u002F\u003Ccase>\u002Fpom.xml`\n   (often filtered through `${project.version}` style tokens from the\n   invoker configuration).\n2. The child resolves artifacts from the **invoker-provided local repository**\n   (the `localRepositoryPath` above), which the parent populates during\n   `invoker:install` with the just-built artifacts of the reactor.\n3. Per-case overrides live in `src\u002Fit\u002F\u003Ccase>\u002Finvoker.properties`\n   (e.g. `invoker.goals`, `invoker.mavenOpts`, `invoker.java.version`,\n   `invoker.buildResult`).\n4. Anything the child needs that the parent did not install into the invoker\n   local repo must be declared in the child's own `pom.xml` or injected via\n   `invoker.properties` \u002F the invoker `settingsFile`.\n\nConsequently, a repair for an Invoker-level failure typically edits files\n**inside the nested test project**, not the parent module:\n\n- missing\u002Fincorrect dependency, plugin version, or `\u003Cbuild>` configuration →\n  edit `src\u002Fit\u002F\u003Ccase>\u002Fpom.xml`;\n- wrong goals, JDK gate, or expected outcome → edit\n  `src\u002Fit\u002F\u003Ccase>\u002Finvoker.properties`;\n- missing or outdated expected source\u002Fresource → edit files under\n  `src\u002Fit\u002F\u003Ccase>\u002Fsrc\u002F...`.\n\nOnly edit the parent module when the failure is clearly in the parent build\n(e.g. the artifact installed into the invoker local repo is itself wrong, or\nthe invoker-plugin configuration in the parent `pom.xml` is misdeclared).\n\nThis nested-project triage still runs **under the declared historical JDK**;\nthe JDK switcher step above is a prerequisite, not an alternative.\n\n## Build-repair artifact contract\n\nThis benchmark requires both a diagnosis artifact and an applicable patch.\nBefore finishing:\n\n1. Classify the failure locus using the section above (parent reactor vs\n   nested Invoker child) and record that classification in\n   `failed_reasons.txt`.\n2. Create at least one non-empty standard unified diff at\n   `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\u002Fpatch_1.diff` (use the actual repo\n   path given by the task, e.g. `...\u002Fgoogle\u002Fauto\u002Fpatch_1.diff`). The diff's\n   `a\u002F` and `b\u002F` paths — and the files it actually touches — must correspond\n   to the failing unit:\n   - parent-reactor failure → files under the parent module\n     (`pom.xml`, `src\u002Fmain\u002F...`, `src\u002Ftest\u002F...`, `build-pom.xml`, etc.);\n   - nested Invoker failure → files inside the nested test project\n     (`\u003Cmodule>\u002Fsrc\u002Fit\u002F\u003Ccase>\u002Fpom.xml`,\n     `\u003Cmodule>\u002Fsrc\u002Fit\u002F\u003Ccase>\u002Finvoker.properties`,\n     `\u003Cmodule>\u002Fsrc\u002Fit\u002F\u003Ccase>\u002Fsrc\u002F...`), **not** the parent module by default.\n   Do not default to the repository root just because that is where the diff\n   artifact lives.\n3. Apply that patch to the failed repository.\n4. Check `git diff`\u002F`git status` and ensure the intended project file — at the\n   correct scope identified in step 1, not only the patch artifact — was\n   changed.\n5. Re-run the exact historical CI verification command under the declared JDK\n   (e.g. JDK 7).\n6. Do not finish until the full reactor, including Maven Invoker integration\n   tests, succeeds.\n\n## Minimal diagnostic sequence\n\n```bash\ncd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Fgoogle\u002Fauto\n\n# 1. Establish target CI and toolchain.\nsed -n '1,220p' .travis.yml\nsource \u002Fopt\u002Fjdk_switcher\u002Fjdk_switcher.sh\njdk_switcher use openjdk7\nexport TRAVIS_JDK_VERSION=openjdk7\njava -version\nmvn -version\n\n# 2. Reproduce the real CI command.\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\n### Nested Invoker test projects — targeted diagnostics\n\nWhen the step above fails inside `maven-invoker-plugin`, add:\n\n```bash\n# a. Identify the failing module and inspect its invoker configuration.\ngrep -R --include=pom.xml -n 'maven-invoker-plugin' .\n\n# b. List nested integration-test projects and their per-case overrides.\nls -1 \u003Cmodule>\u002Fsrc\u002Fit\nfind \u003Cmodule>\u002Fsrc\u002Fit -maxdepth 2 -name pom.xml -o -name invoker.properties\n\n# c. Read the invoked child's own build log — this is the authoritative error,\n#    not the parent reactor summary.\nsed -n '1,400p' \u003Cmodule>\u002Ftarget\u002Fit\u002F\u003Ccase>\u002Fbuild.log\n\n# d. Inspect the invoker-provided local repository used by the child build.\nls \u003Cmodule>\u002Ftarget\u002Fit-repo 2>\u002Fdev\u002Fnull || ls \u003Cmodule>\u002Ftarget\u002Flocal-repo 2>\u002Fdev\u002Fnull\n```\n\nUse the child `build.log` to decide whether the fix belongs in the nested\n`pom.xml`, the nested `invoker.properties`, nested sources, or (less often)\nthe parent configuration that installs artifacts into the invoker local repo.\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- A nested Invoker child build has its own POM, its own local repository, and\n  its own effective settings; do not assume the parent reactor's dependency\n  graph covers it.\n\n",{"name":5,"description":7},"main","cdcb6d230f3b15c3c33f8a2bdd16439f43602cbe","controlled-skill-repair-experiments\u002Fresult\u002Fwml-claude4.7\u002Fexperiments\u002Frepair\u002Fsingle-fix-build-google-auto-RI-002\u002Frun\u002Finputs\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\u002Fwml-claude4.7\u002Fexperiments\u002Frepair\u002Fsingle-fix-build-google-auto-RI-002\u002Frun\u002Finputs\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",[],[]]