[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BKV3PDWQPDGFKM6DFRS1M5":3,"skill-same:01M7BKV3PDWQPDGFKM6DFRS1M5":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},"01M7BKV3PDWQPDGFKM6DFRS1M5","maven-build-lifecycle",null,"Use when reproducing and repairing Maven CI build failures (and when the task contract requires failed_reasons.txt + patch_*.diff artifacts).","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\u002Fskillhone-gpt5.2-xhigh\u002Fcandidates\u002Fsingle-fix-build-google-auto-RI-001\u002Fround-5\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 (and when the task contract requires failed_reasons.txt + patch_*.diff artifacts).\n---\n\n# Maven Build Lifecycle — CI Repair Workflow\n\n## SkillHone artifact contract (do this in every run)\n\nThis task family is evaluated on **build success** and on two explicit artifacts. Create them as files (not just as prose in chat).\n\n### Required files\n\n1. **Diagnosis note** (absolute path): `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt`\n2. **One or more patch files** (absolute path, in repo root): `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\u002Fpatch_1.diff` (and `patch_2.diff`, …)\n\n> Replace `\u003Crepo>` and `\u003Cid>` with the values from the task prompt. If you are already `cd`’d into the repo root, writing `patch_1.diff` in the current directory satisfies the required path.\n\n### Quick templates (copy\u002Fpaste)\n\nCreate the diagnosis note **early**, and update it as you learn more:\n\n```bash\nmkdir -p \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\ncat > \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt \u003C\u003C'EOF'\nToolchain\n- java: \u003Cpaste `java -version`>\n- maven: \u003Cpaste `.\u002Fmvnw -v` or `mvn -v`>\n\nReproduction\n- repo: \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\n- command: \u003Cexact mvn command that fails>\n- first failing module\u002FIT project: \u003Cmodule path or src\u002Fit\u002F* path>\n\nFirst real error\n- \u003Cfirst compiler\u002Ftest error line(s)>\n\nRoot cause hypothesis\n- \u003Cwhy it fails>\n\nPlanned fix\n- \u003Cwhat file(s) \u002F pom changes you will make>\nEOF\n```\n\nGenerate a **non-empty** patch file from your changes **in the repo root**.\n\nTwo common ways people accidentally produce an empty\u002Fmissing patch:\n- They run the command from a subdirectory (e.g., inside `src\u002Fit\u002F...`) and save the diff there.\n- They stage changes with `git add`, then use `git diff` (which only shows *unstaged* changes).\n\nUse this robust snippet instead:\n\n```bash\n# From anywhere inside the git repo:\nREPO_ROOT=\"$(git rev-parse --show-toplevel)\"\ncd \"$REPO_ROOT\"\n\n# `git diff HEAD` captures both staged + unstaged changes.\ngit diff --no-color --full-index --binary HEAD > \"$REPO_ROOT\u002Fpatch_1.diff\"\n\ntest -s \"$REPO_ROOT\u002Fpatch_1.diff\"\n```\n\nTo match the task’s “apply the diff” step, ensure the patch applies cleanly **from the repo root**:\n\n```bash\ngit apply --check \"$REPO_ROOT\u002Fpatch_1.diff\"\n\n# If you need to demonstrate application on a clean tree, do it on a clean checkout.\n# Otherwise, it’s enough that the repo already contains the changes represented by the patch.\n```\n\nIf `git apply` fails because the working tree already contains the same edits, don’t throw away the patch.\nEither apply it on a clean tree, or keep your current edits and proceed as long as `patch_*.diff` correctly represents the final change.\n\n## 1) Locate the repo root (don’t guess)\n\n- The task prompt typically gives an exact path like `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>`.\n- `cd` to that directory and confirm it’s the Maven root:\n  - `test -f pom.xml` should succeed.\n\nIf you are unsure where the root POM is, search for it, but avoid picking an unrelated nested `pom.xml` by accident (multi-module repos have many). Prefer the *top-level* one.\n\n## 2) Toolchain selection (Maven + JDK)\n\n### Maven\n\n1. Prefer the Maven Wrapper (`.\u002Fmvnw`) **if present and usable**; it often matches the project’s expected Maven version.\n2. Fall back to system Maven (`mvn`) if the wrapper is missing **or fails to run** (e.g., wrapper download\u002Fnetwork restrictions, missing wrapper JAR, permission issues).\n\nMinimal robust snippet:\n\n```bash\nMVN=mvn\nif [ -f .\u002Fmvnw ]; then\n  MVN=\".\u002Fmvnw\"\n  [ -x .\u002Fmvnw ] || MVN=\"bash .\u002Fmvnw\"\nfi\n\n# Validate the chosen Maven command; if wrapper fails, fall back.\n$MVN -v || { MVN=mvn; mvn -v; }\n```\n\n### JDK\n\nRecord in your note:\n- `java -version`\n- the project’s expected release level (from `pom.xml` and\u002For CI config)\n\nIf you see errors like **\"invalid target release\"**, **\"unsupported class file major version\"**, or bytecode\u002Fversion mismatches:\n\n- Check `pom.xml` for `maven-compiler-plugin` configuration and properties such as:\n  - `maven.compiler.release`, `maven.compiler.source`, `maven.compiler.target`\n- Check CI configuration (e.g., `.travis.yml`, GitHub Actions) for the JDK version.\n- Prefer switching to the expected JDK (e.g., via `JAVA_HOME` \u002F `PATH`) rather than “papering over” the mismatch.\n- If the project uses Maven Toolchains (`maven-toolchains-plugin`), follow that approach instead of ad-hoc environment changes.\n\n## 3) Reproduce the failure the same way CI does\n\n### Use the CI command first\n\n- Mirror CI goals\u002Fprofiles first; then narrow down once you know the first failing module.\n- Find the exact Maven goals and profiles from CI config\u002Flogs (common examples: `test`, `verify`, `-P...`, `-D...`).\n- Always include stack traces for diagnosis:\n  - `-e -DtrimStackTrace=false`\n\nIf the CI command is unknown, start with a reasonable baseline and iterate.\n\nFor **final verification**, prefer `clean verify` because it’s the most common CI target and exercises more of the lifecycle (unit tests, integration tests, and plugins bound to `verify`).\n\n```bash\n# Prefer wrapper if available (see toolchain section)\n\n# Good default (and recommended final check)\n$MVN -e -DtrimStackTrace=false clean verify\n\n# Faster loop when you’re iterating and `verify` is too slow\n$MVN -e -DtrimStackTrace=false clean test\n```\n\n### Narrow down for faster iteration\n\nOnce you know the first failing module, rerun narrowly:\n\n```bash\n# From the repo root, target a single module by artifactId and build its deps.\n$MVN -e -DtrimStackTrace=false -pl :\u003CartifactId> -am test\n```\n\nTip: `-DskipTests` skips running tests but still compiles them; `-Dmaven.test.skip=true` skips compiling tests too. Use these only for *triage*—final verification should match CI\u002Ftask expectations.\n\n## 4) Maven Invoker failures: debug the nested project, not just the reactor\n\n`maven-invoker-plugin` can launch independent Maven builds from integration test projects such as `src\u002Fit\u002F*\u002Fpom.xml`. Those nested builds have their own dependency mediation and can fail even when the parent module's normal unit tests pass.\n\nIf Maven reports output similar to:\n\n```text\nThe following builds failed:\n*  \u003Cit-project>\u002Fpom.xml\n```\n\nthen:\n\n1. Locate the exact integration-test POM named by the Invoker (often under `...\u002Fsrc\u002Fit\u002F\u003Cname>\u002Fpom.xml`).\n2. Read the corresponding Invoker `build.log` and\u002For `invoker-reports` output (commonly under `target\u002Fit\u002F...`).\n3. Identify the *first concrete compiler\u002Ftest error* inside that nested build.\n4. Inspect the nested POM's direct dependencies and resolved versions.\n   - Run `mvn help:effective-pom` and `mvn dependency:tree` inside the nested build directory if needed.\n5. Repair the nested dependency\u002Fconfiguration drift instead of broad-editing unrelated top-level modules.\n\nDo not assume versions declared in the parent reactor automatically govern an Invoker integration-test POM. Some IT POMs are copied or maintained separately and can become stale.\n\n## 5) Dependency-drift signals in nested builds\n\nCommon symptoms that point to nested-build dependency\u002Fversion drift:\n\n- \"cannot find symbol\" for a class\u002Fmethod that exists in newer versions of a library\n- test-only artifacts that are designed to be version-coupled (e.g., `\u003Clib>` and `\u003Clib>-testlib`) resolving to different versions\n- `NoSuchMethodError` \u002F `ClassNotFoundException` during tests even though the main reactor compiles\n\nPrefer aligning versions\u002Fconfiguration in the nested POM (or via a BOM\u002Fimport that the nested POM actually inherits) rather than rewriting valid source code to avoid an API.\n\n## 6) Minimal diagnostic sequence (end-to-end)\n\n```bash\n# 0) Create\u002Fupdate the diagnosis note first\n#    (see the template in the artifact contract section)\n\n# 1) cd to the repo path from the task prompt\ncd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\n\n# 2) Select toolchain\nMVN=mvn\nif [ -f .\u002Fmvnw ]; then\n  MVN=\".\u002Fmvnw\"\n  [ -x .\u002Fmvnw ] || MVN=\"bash .\u002Fmvnw\"\nfi\n$MVN -v || { MVN=mvn; mvn -v; }\njava -version\n\n# 3) Reproduce\n$MVN -e -DtrimStackTrace=false clean test\n\n# 4) After implementing a fix, write a patch file in the repo root\n#    (use `git diff HEAD` so staged changes are included)\nREPO_ROOT=\"$(git rev-parse --show-toplevel)\"\ncd \"$REPO_ROOT\"\n\ngit diff --no-color --full-index --binary HEAD > \"$REPO_ROOT\u002Fpatch_1.diff\"\n\ntest -s \"$REPO_ROOT\u002Fpatch_1.diff\"\n\n# 5) Verify again (match CI\u002Ftask expectations)\n$MVN -e -DtrimStackTrace=false clean test\n```\n\n## General Maven lifecycle reminders\n\n- In multi-module projects, use the reactor summary to identify the first genuinely failing module, then inspect that module's own integration steps.\n- Prefer minimal, targeted changes. Fix the root cause (dependency\u002Fconfig\u002Ftoolchain drift) rather than masking errors by skipping build phases.\n","# Maven Build Lifecycle — CI Repair Workflow\n\n## SkillHone artifact contract (do this in every run)\n\nThis task family is evaluated on **build success** and on two explicit artifacts. Create them as files (not just as prose in chat).\n\n### Required files\n\n1. **Diagnosis note** (absolute path): `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt`\n2. **One or more patch files** (absolute path, in repo root): `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\u002Fpatch_1.diff` (and `patch_2.diff`, …)\n\n> Replace `\u003Crepo>` and `\u003Cid>` with the values from the task prompt. If you are already `cd`’d into the repo root, writing `patch_1.diff` in the current directory satisfies the required path.\n\n### Quick templates (copy\u002Fpaste)\n\nCreate the diagnosis note **early**, and update it as you learn more:\n\n```bash\nmkdir -p \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\ncat > \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt \u003C\u003C'EOF'\nToolchain\n- java: \u003Cpaste `java -version`>\n- maven: \u003Cpaste `.\u002Fmvnw -v` or `mvn -v`>\n\nReproduction\n- repo: \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\n- command: \u003Cexact mvn command that fails>\n- first failing module\u002FIT project: \u003Cmodule path or src\u002Fit\u002F* path>\n\nFirst real error\n- \u003Cfirst compiler\u002Ftest error line(s)>\n\nRoot cause hypothesis\n- \u003Cwhy it fails>\n\nPlanned fix\n- \u003Cwhat file(s) \u002F pom changes you will make>\nEOF\n```\n\nGenerate a **non-empty** patch file from your changes **in the repo root**.\n\nTwo common ways people accidentally produce an empty\u002Fmissing patch:\n- They run the command from a subdirectory (e.g., inside `src\u002Fit\u002F...`) and save the diff there.\n- They stage changes with `git add`, then use `git diff` (which only shows *unstaged* changes).\n\nUse this robust snippet instead:\n\n```bash\n# From anywhere inside the git repo:\nREPO_ROOT=\"$(git rev-parse --show-toplevel)\"\ncd \"$REPO_ROOT\"\n\n# `git diff HEAD` captures both staged + unstaged changes.\ngit diff --no-color --full-index --binary HEAD > \"$REPO_ROOT\u002Fpatch_1.diff\"\n\ntest -s \"$REPO_ROOT\u002Fpatch_1.diff\"\n```\n\nTo match the task’s “apply the diff” step, ensure the patch applies cleanly **from the repo root**:\n\n```bash\ngit apply --check \"$REPO_ROOT\u002Fpatch_1.diff\"\n\n# If you need to demonstrate application on a clean tree, do it on a clean checkout.\n# Otherwise, it’s enough that the repo already contains the changes represented by the patch.\n```\n\nIf `git apply` fails because the working tree already contains the same edits, don’t throw away the patch.\nEither apply it on a clean tree, or keep your current edits and proceed as long as `patch_*.diff` correctly represents the final change.\n\n## 1) Locate the repo root (don’t guess)\n\n- The task prompt typically gives an exact path like `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>`.\n- `cd` to that directory and confirm it’s the Maven root:\n  - `test -f pom.xml` should succeed.\n\nIf you are unsure where the root POM is, search for it, but avoid picking an unrelated nested `pom.xml` by accident (multi-module repos have many). Prefer the *top-level* one.\n\n## 2) Toolchain selection (Maven + JDK)\n\n### Maven\n\n1. Prefer the Maven Wrapper (`.\u002Fmvnw`) **if present and usable**; it often matches the project’s expected Maven version.\n2. Fall back to system Maven (`mvn`) if the wrapper is missing **or fails to run** (e.g., wrapper download\u002Fnetwork restrictions, missing wrapper JAR, permission issues).\n\nMinimal robust snippet:\n\n```bash\nMVN=mvn\nif [ -f .\u002Fmvnw ]; then\n  MVN=\".\u002Fmvnw\"\n  [ -x .\u002Fmvnw ] || MVN=\"bash .\u002Fmvnw\"\nfi\n\n# Validate the chosen Maven command; if wrapper fails, fall back.\n$MVN -v || { MVN=mvn; mvn -v; }\n```\n\n### JDK\n\nRecord in your note:\n- `java -version`\n- the project’s expected release level (from `pom.xml` and\u002For CI config)\n\nIf you see errors like **\"invalid target release\"**, **\"unsupported class file major version\"**, or bytecode\u002Fversion mismatches:\n\n- Check `pom.xml` for `maven-compiler-plugin` configuration and properties such as:\n  - `maven.compiler.release`, `maven.compiler.source`, `maven.compiler.target`\n- Check CI configuration (e.g., `.travis.yml`, GitHub Actions) for the JDK version.\n- Prefer switching to the expected JDK (e.g., via `JAVA_HOME` \u002F `PATH`) rather than “papering over” the mismatch.\n- If the project uses Maven Toolchains (`maven-toolchains-plugin`), follow that approach instead of ad-hoc environment changes.\n\n## 3) Reproduce the failure the same way CI does\n\n### Use the CI command first\n\n- Mirror CI goals\u002Fprofiles first; then narrow down once you know the first failing module.\n- Find the exact Maven goals and profiles from CI config\u002Flogs (common examples: `test`, `verify`, `-P...`, `-D...`).\n- Always include stack traces for diagnosis:\n  - `-e -DtrimStackTrace=false`\n\nIf the CI command is unknown, start with a reasonable baseline and iterate.\n\nFor **final verification**, prefer `clean verify` because it’s the most common CI target and exercises more of the lifecycle (unit tests, integration tests, and plugins bound to `verify`).\n\n```bash\n# Prefer wrapper if available (see toolchain section)\n\n# Good default (and recommended final check)\n$MVN -e -DtrimStackTrace=false clean verify\n\n# Faster loop when you’re iterating and `verify` is too slow\n$MVN -e -DtrimStackTrace=false clean test\n```\n\n### Narrow down for faster iteration\n\nOnce you know the first failing module, rerun narrowly:\n\n```bash\n# From the repo root, target a single module by artifactId and build its deps.\n$MVN -e -DtrimStackTrace=false -pl :\u003CartifactId> -am test\n```\n\nTip: `-DskipTests` skips running tests but still compiles them; `-Dmaven.test.skip=true` skips compiling tests too. Use these only for *triage*—final verification should match CI\u002Ftask expectations.\n\n## 4) Maven Invoker failures: debug the nested project, not just the reactor\n\n`maven-invoker-plugin` can launch independent Maven builds from integration test projects such as `src\u002Fit\u002F*\u002Fpom.xml`. Those nested builds have their own dependency mediation and can fail even when the parent module's normal unit tests pass.\n\nIf Maven reports output similar to:\n\n```text\nThe following builds failed:\n*  \u003Cit-project>\u002Fpom.xml\n```\n\nthen:\n\n1. Locate the exact integration-test POM named by the Invoker (often under `...\u002Fsrc\u002Fit\u002F\u003Cname>\u002Fpom.xml`).\n2. Read the corresponding Invoker `build.log` and\u002For `invoker-reports` output (commonly under `target\u002Fit\u002F...`).\n3. Identify the *first concrete compiler\u002Ftest error* inside that nested build.\n4. Inspect the nested POM's direct dependencies and resolved versions.\n   - Run `mvn help:effective-pom` and `mvn dependency:tree` inside the nested build directory if needed.\n5. Repair the nested dependency\u002Fconfiguration drift instead of broad-editing unrelated top-level modules.\n\nDo not assume versions declared in the parent reactor automatically govern an Invoker integration-test POM. Some IT POMs are copied or maintained separately and can become stale.\n\n## 5) Dependency-drift signals in nested builds\n\nCommon symptoms that point to nested-build dependency\u002Fversion drift:\n\n- \"cannot find symbol\" for a class\u002Fmethod that exists in newer versions of a library\n- test-only artifacts that are designed to be version-coupled (e.g., `\u003Clib>` and `\u003Clib>-testlib`) resolving to different versions\n- `NoSuchMethodError` \u002F `ClassNotFoundException` during tests even though the main reactor compiles\n\nPrefer aligning versions\u002Fconfiguration in the nested POM (or via a BOM\u002Fimport that the nested POM actually inherits) rather than rewriting valid source code to avoid an API.\n\n## 6) Minimal diagnostic sequence (end-to-end)\n\n```bash\n# 0) Create\u002Fupdate the diagnosis note first\n#    (see the template in the artifact contract section)\n\n# 1) cd to the repo path from the task prompt\ncd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\n\n# 2) Select toolchain\nMVN=mvn\nif [ -f .\u002Fmvnw ]; then\n  MVN=\".\u002Fmvnw\"\n  [ -x .\u002Fmvnw ] || MVN=\"bash .\u002Fmvnw\"\nfi\n$MVN -v || { MVN=mvn; mvn -v; }\njava -version\n\n# 3) Reproduce\n$MVN -e -DtrimStackTrace=false clean test\n\n# 4) After implementing a fix, write a patch file in the repo root\n#    (use `git diff HEAD` so staged changes are included)\nREPO_ROOT=\"$(git rev-parse --show-toplevel)\"\ncd \"$REPO_ROOT\"\n\ngit diff --no-color --full-index --binary HEAD > \"$REPO_ROOT\u002Fpatch_1.diff\"\n\ntest -s \"$REPO_ROOT\u002Fpatch_1.diff\"\n\n# 5) Verify again (match CI\u002Ftask expectations)\n$MVN -e -DtrimStackTrace=false clean test\n```\n\n## General Maven lifecycle reminders\n\n- In multi-module projects, use the reactor summary to identify the first genuinely failing module, then inspect that module's own integration steps.\n- Prefer minimal, targeted changes. Fix the root cause (dependency\u002Fconfig\u002Ftoolchain drift) rather than masking errors by skipping build phases.\n",{"name":5,"description":7},"main","cdcb6d230f3b15c3c33f8a2bdd16439f43602cbe","controlled-skill-repair-experiments\u002Fresult\u002Fskillhone-gpt5.2-xhigh\u002Fcandidates\u002Fsingle-fix-build-google-auto-RI-001\u002Fround-5\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\u002Fskillhone-gpt5.2-xhigh\u002Fcandidates\u002Fsingle-fix-build-google-auto-RI-001\u002Fround-5\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",[],[]]