[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71E52MJKF29S6JPX8JSZ8M9":3,"skill-same:01M71E52MJKF29S6JPX8JSZ8M9":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M71E52MJKF29S6JPX8JSZ8M9","evals-context",null,"Provides context for Alpha's retained evaluation infrastructure and extension quality suites. Use when a task mentions evals, evaluation runs, eval exercises, benchmark campaigns, or VS Code extension certification.","lukegob10\u002Falpha","lukegob10","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F70302814?v=4","01M71E4WK7A0NNE7QK5R168HKH","01M71E4WKWRSR78QAC66WCCQDT",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flukegob10\u002Falpha\u002Fblob\u002Fmain\u002F.alpha\u002Fskills\u002Fevals-context\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"evals context","context","evals","infrastructure","certification","benchmark","extension","Evaluation","quality","exercises","task","code","when","use","eval","alpha","for","campaigns","2026-11-10 10:12:30",false,"---\nname: evals-context\ndescription: Provides context for Alpha's retained evaluation infrastructure and extension quality suites. Use when a task mentions evals, evaluation runs, eval exercises, benchmark campaigns, or VS Code extension certification.\n---\n\n# Evals Codebase Context\n\nUse this skill for work on the evaluation infrastructure that exercises the Alpha VS Code extension. The repository keeps\nthe evaluator package, the exact-host VS Code runner, extension-specific suites, and the campaign definitions needed to\nreproduce benchmark work. The former standalone eval dashboard and nightly packaging variant are retired.\n\n## When to use this skill\n\nUse it when a task involves:\n\n- `packages\u002Fevals\u002F` controller, runner, database, evidence, grading, or benchmark code\n- `apps\u002Fvscode-e2e\u002F` host-contract and live evaluation runners\n- extension-specific suites under `evals\u002F`\n- historical campaign snapshots under `evals\u002Farchive\u002Ffrontier-campaign\u002F`\n- adding or reviewing exercises in the external [Alpha-Evals](https:\u002F\u002Fgithub.com\u002FAlphaInc\u002FAlpha-Evals) repository\n\nDo not use it for ordinary extension or webview changes unless the task also changes an evaluation contract.\n\n## Repository boundaries\n\n| Component              | Path                                                   | Purpose                                                                                                                  |\n| ---------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ |\n| Evaluation package     | `packages\u002Fevals\u002F`                                      | Optional controller, runner, database, evidence, grading, and benchmark tooling that executes the real VS Code extension |\n| VS Code runner         | `apps\u002Fvscode-e2e\u002F`                                     | Exact VS Code 1.141.0 reference-host and 1.125.0 compatibility tests, scripted providers, and live host harnesses        |\n| Local extension suites | `evals\u002F`                                               | Deterministic extension and safety suites that are part of Alpha's quality checks                                        |\n| Historical campaigns   | `evals\u002Farchive\u002Ffrontier-campaign\u002F`                     | Archived configurations, authoring reports, and milestone results; new run output belongs in ignored evaluator artifacts |\n| Exercise repository    | [Alpha-Evals](https:\u002F\u002Fgithub.com\u002FAlphaInc\u002FAlpha-Evals) | External language exercises and their tests                                                                              |\n\nThe evaluator launches the real extension through VS Code. It is not a second Alpha runtime. Keep extension policy,\ntool availability, persisted task behavior, and provider contracts in the extension packages that own them.\n\n## Package layout\n\nThe package layout can evolve with the evaluator; these are the current active areas:\n\n```text\npackages\u002Fevals\u002F\n├── src\u002Fbenchmark\u002F       # benchmark commands\n├── src\u002Fcampaign\u002F        # reproducible campaign definitions and runs\n├── src\u002Fcertification\u002F   # certification workflows\n├── src\u002Fcli\u002F             # evaluator orchestration and VS Code task execution\n├── src\u002Fdb\u002F              # run, task, and evidence persistence\n├── src\u002Fevidence\u002F        # manifests, journals, reconstruction, and integrity checks\n├── src\u002Fexperiments\u002F     # governed comparison and reporting helpers\n├── src\u002Fexercises\u002F       # exercise loading and task metadata\n├── src\u002Fgrading\u002F         # result aggregation and grading plugins\n├── src\u002Finfrastructure\u002F  # Docker and runner lifecycle adapters\n├── src\u002Flifecycle\u002F       # run state transitions\n├── src\u002Forchestration\u002F   # run scheduling and coordination\n└── src\u002Ftesting\u002F         # evaluator test helpers and contracts\n```\n\nTreat `packages\u002Fevals\u002Fsrc\u002F**\u002F__fixtures__` and contract fixtures as immutable test inputs unless a contract change\nexplicitly requires updating them. Historical campaign output is evidence, not a source fixture. New campaigns default to\n`packages\u002Fevals\u002Fartifacts\u002Fcampaigns\u002F`; authoring reports default to `packages\u002Fevals\u002Fartifacts\u002Fauthoring\u002F`. Both are ignored.\n\n## Common commands\n\nRun the default repository checks from the root for the extension, webview, and VS Code E2E dependency graph:\n\n```sh\npnpm lint\npnpm check-types\npnpm test\n```\n\nUse the exact release-host gate when a change affects extension activation, VS Code APIs, task lifecycle, or packaging:\n\n```sh\npnpm --filter @alpha-code\u002Fvscode-e2e test:smoke:1410\n```\n\nThe default root checks intentionally exclude optional evaluator work. Run all retained workspace checks explicitly when\nthat surface is in scope:\n\n```sh\npnpm lint:all\npnpm check-types:all\npnpm test:all\n```\n\nFor evaluator-only validation, prefer the package scripts so each suite's environment is explicit:\n\n```sh\npnpm test:evals\npnpm test:evals:offline\npnpm --filter @alpha-code\u002Fevals test:unit\npnpm --filter @alpha-code\u002Fevals test:contract\npnpm --filter @alpha-code\u002Fevals test:certification\n```\n\nLive evaluator runs require the configured provider credentials, a working VS Code installation, and any services named\nby the selected package command. Do not treat an offline or fixture run as evidence for live provider quality.\n\n## Adding or changing exercises\n\nFollow the [authoring guide](..\u002F..\u002F..\u002Fpackages\u002Fevals\u002FREADME.md#authoring-and-running-benchmarks) for local or external\nexercise roots. Keep the evaluator's language adapters, Docker image, and tests in sync. A new exercise should include\nits instructions, implementation stub, language-specific test, and deterministic success criteria.\n\nChanges to evaluator behavior should include focused package tests and, when the behavior crosses the extension boundary,\nan exact-host or contract test. Preserve historical run records and result values; migrations and compatibility readers\nmust remain able to load older records.\n\n## Campaigns and evidence\n\nTracked files under `evals\u002Farchive\u002Ffrontier-campaign\u002F` preserve historical definitions, reports, and reproducibility\nmetadata. Some snapshots name retired packages and missing documents; do not treat them as current runnable commands.\nPreserve their bytes and recorded digests. Explicit legacy artifact roots remain supported for existing configurations.\nDo not delete immutable evaluator fixtures because no current source file imports them: runners resolve inputs by path.\n\nWhen reporting benchmark results, identify the campaign\u002Fconfiguration, evaluator version, VS Code host, model and effort,\nfixture or exercise revision, and evidence root. Separate deterministic offline checks from live-model observations.\n","# Evals Codebase Context\n\nUse this skill for work on the evaluation infrastructure that exercises the Alpha VS Code extension. The repository keeps\nthe evaluator package, the exact-host VS Code runner, extension-specific suites, and the campaign definitions needed to\nreproduce benchmark work. The former standalone eval dashboard and nightly packaging variant are retired.\n\n## When to use this skill\n\nUse it when a task involves:\n\n- `packages\u002Fevals\u002F` controller, runner, database, evidence, grading, or benchmark code\n- `apps\u002Fvscode-e2e\u002F` host-contract and live evaluation runners\n- extension-specific suites under `evals\u002F`\n- historical campaign snapshots under `evals\u002Farchive\u002Ffrontier-campaign\u002F`\n- adding or reviewing exercises in the external [Alpha-Evals](https:\u002F\u002Fgithub.com\u002FAlphaInc\u002FAlpha-Evals) repository\n\nDo not use it for ordinary extension or webview changes unless the task also changes an evaluation contract.\n\n## Repository boundaries\n\n| Component              | Path                                                   | Purpose                                                                                                                  |\n| ---------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ |\n| Evaluation package     | `packages\u002Fevals\u002F`                                      | Optional controller, runner, database, evidence, grading, and benchmark tooling that executes the real VS Code extension |\n| VS Code runner         | `apps\u002Fvscode-e2e\u002F`                                     | Exact VS Code 1.141.0 reference-host and 1.125.0 compatibility tests, scripted providers, and live host harnesses        |\n| Local extension suites | `evals\u002F`                                               | Deterministic extension and safety suites that are part of Alpha's quality checks                                        |\n| Historical campaigns   | `evals\u002Farchive\u002Ffrontier-campaign\u002F`                     | Archived configurations, authoring reports, and milestone results; new run output belongs in ignored evaluator artifacts |\n| Exercise repository    | [Alpha-Evals](https:\u002F\u002Fgithub.com\u002FAlphaInc\u002FAlpha-Evals) | External language exercises and their tests                                                                              |\n\nThe evaluator launches the real extension through VS Code. It is not a second Alpha runtime. Keep extension policy,\ntool availability, persisted task behavior, and provider contracts in the extension packages that own them.\n\n## Package layout\n\nThe package layout can evolve with the evaluator; these are the current active areas:\n\n```text\npackages\u002Fevals\u002F\n├── src\u002Fbenchmark\u002F       # benchmark commands\n├── src\u002Fcampaign\u002F        # reproducible campaign definitions and runs\n├── src\u002Fcertification\u002F   # certification workflows\n├── src\u002Fcli\u002F             # evaluator orchestration and VS Code task execution\n├── src\u002Fdb\u002F              # run, task, and evidence persistence\n├── src\u002Fevidence\u002F        # manifests, journals, reconstruction, and integrity checks\n├── src\u002Fexperiments\u002F     # governed comparison and reporting helpers\n├── src\u002Fexercises\u002F       # exercise loading and task metadata\n├── src\u002Fgrading\u002F         # result aggregation and grading plugins\n├── src\u002Finfrastructure\u002F  # Docker and runner lifecycle adapters\n├── src\u002Flifecycle\u002F       # run state transitions\n├── src\u002Forchestration\u002F   # run scheduling and coordination\n└── src\u002Ftesting\u002F         # evaluator test helpers and contracts\n```\n\nTreat `packages\u002Fevals\u002Fsrc\u002F**\u002F__fixtures__` and contract fixtures as immutable test inputs unless a contract change\nexplicitly requires updating them. Historical campaign output is evidence, not a source fixture. New campaigns default to\n`packages\u002Fevals\u002Fartifacts\u002Fcampaigns\u002F`; authoring reports default to `packages\u002Fevals\u002Fartifacts\u002Fauthoring\u002F`. Both are ignored.\n\n## Common commands\n\nRun the default repository checks from the root for the extension, webview, and VS Code E2E dependency graph:\n\n```sh\npnpm lint\npnpm check-types\npnpm test\n```\n\nUse the exact release-host gate when a change affects extension activation, VS Code APIs, task lifecycle, or packaging:\n\n```sh\npnpm --filter @alpha-code\u002Fvscode-e2e test:smoke:1410\n```\n\nThe default root checks intentionally exclude optional evaluator work. Run all retained workspace checks explicitly when\nthat surface is in scope:\n\n```sh\npnpm lint:all\npnpm check-types:all\npnpm test:all\n```\n\nFor evaluator-only validation, prefer the package scripts so each suite's environment is explicit:\n\n```sh\npnpm test:evals\npnpm test:evals:offline\npnpm --filter @alpha-code\u002Fevals test:unit\npnpm --filter @alpha-code\u002Fevals test:contract\npnpm --filter @alpha-code\u002Fevals test:certification\n```\n\nLive evaluator runs require the configured provider credentials, a working VS Code installation, and any services named\nby the selected package command. Do not treat an offline or fixture run as evidence for live provider quality.\n\n## Adding or changing exercises\n\nFollow the [authoring guide](..\u002F..\u002F..\u002Fpackages\u002Fevals\u002FREADME.md#authoring-and-running-benchmarks) for local or external\nexercise roots. Keep the evaluator's language adapters, Docker image, and tests in sync. A new exercise should include\nits instructions, implementation stub, language-specific test, and deterministic success criteria.\n\nChanges to evaluator behavior should include focused package tests and, when the behavior crosses the extension boundary,\nan exact-host or contract test. Preserve historical run records and result values; migrations and compatibility readers\nmust remain able to load older records.\n\n## Campaigns and evidence\n\nTracked files under `evals\u002Farchive\u002Ffrontier-campaign\u002F` preserve historical definitions, reports, and reproducibility\nmetadata. Some snapshots name retired packages and missing documents; do not treat them as current runnable commands.\nPreserve their bytes and recorded digests. Explicit legacy artifact roots remain supported for existing configurations.\nDo not delete immutable evaluator fixtures because no current source file imports them: runners resolve inputs by path.\n\nWhen reporting benchmark results, identify the campaign\u002Fconfiguration, evaluator version, VS Code host, model and effort,\nfixture or exercise revision, and evidence root. Separate deterministic offline checks from live-model observations.\n",{"name":5,"description":7},"main","bdda1ce57d76bafc4622250fecd1a936beb06160",".alpha\u002Fskills\u002Fevals-context",1,"https:\u002F\u002Fgithub.com\u002Flukegob10\u002Falpha","https:\u002F\u002Fgithub.com\u002Flukegob10","2026-11-13 01:50:30",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add lukegob10\u002Falpha --skill evals-context",{"tool":54,"command":55},"bunx","bunx skills add lukegob10\u002Falpha --skill evals-context",{"tool":57,"command":58},"pnpm","pnpm dlx skills add lukegob10\u002Falpha --skill evals-context","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flukegob10\u002Falpha\u002Fblob\u002Fmain\u002F.alpha\u002Fskills\u002Fevals-context\u002FSKILL.md",true,[],[63,92,113,137,162,169],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":74,"publishedAt":36},"01M71E5BXYDZZT0E3R78QVBFS5","skill-builder","Create, revise, migrate, and evaluate production-quality Agent Skills packages with standards-compliant SKILL.md frontmatter, focused instructions, progressive disclosure, safe supporting resources, and trigger and behavior tests. Use when the user asks to build, improve, standardize, or audit a skill or SKILL.md for Alpha, Cursor, Claude Code, Codex, or another Agent Skills-compatible host. Do not use merely to install, list, or invoke an existing skill.","https:\u002F\u002Fgithub.com\u002Flukegob10\u002Falpha\u002Fblob\u002Fmain\u002Fsrc\u002Fassets\u002Fskills\u002Fskill-builder\u002FSKILL.md",[69],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[75,76,77,78,79,80,81,82,83,84,85,86,87,29,30,88,89,90,33,91],"Skill Builder","builder","existing skill","migrate","revise","frontmatter","list","a skill","install","safe","audit","packages","create","invoke","host","improve","resources",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":36},"01M71E59YCND235ZE1H81B2ZPV","rich-documents","Create or revise a rich HTML document in Alpha's built-in HTML previewer for a substantial spec, review, or quantitative report, or when explicitly requested. Respect plain text, Markdown, existing output destinations, and ordinary short answers or code fixes.","https:\u002F\u002Fgithub.com\u002Flukegob10\u002Falpha\u002Fblob\u002Fmain\u002Fsrc\u002Fassets\u002Fskills\u002Frich-documents\u002FSKILL.md",[],[99,100,101,102,103,87,104,29,30,105,106,107,33,34,108,109,79,110,111,112],"rich","documents","rich documents","output","review","text","document","Existing","short","fixes","markdown","plain","spec","report",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":125,"publishedAt":36},"01M71E585QAQCYMJF0GW521X1Z","review-agent","Review a specified code change for actionable defects and return prioritized findings without editing. Use when explicitly asked to use this skill, including a delegated review of working changes, a commit, or a branch against its base. Investigating a reported failure belongs to debug.","https:\u002F\u002Fgithub.com\u002Flukegob10\u002Falpha\u002Fblob\u002Fmain\u002Fsrc\u002Fassets\u002Fskills\u002Freview-agent\u002FSKILL.md",[119,120],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[126,103,127,128,29,30,129,130,131,132,34,133,134,135,136,31],"review agent","debug","commit","base","editing","actionable","defects","changes","change","branch","code change",{"skillNo":138,"name":127,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":146,"publishedAt":36},"01M71E55MFBZP2S27286B0S45Z","Investigate a concrete bug with an unclear cause using reproduction, hypotheses, and runtime evidence. Use for an explicit debugging investigation, unexplained or intermittent incorrect behavior, or the same failure persisting after an attempted fix. Skip routine commands, ordinary implementation, code review, general debugging questions, and isolated build\u002Ftest errors whose cause and correction are already clear. Mentioning a bug, error, log, or test alone does not trigger this skill.","https:\u002F\u002Fgithub.com\u002Flukegob10\u002Falpha\u002Fblob\u002Fmain\u002Fsrc\u002Fassets\u002Fskills\u002Fdebug\u002FSKILL.md",[142,145],{"categoryNo":143,"categoryName":144,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},[127,147,148,149,34,150,151,152,153,154,155,156,157,103,158,29,159,31,160,161],"trigger","code review","runtime","evidence","error","fix","build","questions","test","investigate","with","log","debugging","errors","general",{"skillNo":163,"name":164,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":168,"publishedAt":36},"01M71E54DERK8A9CDYT48CNJ59","skill","https:\u002F\u002Fgithub.com\u002Flukegob10\u002Falpha\u002Fblob\u002Fmain\u002Fevals\u002Fjavascript\u002Falpha-skill-workflow\u002Fskill\u002FSKILL.md",[167],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},[],{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":176,"publishedAt":36},"01M71E4Z98E8AETCFR2ZARXSDS","alpha-conflict-resolution","Provides comprehensive guidelines for resolving merge conflicts intelligently using git history and commit context. Use when tasks involve merge conflicts, rebasing, PR conflicts, or git conflict resolution. This skill analyzes commit messages, git blame, and code intent to make intelligent resolution decisions.","https:\u002F\u002Fgithub.com\u002Flukegob10\u002Falpha\u002Fblob\u002Fmain\u002F.alpha\u002Fskills\u002Falpha-conflict-resolution\u002FSKILL.md",[175],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},[177,178,179,180,33,181,182,183,184,19,185,186,187,188,128,189,29,30,190,191],"conflict resolution","alpha conflict resolution","resolution","conflict","commit messages","history","Using git","make","git","merge","intent","conflicts","tasks","messages","pr conflicts"]