[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C3F9J23KAVEG9BKN89B085":3,"skill-same:01M7C3F9J23KAVEG9BKN89B085":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},"01M7C3F9J23KAVEG9BKN89B085","skilltta-task-guidance",null,"Task-specific operational guidance synthesized at test time from retrieved training examples.","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\u002Fevaluation\u002Fresults\u002Fskilltta-synthesis-opus47-tatumass-failed15-20260923\u002Ftasks\u002Ffix-build-agentops\u002Frepaired_skill\u002Fskilltta-task-guidance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: skilltta-task-guidance\ndescription: Task-specific operational guidance synthesized at test time from retrieved training examples.\n---\n\n# SKILL.md\n\n## When to use\nUse this skill when the task is to diagnose and repair a failing Python build in a broken repository under a fixed working root (e.g., `\u002Fhome\u002Fgithub\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>`), and the workflow demands a three-step deliverable: (1) a written analysis file, (2) one or more `patch_{i}.diff` files in the repo directory in standard `git`\u002F`diffutils` diff format, and (3) actual application of those diffs so the build succeeds. Before acting, gather:\n- The exact repo path and its layout (`ls`, find `pyproject.toml`, `setup.py`, `setup.cfg`, `tox.ini`, `requirements*.txt`, CI configs).\n- The concrete failure signal: run the build\u002Finstall\u002Ftest command the project expects (e.g., `pip install -e .`, `python -m build`, `pytest`, `python -m compileall`) and capture the real error text.\n- The Python version and any pinned dependency constraints referenced by the config.\n- Whether errors are code-level (syntax, imports, typos, missing files) vs. configuration-level (bad metadata, wrong entry points, invalid TOML, unsatisfiable deps, missing build backend).\n\n## Possible Failure Modes\n- Writing analysis or diffs to the wrong path (e.g., outside `\u002Fhome\u002Fgithub\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt` or not under `\u002Fhome\u002Fgithub\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\u002Fpatch_{i}.diff`).\n- Producing diffs that are not valid `git apply`\u002F`patch` input: missing `--- a\u002F…` and `+++ b\u002F…` headers, wrong hunk `@@` line counts, missing trailing newline, CRLF endings, or paths not relative to repo root.\n- Fixing a symptom you assumed rather than the actual error printed by the build tool — skipping the step of running the build to reproduce.\n- Editing files directly and forgetting to also emit the corresponding `patch_{i}.diff` (the task requires both the diff artifact and applying it).\n- Applying a patch on top of already-edited files, causing \"already applied\" or context mismatch failures.\n- Over-broad rewrites: rewriting whole files when a minimal hunk suffices, making diffs brittle.\n- Ignoring configuration files (`pyproject.toml`, `setup.cfg`) when the real problem is metadata\u002Fbuild-backend, not source code.\n- Introducing new dependencies or Python-version bumps that the environment cannot satisfy.\n- Not re-running the build after applying patches, or declaring success on partial fixes.\n- Touching unrelated files or leaving stray backup\u002Ftemp files in the repo.\n\n## Possible procedures\n1. **Reproduce first.** `cd` into the repo and run the natural build\u002Finstall command. Capture stderr verbatim. If unclear which command to use, inspect `pyproject.toml`\u002F`setup.py`\u002FCI files to infer it.\n2. **Classify the error.** Decide: source-code bug (SyntaxError, ImportError, NameError, bad type annotation for the Python version), packaging\u002Fconfig bug (invalid TOML, missing `build-system.requires`, wrong `packages` entry, missing `__init__.py`, wrong version specifier), or dependency issue.\n3. **Write `failed_reasons.txt`** at the exact required path with: the reproduction command, the key error lines, root-cause hypothesis, and a minimal fix plan enumerating each file to change.\n4. **Draft minimal diffs.** For each file to change, produce a unified diff with:\n   - Headers `--- a\u002F\u003Crelpath>` and `+++ b\u002F\u003Crelpath>` (relative to repo root).\n   - Correct `@@ -start,len +start,len @@` hunk headers.\n   - Enough context lines (typically 3) around each change.\n   - LF line endings and a trailing newline.\n   Save as `patch_1.diff`, `patch_2.diff`, … in the repo directory. Prefer one logical change per diff.\n5. **Apply diffs** with `git apply --check patch_1.diff` first; if it fails, inspect and correct the diff rather than editing files directly. Then `git apply patch_1.diff` (or `patch -p1 \u003C patch_1.diff` as fallback). Apply in order.\n6. **Re-run the build** to confirm the failure is resolved. If a new error surfaces, iterate: append notes, create `patch_{i+1}.diff`, apply, re-verify.\n7. **Decision points:**\n   - If the error is a missing dependency, prefer fixing the declared dependency metadata over adding runtime workarounds.\n   - If the error is Python-version syntax (e.g., walrus, f-string features, `match`), either lower the syntax or fix `python_requires`\u002Fclassifiers — pick whichever preserves intent.\n   - If tests fail but the task is \"build,\" focus on making the package installable\u002Fimportable; do not chase unrelated test failures unless they block the build.\n8. **Recovery check:** if `git apply --check` reports \"patch does not apply,\" re-read the target file's current bytes, regenerate the diff from the true current state, and retry.\n\n## Verification Checklist\n- [ ] `\u002Fhome\u002Fgithub\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt` exists and contains a concrete, evidence-based analysis and plan.\n- [ ] One or more `patch_{i}.diff` files exist under `\u002Fhome\u002Fgithub\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\u002F`, numbered sequentially starting at 1.\n- [ ] Each diff is in standard unified format (`--- a\u002F…`, `+++ b\u002F…`, valid `@@` hunks) and passes `git apply --check` against the pre-application state.\n- [ ] All diffs have been applied to the working tree (verified via `git diff` or by inspecting the changed files).\n- [ ] The original failing build command now succeeds (or at minimum the specific errors identified in `failed_reasons.txt` are gone and no regressions were introduced).\n- [ ] No files outside the scope of the identified root cause were modified; no stray temp\u002Fbackup files remain.\n- [ ] Paths in diffs are repo-root-relative, not absolute, and match the on-disk layout.\n- [ ] No content, identifiers, or fixes were copied verbatim from unrelated example tasks; the changes are derived from this repository's own error output.\n- [ ] If a patch failed to apply, the diff was regenerated from current file state rather than the underlying file being hand-edited to mask the mismatch.\n","# SKILL.md\n\n## When to use\nUse this skill when the task is to diagnose and repair a failing Python build in a broken repository under a fixed working root (e.g., `\u002Fhome\u002Fgithub\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>`), and the workflow demands a three-step deliverable: (1) a written analysis file, (2) one or more `patch_{i}.diff` files in the repo directory in standard `git`\u002F`diffutils` diff format, and (3) actual application of those diffs so the build succeeds. Before acting, gather:\n- The exact repo path and its layout (`ls`, find `pyproject.toml`, `setup.py`, `setup.cfg`, `tox.ini`, `requirements*.txt`, CI configs).\n- The concrete failure signal: run the build\u002Finstall\u002Ftest command the project expects (e.g., `pip install -e .`, `python -m build`, `pytest`, `python -m compileall`) and capture the real error text.\n- The Python version and any pinned dependency constraints referenced by the config.\n- Whether errors are code-level (syntax, imports, typos, missing files) vs. configuration-level (bad metadata, wrong entry points, invalid TOML, unsatisfiable deps, missing build backend).\n\n## Possible Failure Modes\n- Writing analysis or diffs to the wrong path (e.g., outside `\u002Fhome\u002Fgithub\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt` or not under `\u002Fhome\u002Fgithub\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\u002Fpatch_{i}.diff`).\n- Producing diffs that are not valid `git apply`\u002F`patch` input: missing `--- a\u002F…` and `+++ b\u002F…` headers, wrong hunk `@@` line counts, missing trailing newline, CRLF endings, or paths not relative to repo root.\n- Fixing a symptom you assumed rather than the actual error printed by the build tool — skipping the step of running the build to reproduce.\n- Editing files directly and forgetting to also emit the corresponding `patch_{i}.diff` (the task requires both the diff artifact and applying it).\n- Applying a patch on top of already-edited files, causing \"already applied\" or context mismatch failures.\n- Over-broad rewrites: rewriting whole files when a minimal hunk suffices, making diffs brittle.\n- Ignoring configuration files (`pyproject.toml`, `setup.cfg`) when the real problem is metadata\u002Fbuild-backend, not source code.\n- Introducing new dependencies or Python-version bumps that the environment cannot satisfy.\n- Not re-running the build after applying patches, or declaring success on partial fixes.\n- Touching unrelated files or leaving stray backup\u002Ftemp files in the repo.\n\n## Possible procedures\n1. **Reproduce first.** `cd` into the repo and run the natural build\u002Finstall command. Capture stderr verbatim. If unclear which command to use, inspect `pyproject.toml`\u002F`setup.py`\u002FCI files to infer it.\n2. **Classify the error.** Decide: source-code bug (SyntaxError, ImportError, NameError, bad type annotation for the Python version), packaging\u002Fconfig bug (invalid TOML, missing `build-system.requires`, wrong `packages` entry, missing `__init__.py`, wrong version specifier), or dependency issue.\n3. **Write `failed_reasons.txt`** at the exact required path with: the reproduction command, the key error lines, root-cause hypothesis, and a minimal fix plan enumerating each file to change.\n4. **Draft minimal diffs.** For each file to change, produce a unified diff with:\n   - Headers `--- a\u002F\u003Crelpath>` and `+++ b\u002F\u003Crelpath>` (relative to repo root).\n   - Correct `@@ -start,len +start,len @@` hunk headers.\n   - Enough context lines (typically 3) around each change.\n   - LF line endings and a trailing newline.\n   Save as `patch_1.diff`, `patch_2.diff`, … in the repo directory. Prefer one logical change per diff.\n5. **Apply diffs** with `git apply --check patch_1.diff` first; if it fails, inspect and correct the diff rather than editing files directly. Then `git apply patch_1.diff` (or `patch -p1 \u003C patch_1.diff` as fallback). Apply in order.\n6. **Re-run the build** to confirm the failure is resolved. If a new error surfaces, iterate: append notes, create `patch_{i+1}.diff`, apply, re-verify.\n7. **Decision points:**\n   - If the error is a missing dependency, prefer fixing the declared dependency metadata over adding runtime workarounds.\n   - If the error is Python-version syntax (e.g., walrus, f-string features, `match`), either lower the syntax or fix `python_requires`\u002Fclassifiers — pick whichever preserves intent.\n   - If tests fail but the task is \"build,\" focus on making the package installable\u002Fimportable; do not chase unrelated test failures unless they block the build.\n8. **Recovery check:** if `git apply --check` reports \"patch does not apply,\" re-read the target file's current bytes, regenerate the diff from the true current state, and retry.\n\n## Verification Checklist\n- [ ] `\u002Fhome\u002Fgithub\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt` exists and contains a concrete, evidence-based analysis and plan.\n- [ ] One or more `patch_{i}.diff` files exist under `\u002Fhome\u002Fgithub\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\u002F`, numbered sequentially starting at 1.\n- [ ] Each diff is in standard unified format (`--- a\u002F…`, `+++ b\u002F…`, valid `@@` hunks) and passes `git apply --check` against the pre-application state.\n- [ ] All diffs have been applied to the working tree (verified via `git diff` or by inspecting the changed files).\n- [ ] The original failing build command now succeeds (or at minimum the specific errors identified in `failed_reasons.txt` are gone and no regressions were introduced).\n- [ ] No files outside the scope of the identified root cause were modified; no stray temp\u002Fbackup files remain.\n- [ ] Paths in diffs are repo-root-relative, not absolute, and match the on-disk layout.\n- [ ] No content, identifiers, or fixes were copied verbatim from unrelated example tasks; the changes are derived from this repository's own error output.\n- [ ] If a patch failed to apply, the diff was regenerated from current file state rather than the underlying file being hand-edited to mask the mismatch.\n",{"name":5,"description":7},"main","cdcb6d230f3b15c3c33f8a2bdd16439f43602cbe","evaluation\u002Fresults\u002Fskilltta-synthesis-opus47-tatumass-failed15-20260923\u002Ftasks\u002Ffix-build-agentops\u002Frepaired_skill\u002Fskilltta-task-guidance",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 skilltta-task-guidance",{"tool":37,"command":38},"bunx","bunx skills add linyouxue\u002Fskill-repair-benchmark --skill skilltta-task-guidance",{"tool":40,"command":41},"pnpm","pnpm dlx skills add linyouxue\u002Fskill-repair-benchmark --skill skilltta-task-guidance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fevaluation\u002Fresults\u002Fskilltta-synthesis-opus47-tatumass-failed15-20260923\u002Ftasks\u002Ffix-build-agentops\u002Frepaired_skill\u002Fskilltta-task-guidance\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",[],[]]