[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BNEPT104B429643JBYMFGR":3,"skill-same:01M7BNEPT104B429643JBYMFGR":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},"01M7BNEPT104B429643JBYMFGR","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\u002Fskilltta-claude4.7\u002Ftasks\u002Fsingle-fix-build-google-auto-RI-001\u002Frepaired_skill\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## Toolchain selection\n\nBefore attempting reproduction, confirm the build toolchain the project was\nauthored against. Legacy snapshots (for example older Google Auto \u002F AutoValue\ncheckouts) commonly target **JDK 8** and Maven 3.3–3.6. Modern JDKs can break\nannotation processing, `-source`\u002F`-target` validation, and Guava internals.\n\nChecks to perform before running Maven:\n\n1. Inspect `.travis.yml`, `.github\u002Fworkflows\u002F*.yml`, or `Jenkinsfile` for the\n   declared `jdk:` \u002F `java-version:` and any `MAVEN_OPTS`.\n2. Read the root `pom.xml` for `maven.compiler.source` \u002F `maven.compiler.target`\n   \u002F `maven.compiler.release` and for any `\u003CrequireJavaVersion>` enforcer rule.\n3. Verify the active `JAVA_HOME` (`java -version`, `mvn -v`) matches the\n   project's expectation; switch toolchain before reproducing if not.\n4. Note the Maven version actually invoked — plugin defaults differ across\n   Maven 3.x minor releases.\n\nDo not upgrade `source`\u002F`target` just to make the current JDK happy; prefer\naligning the JDK to the project.\n\n## Failure reproduction\n\nReproduce the failure deterministically before editing anything:\n\n```bash\ncd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\n\n# Primary reproduction (covers Invoker integration tests, which only run in\n# the integration-test \u002F verify phases — never at compile).\nmvn -B -V -ntp -e clean verify 2>&1 | tee \u002Ftmp\u002Fbuild.log\n\n# Narrow to a single module when the reactor is large:\n# mvn -B -V -ntp -e -pl \u003Cmodule> -am verify 2>&1 | tee \u002Ftmp\u002Fbuild.log\n\n# Some legacy projects gate Invoker ITs behind a profile:\n# mvn -B -V -ntp -e -Prun-its verify 2>&1 | tee \u002Ftmp\u002Fbuild.log\n```\n\nKey points:\n\n- The `maven-invoker-plugin` binds to `integration-test`; `mvn compile` or\n  `mvn test` will not surface Invoker failures.\n- Capture the full log to `\u002Ftmp\u002Fbuild.log` so later `grep` passes are cheap.\n- Prefer `-B -V -ntp -e` so that output is stable, versions are logged, and\n  stack traces are shown on plugin errors.\n\n## Maven Invoker failures: debug the nested project, not just the reactor\n\n`maven-invoker-plugin` can launch independent Maven builds from files such as\n`src\u002Fit\u002F*\u002Fpom.xml`. Those nested builds have their own dependency mediation and\ncan 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*  functional\u002Fpom.xml\n```\n\nthen:\n\n1. Locate the exact integration-test POM named by the Invoker.\n2. Read the corresponding Invoker `build.log` or the surrounding CI output.\n3. Identify the *first concrete compiler\u002Ftest error* inside that nested build.\n4. Inspect the nested POM's direct dependencies and versions.\n5. Run `mvn -f \u003Cnested-pom> dependency:tree` to see what the nested build\n   actually resolved (its mediation is independent of the reactor).\n6. Repair the nested dependency\u002Fconfiguration drift instead of broad-editing\n   unrelated top-level modules.\n\nDo not assume versions declared in the parent module automatically govern an\nInvoker integration-test POM. An integration-test POM copied or synchronized\nseparately can become stale.\n\n## Missing library classes usually indicate dependency-version drift\n\nFor a compiler error such as:\n\n```text\ncannot find symbol: class MoreObjects\nlocation: package com.google.common.base\n```\n\nfirst ask which Guava version the failing nested build actually selected.\n`MoreObjects` is an API-version signal: a stale\u002Ftransitively selected Guava can\nmake valid test source fail even though the main reactor uses a newer Guava.\n\nFor test libraries that are designed to be version-coupled (for example\n`guava` and `guava-testlib`), prefer an explicit, synchronized dependency set.\nDo not \"fix\" valid source by rewriting it to avoid the missing API unless the\nsource itself is demonstrated to be wrong.\n\n## Diagnosing dependency drift in an Invoker integration test\n\nWhen a nested Invoker POM fails with `cannot find symbol` or `NoSuchMethodError`\nagainst a common library (Guava, Truth, JUnit, jsr305, …), treat it as a\n*drift-detection* problem rather than reaching for a specific version list:\n\n1. Open the nested POM (e.g. `\u003Cmodule>\u002Fsrc\u002Fit\u002F\u003Cname>\u002Fpom.xml`) and list its\n   direct dependencies and declared versions.\n2. Run `mvn -f \u003Cnested-pom> dependency:tree -Dverbose` to see which version\n   each GAV actually resolved to and why.\n3. Open the Invoker `build.log` under `target\u002Fit\u002F\u003Cname>\u002Fbuild.log` and locate\n   the *first* compiler error. The symbol it mentions implies a minimum API\n   level for the owning library.\n4. Cross-check that minimum against the resolved version from step 2. A\n   missing symbol in a library that *is* on the classpath almost always means\n   the resolved version is older than the source requires.\n5. Prefer synchronizing version-coupled artifacts together (e.g. `guava` with\n   `guava-testlib`) rather than bumping one in isolation.\n\n*Illustrative example only* (do not copy blindly; verify against the repository\nunder repair): one historical AutoValue functional-IT drift was resolved by\nsynchronizing `jsr305`, `junit`, `guava` + `guava-testlib`, and `truth` to a\nmutually compatible set declared directly in the nested POM. The correct set\nfor any given snapshot must be derived from the error log and dependency tree,\nnot assumed.\n\n## Build-repair artifact contract\n\nThis benchmark requires both a diagnosis artifact and an applicable patch.\nBefore finishing:\n\n1. Write `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt` with the reproduced\n   target environment, the exact failing nested POM, the first real error, and\n   the dependency-drift root cause.\n2. Create at least one non-empty standard unified diff at\n   `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\u002Fpatch_1.diff` (substituting the\n   actual repository and id segments provided by the task) containing the\n   intended source\u002Fconfiguration change.\n3. Apply that patch to the failed repository.\n4. Check `git diff`\u002F`git status` and ensure the intended project file—not only\n   the patch artifact—was changed.\n\n## Minimal diagnostic sequence\n\n```bash\ncd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\n\n# 1. Confirm toolchain and reactor layout.\nmvn -v\nfind . -maxdepth 3 -name pom.xml -print\n\n# 2. Reproduce the failure end-to-end and capture logs.\nmvn -B -V -ntp -e clean verify 2>&1 | tee \u002Ftmp\u002Fbuild.log\n\n# 3. If an Invoker integration build fails, inspect the nested POM and its\n#    own build.log for the first concrete error.\nfind . -path '*\u002Fsrc\u002Fit\u002F*\u002Fpom.xml' -print\nfind . -path '*\u002Ftarget\u002Fit\u002F*\u002Fbuild.log' -print\n# sed -n '1,180p' \u003Cmodule>\u002Fsrc\u002Fit\u002F\u003Cname>\u002Fpom.xml\n# sed -n '1,200p' \u003Cmodule>\u002Ftarget\u002Fit\u002F\u003Cname>\u002Fbuild.log\n\n# 4. Compare declared vs resolved versions in the nested build.\n# mvn -f \u003Cmodule>\u002Fsrc\u002Fit\u002F\u003Cname>\u002Fpom.xml dependency:tree -Dverbose\n```\n\n## General Maven lifecycle reminders\n\n- In multi-module projects, use the reactor summary to identify the first\n  genuinely failing module, then inspect that module's own integration steps.\n- Invoker integration tests run during `integration-test`\u002F`verify`; always\n  reproduce with a phase that reaches them.\n- Prefer aligning the JDK to the project rather than silently bumping\n  `maven.compiler.source`\u002F`target` to appease a newer JDK.\n","# Maven Build Lifecycle — Legacy CI Repair Workflow\n\n## Toolchain selection\n\nBefore attempting reproduction, confirm the build toolchain the project was\nauthored against. Legacy snapshots (for example older Google Auto \u002F AutoValue\ncheckouts) commonly target **JDK 8** and Maven 3.3–3.6. Modern JDKs can break\nannotation processing, `-source`\u002F`-target` validation, and Guava internals.\n\nChecks to perform before running Maven:\n\n1. Inspect `.travis.yml`, `.github\u002Fworkflows\u002F*.yml`, or `Jenkinsfile` for the\n   declared `jdk:` \u002F `java-version:` and any `MAVEN_OPTS`.\n2. Read the root `pom.xml` for `maven.compiler.source` \u002F `maven.compiler.target`\n   \u002F `maven.compiler.release` and for any `\u003CrequireJavaVersion>` enforcer rule.\n3. Verify the active `JAVA_HOME` (`java -version`, `mvn -v`) matches the\n   project's expectation; switch toolchain before reproducing if not.\n4. Note the Maven version actually invoked — plugin defaults differ across\n   Maven 3.x minor releases.\n\nDo not upgrade `source`\u002F`target` just to make the current JDK happy; prefer\naligning the JDK to the project.\n\n## Failure reproduction\n\nReproduce the failure deterministically before editing anything:\n\n```bash\ncd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\n\n# Primary reproduction (covers Invoker integration tests, which only run in\n# the integration-test \u002F verify phases — never at compile).\nmvn -B -V -ntp -e clean verify 2>&1 | tee \u002Ftmp\u002Fbuild.log\n\n# Narrow to a single module when the reactor is large:\n# mvn -B -V -ntp -e -pl \u003Cmodule> -am verify 2>&1 | tee \u002Ftmp\u002Fbuild.log\n\n# Some legacy projects gate Invoker ITs behind a profile:\n# mvn -B -V -ntp -e -Prun-its verify 2>&1 | tee \u002Ftmp\u002Fbuild.log\n```\n\nKey points:\n\n- The `maven-invoker-plugin` binds to `integration-test`; `mvn compile` or\n  `mvn test` will not surface Invoker failures.\n- Capture the full log to `\u002Ftmp\u002Fbuild.log` so later `grep` passes are cheap.\n- Prefer `-B -V -ntp -e` so that output is stable, versions are logged, and\n  stack traces are shown on plugin errors.\n\n## Maven Invoker failures: debug the nested project, not just the reactor\n\n`maven-invoker-plugin` can launch independent Maven builds from files such as\n`src\u002Fit\u002F*\u002Fpom.xml`. Those nested builds have their own dependency mediation and\ncan 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*  functional\u002Fpom.xml\n```\n\nthen:\n\n1. Locate the exact integration-test POM named by the Invoker.\n2. Read the corresponding Invoker `build.log` or the surrounding CI output.\n3. Identify the *first concrete compiler\u002Ftest error* inside that nested build.\n4. Inspect the nested POM's direct dependencies and versions.\n5. Run `mvn -f \u003Cnested-pom> dependency:tree` to see what the nested build\n   actually resolved (its mediation is independent of the reactor).\n6. Repair the nested dependency\u002Fconfiguration drift instead of broad-editing\n   unrelated top-level modules.\n\nDo not assume versions declared in the parent module automatically govern an\nInvoker integration-test POM. An integration-test POM copied or synchronized\nseparately can become stale.\n\n## Missing library classes usually indicate dependency-version drift\n\nFor a compiler error such as:\n\n```text\ncannot find symbol: class MoreObjects\nlocation: package com.google.common.base\n```\n\nfirst ask which Guava version the failing nested build actually selected.\n`MoreObjects` is an API-version signal: a stale\u002Ftransitively selected Guava can\nmake valid test source fail even though the main reactor uses a newer Guava.\n\nFor test libraries that are designed to be version-coupled (for example\n`guava` and `guava-testlib`), prefer an explicit, synchronized dependency set.\nDo not \"fix\" valid source by rewriting it to avoid the missing API unless the\nsource itself is demonstrated to be wrong.\n\n## Diagnosing dependency drift in an Invoker integration test\n\nWhen a nested Invoker POM fails with `cannot find symbol` or `NoSuchMethodError`\nagainst a common library (Guava, Truth, JUnit, jsr305, …), treat it as a\n*drift-detection* problem rather than reaching for a specific version list:\n\n1. Open the nested POM (e.g. `\u003Cmodule>\u002Fsrc\u002Fit\u002F\u003Cname>\u002Fpom.xml`) and list its\n   direct dependencies and declared versions.\n2. Run `mvn -f \u003Cnested-pom> dependency:tree -Dverbose` to see which version\n   each GAV actually resolved to and why.\n3. Open the Invoker `build.log` under `target\u002Fit\u002F\u003Cname>\u002Fbuild.log` and locate\n   the *first* compiler error. The symbol it mentions implies a minimum API\n   level for the owning library.\n4. Cross-check that minimum against the resolved version from step 2. A\n   missing symbol in a library that *is* on the classpath almost always means\n   the resolved version is older than the source requires.\n5. Prefer synchronizing version-coupled artifacts together (e.g. `guava` with\n   `guava-testlib`) rather than bumping one in isolation.\n\n*Illustrative example only* (do not copy blindly; verify against the repository\nunder repair): one historical AutoValue functional-IT drift was resolved by\nsynchronizing `jsr305`, `junit`, `guava` + `guava-testlib`, and `truth` to a\nmutually compatible set declared directly in the nested POM. The correct set\nfor any given snapshot must be derived from the error log and dependency tree,\nnot assumed.\n\n## Build-repair artifact contract\n\nThis benchmark requires both a diagnosis artifact and an applicable patch.\nBefore finishing:\n\n1. Write `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt` with the reproduced\n   target environment, the exact failing nested POM, the first real error, and\n   the dependency-drift root cause.\n2. Create at least one non-empty standard unified diff at\n   `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\u002Fpatch_1.diff` (substituting the\n   actual repository and id segments provided by the task) containing the\n   intended source\u002Fconfiguration change.\n3. Apply that patch to the failed repository.\n4. Check `git diff`\u002F`git status` and ensure the intended project file—not only\n   the patch artifact—was changed.\n\n## Minimal diagnostic sequence\n\n```bash\ncd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\n\n# 1. Confirm toolchain and reactor layout.\nmvn -v\nfind . -maxdepth 3 -name pom.xml -print\n\n# 2. Reproduce the failure end-to-end and capture logs.\nmvn -B -V -ntp -e clean verify 2>&1 | tee \u002Ftmp\u002Fbuild.log\n\n# 3. If an Invoker integration build fails, inspect the nested POM and its\n#    own build.log for the first concrete error.\nfind . -path '*\u002Fsrc\u002Fit\u002F*\u002Fpom.xml' -print\nfind . -path '*\u002Ftarget\u002Fit\u002F*\u002Fbuild.log' -print\n# sed -n '1,180p' \u003Cmodule>\u002Fsrc\u002Fit\u002F\u003Cname>\u002Fpom.xml\n# sed -n '1,200p' \u003Cmodule>\u002Ftarget\u002Fit\u002F\u003Cname>\u002Fbuild.log\n\n# 4. Compare declared vs resolved versions in the nested build.\n# mvn -f \u003Cmodule>\u002Fsrc\u002Fit\u002F\u003Cname>\u002Fpom.xml dependency:tree -Dverbose\n```\n\n## General Maven lifecycle reminders\n\n- In multi-module projects, use the reactor summary to identify the first\n  genuinely failing module, then inspect that module's own integration steps.\n- Invoker integration tests run during `integration-test`\u002F`verify`; always\n  reproduce with a phase that reaches them.\n- Prefer aligning the JDK to the project rather than silently bumping\n  `maven.compiler.source`\u002F`target` to appease a newer JDK.\n",{"name":5,"description":7},"main","cdcb6d230f3b15c3c33f8a2bdd16439f43602cbe","controlled-skill-repair-experiments\u002Fresult\u002Fskilltta-claude4.7\u002Ftasks\u002Fsingle-fix-build-google-auto-RI-001\u002Frepaired_skill\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\u002Fskilltta-claude4.7\u002Ftasks\u002Fsingle-fix-build-google-auto-RI-001\u002Frepaired_skill\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",[],[]]