[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79T2G4H62SNCYJ76ECKAPFH":3,"skill-same:01M79T2G4H62SNCYJ76ECKAPFH":49},{"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":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M79T2G4H62SNCYJ76ECKAPFH","migrate-to-codex",null,"Migrate supported instruction files, skills, agents, and MCP config into Codex project and global files.","Snuc1925\u002FSWE-AI-Agent","Snuc1925","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87866086?v=4","01M79SEFKVJ24BEZS59RCHPNSX","01M79SEFMJFYTNK7S8WF299CWN",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fmigration-release\u002Fmigrate-to-codex\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fmigration-release\u002Fmigrate-to-codex\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: migrate-to-codex\ndescription: Migrate supported instruction files, skills, agents, and MCP config into Codex project and global files.\n---\n\n# Migrate to Codex\n\n## Autonomy\n\nKeep going until the selected migration is completely done: run the migrator, inspect the report, fix migrated Codex instructions\u002Fskills\u002Fagents\u002FMCP config, and re-run checks without stopping to ask for confirmation of the next step. If the user has selected a target, do not ask before creating, editing, replacing, or deleting generated Codex artifacts in that target (`AGENTS.md`, `.codex\u002F`, `.agents\u002F`, or `~\u002F.codex\u002F`). Preserve unrelated existing Codex config entries in `.codex\u002Fconfig.toml` or `~\u002F.codex\u002Fconfig.toml`, such as `notify`, `projects`, `marketplaces`, or unrelated MCP servers; do not ask about them unless they fail validation or directly conflict with the migration. Do not edit source Claude Code files (`.claude\u002F`, `~\u002F.claude\u002F`, `.mcp.json`, or `.claude.json`), unrelated project code, secrets, or another repository.\n\n## Migration Order\n\nRun the migration in this order for each selected global or project source:\n\n1. Start by using Codex's built-in TODO\u002Ftask list tool. Do not create `MIGRATION_TODOS.md` or any TODO file unless the user explicitly asks. The TODO list input has a `plan` array whose items each have `step` and `status`; use statuses `pending`, `in_progress`, and `completed`. Make the TODOs specific to the selected artifacts. Before finishing, update the TODO list so every finished step is marked `completed` and no step remains `in_progress`. Use literal source → Codex target labels, for example:\n   - Inspect `.claude\u002Fcommands` → Codex skills\u002Fprompts\n   - Inspect `.claude\u002Fagents` → `.codex\u002Fagents`\n   - Inspect `.mcp.json` → `.codex\u002Fconfig.toml` MCP servers\n   - Inspect `.claude\u002Fsettings.json` hooks → `.codex\u002Fhooks.json`\n   - Migrate safe selected artifacts → Codex files\n   - Validate generated `.codex\u002Fconfig.toml`\n   - Validate generated `.codex\u002Fagents`\n   - Report migrated artifacts and manual-review items\n\n2. Read `references\u002Fdifferences.md` (and refresh Codex docs if its `Docs last checked` date is old).\n\n3. Scan and inspect before writing:\n   - `--scan-only` lists active and inactive source surfaces.\n   - `--plan` prints staged Codex artifact paths and report rows.\n   - `--doctor` summarizes readiness, manual-review work, and validation risks.\n\n4. Convert surfaces in the same order the CLI uses:\n   - instructions: `CLAUDE.md` \u002F `AGENTS.md` to `AGENTS.md`\n   - plugins: report Claude plugin trees and marketplaces as manual migration work\n   - hooks: rewrite supported Claude hooks into `.codex\u002Fhooks.json` and enable `[features].codex_hooks = true`\n   - skills and commands: write Codex skills under `.agents\u002Fskills\u002F`\n   - config: write `.codex\u002Fconfig.toml` from Claude model\u002Fsandbox settings and MCP servers, including `personality = \"friendly\"` when config is generated\n   - subagents: write Codex custom agents under `.codex\u002Fagents\u002F`\n\n5. Dry-run, then write the selected target. Use `--replace` only when orphan generated skills or agents should be deleted.\n\n6. Inspect the terminal output and `.codex\u002Fmigrate-to-codex-report.txt` after real runs.\n\n7. Review generated artifacts in this order: `AGENTS.md`, `.agents\u002Fskills\u002F`, `.codex\u002Fconfig.toml`, `.codex\u002Fhooks.json`, `.codex\u002Fagents\u002F`, then report-only plugin items.\n\n8. Run `--validate-target` against each target after edits.\n\n9. Re-run checks and `--dry-run` after edits.\n\n10. Return the final migration report as one markdown table per scope that has rows. The tables cover only the non-native follow-up migration work you performed, such as skills created from slash commands, subagents, MCP servers, hooks, unsupported\u002Flocal plugin notes, and manual-review caveats. Include programmatic native import rows for config, instructions, skills, or supported plugins only if you personally migrated them in this follow-up run.\n\n    If only one scope has rows, render only the table with no heading. If multiple scopes have rows, render one heading before each table. Use `**User Config**` for user-scope rows. For project-scope rows, use the actual project folder name as the heading, for example `**northstar-support-portal**`; do not use `Current Project` as the heading. Do not add prose before or after the table output.\n\n    Use exactly these columns:\n\n    **northstar-support-portal**\n\n    | Status | Item | Notes |\n    | --- | --- | --- |\n    | `Added` | `Slash command` pr-review | Converted into a Codex skill |\n    | `Added` | `Subagent` release-lead | Added as a Codex subagent |\n    | `Check before using` | `Hook` PreToolUse | Converted, but some Claude hook behavior differs in Codex |\n    | `Not Added` | `Hook` Notification | Codex does not have an equivalent notification hook |\n    | `Not Added` | `Plugin` team-macros | Plugin needs manual setup |\n\n    `Status` must be `Added`, `Check before using`, or `Not Added`. Use `Added` when a Codex-facing artifact was created or changed and needs no special review. Use `Check before using` when a Codex-facing artifact was created or changed but the migration changed semantics, inferred behavior, preserved tool rules as guidance, or dropped unsupported behavior. Use `Not Added` when a source artifact was detected but no Codex-facing artifact was created. `Item` combines the artifact type and concrete item name in one cell. Artifact type must be singular: `Skill`, `Slash command`, `Subagent`, `MCP`, `Hook`, or `Plugin`. Wrap the artifact type in inline code; write the item name as plain text after it. `Notes` is always required; never leave it empty. Keep notes short, plain, and literal. Avoid internal implementation terms such as runtime expansion. Prefer phrases like `Converted into a Codex skill`, `Added as a Codex subagent`, `Added to Codex config`, `Converted into a Codex hook`, `Converted, but some Claude hook behavior differs in Codex`, `Codex does not have an equivalent notification hook`, `Plugin needs manual setup`, or `Plugin marketplace needs manual setup`.\n\n## Self-Healing Loop\n\nKeep looping until the selected migration is complete:\n\n1. Run `--plan` or `--doctor`.\n2. Run the migration with `--dry-run`.\n3. Run the migration for real.\n4. Fix every generated `## MANUAL MIGRATION REQUIRED` block and every `manual_fix_required` or `skipped` report row that can be resolved inside Codex artifacts.\n5. Run `--validate-target`.\n6. Re-run the migrator and validator until the report and validator have no actionable generated-artifact fixes left.\n\nDo not edit source Claude Code files, unrelated project code, secrets, or another repository during this loop. If a report row requires source-provider changes or product judgment, leave the generated Codex artifact with clear manual guidance instead of changing the source.\n\n## Commands\n\nChoose the migrator command.\n\n   ```bash\n   MIGRATE_TO_CODEX='python3 .codex\u002Fskills\u002Fmigrate-to-codex\u002Fscripts\u002Fmigrate-to-codex.py'\n   ```\n\nInspect the migration before writing.\n\n   ```bash\n   $MIGRATE_TO_CODEX --source ~\u002F.claude\u002F --scan-only\n   $MIGRATE_TO_CODEX --source ~\u002F.claude\u002F --target ~\u002F.codex\u002F --plan\n   $MIGRATE_TO_CODEX --source ~\u002F.claude\u002F --target ~\u002F.codex\u002F --doctor\n   ```\n\nDry-run, then run without `--dry-run`, for global and project.\n\n   ```bash\n   $MIGRATE_TO_CODEX --source ~\u002F.claude\u002F --target ~\u002F.codex\u002F --dry-run\n   $MIGRATE_TO_CODEX --source ~\u002F.claude\u002F --target ~\u002F.codex\u002F\n   $MIGRATE_TO_CODEX --source .\u002F.claude\u002F --target .\u002F.codex\u002F --dry-run\n   $MIGRATE_TO_CODEX --source .\u002F.claude\u002F --target .\u002F.codex\u002F\n   ```\n\nRun the post-migration validator against each target after edits.\n\n   ```bash\n   $MIGRATE_TO_CODEX --validate-target ~\u002F.codex\u002F\n   $MIGRATE_TO_CODEX --validate-target .\u002F.codex\u002F\n   ```\n\nRun `$MIGRATE_TO_CODEX --help` for flags (`--scan-only`, `--plan`, `--doctor`, `--validate-target`, defaults, and so on). Deep tables and more links are in `references\u002Fdifferences.md`.\n","# Migrate to Codex\n\n## Autonomy\n\nKeep going until the selected migration is completely done: run the migrator, inspect the report, fix migrated Codex instructions\u002Fskills\u002Fagents\u002FMCP config, and re-run checks without stopping to ask for confirmation of the next step. If the user has selected a target, do not ask before creating, editing, replacing, or deleting generated Codex artifacts in that target (`AGENTS.md`, `.codex\u002F`, `.agents\u002F`, or `~\u002F.codex\u002F`). Preserve unrelated existing Codex config entries in `.codex\u002Fconfig.toml` or `~\u002F.codex\u002Fconfig.toml`, such as `notify`, `projects`, `marketplaces`, or unrelated MCP servers; do not ask about them unless they fail validation or directly conflict with the migration. Do not edit source Claude Code files (`.claude\u002F`, `~\u002F.claude\u002F`, `.mcp.json`, or `.claude.json`), unrelated project code, secrets, or another repository.\n\n## Migration Order\n\nRun the migration in this order for each selected global or project source:\n\n1. Start by using Codex's built-in TODO\u002Ftask list tool. Do not create `MIGRATION_TODOS.md` or any TODO file unless the user explicitly asks. The TODO list input has a `plan` array whose items each have `step` and `status`; use statuses `pending`, `in_progress`, and `completed`. Make the TODOs specific to the selected artifacts. Before finishing, update the TODO list so every finished step is marked `completed` and no step remains `in_progress`. Use literal source → Codex target labels, for example:\n   - Inspect `.claude\u002Fcommands` → Codex skills\u002Fprompts\n   - Inspect `.claude\u002Fagents` → `.codex\u002Fagents`\n   - Inspect `.mcp.json` → `.codex\u002Fconfig.toml` MCP servers\n   - Inspect `.claude\u002Fsettings.json` hooks → `.codex\u002Fhooks.json`\n   - Migrate safe selected artifacts → Codex files\n   - Validate generated `.codex\u002Fconfig.toml`\n   - Validate generated `.codex\u002Fagents`\n   - Report migrated artifacts and manual-review items\n\n2. Read `references\u002Fdifferences.md` (and refresh Codex docs if its `Docs last checked` date is old).\n\n3. Scan and inspect before writing:\n   - `--scan-only` lists active and inactive source surfaces.\n   - `--plan` prints staged Codex artifact paths and report rows.\n   - `--doctor` summarizes readiness, manual-review work, and validation risks.\n\n4. Convert surfaces in the same order the CLI uses:\n   - instructions: `CLAUDE.md` \u002F `AGENTS.md` to `AGENTS.md`\n   - plugins: report Claude plugin trees and marketplaces as manual migration work\n   - hooks: rewrite supported Claude hooks into `.codex\u002Fhooks.json` and enable `[features].codex_hooks = true`\n   - skills and commands: write Codex skills under `.agents\u002Fskills\u002F`\n   - config: write `.codex\u002Fconfig.toml` from Claude model\u002Fsandbox settings and MCP servers, including `personality = \"friendly\"` when config is generated\n   - subagents: write Codex custom agents under `.codex\u002Fagents\u002F`\n\n5. Dry-run, then write the selected target. Use `--replace` only when orphan generated skills or agents should be deleted.\n\n6. Inspect the terminal output and `.codex\u002Fmigrate-to-codex-report.txt` after real runs.\n\n7. Review generated artifacts in this order: `AGENTS.md`, `.agents\u002Fskills\u002F`, `.codex\u002Fconfig.toml`, `.codex\u002Fhooks.json`, `.codex\u002Fagents\u002F`, then report-only plugin items.\n\n8. Run `--validate-target` against each target after edits.\n\n9. Re-run checks and `--dry-run` after edits.\n\n10. Return the final migration report as one markdown table per scope that has rows. The tables cover only the non-native follow-up migration work you performed, such as skills created from slash commands, subagents, MCP servers, hooks, unsupported\u002Flocal plugin notes, and manual-review caveats. Include programmatic native import rows for config, instructions, skills, or supported plugins only if you personally migrated them in this follow-up run.\n\n    If only one scope has rows, render only the table with no heading. If multiple scopes have rows, render one heading before each table. Use `**User Config**` for user-scope rows. For project-scope rows, use the actual project folder name as the heading, for example `**northstar-support-portal**`; do not use `Current Project` as the heading. Do not add prose before or after the table output.\n\n    Use exactly these columns:\n\n    **northstar-support-portal**\n\n    | Status | Item | Notes |\n    | --- | --- | --- |\n    | `Added` | `Slash command` pr-review | Converted into a Codex skill |\n    | `Added` | `Subagent` release-lead | Added as a Codex subagent |\n    | `Check before using` | `Hook` PreToolUse | Converted, but some Claude hook behavior differs in Codex |\n    | `Not Added` | `Hook` Notification | Codex does not have an equivalent notification hook |\n    | `Not Added` | `Plugin` team-macros | Plugin needs manual setup |\n\n    `Status` must be `Added`, `Check before using`, or `Not Added`. Use `Added` when a Codex-facing artifact was created or changed and needs no special review. Use `Check before using` when a Codex-facing artifact was created or changed but the migration changed semantics, inferred behavior, preserved tool rules as guidance, or dropped unsupported behavior. Use `Not Added` when a source artifact was detected but no Codex-facing artifact was created. `Item` combines the artifact type and concrete item name in one cell. Artifact type must be singular: `Skill`, `Slash command`, `Subagent`, `MCP`, `Hook`, or `Plugin`. Wrap the artifact type in inline code; write the item name as plain text after it. `Notes` is always required; never leave it empty. Keep notes short, plain, and literal. Avoid internal implementation terms such as runtime expansion. Prefer phrases like `Converted into a Codex skill`, `Added as a Codex subagent`, `Added to Codex config`, `Converted into a Codex hook`, `Converted, but some Claude hook behavior differs in Codex`, `Codex does not have an equivalent notification hook`, `Plugin needs manual setup`, or `Plugin marketplace needs manual setup`.\n\n## Self-Healing Loop\n\nKeep looping until the selected migration is complete:\n\n1. Run `--plan` or `--doctor`.\n2. Run the migration with `--dry-run`.\n3. Run the migration for real.\n4. Fix every generated `## MANUAL MIGRATION REQUIRED` block and every `manual_fix_required` or `skipped` report row that can be resolved inside Codex artifacts.\n5. Run `--validate-target`.\n6. Re-run the migrator and validator until the report and validator have no actionable generated-artifact fixes left.\n\nDo not edit source Claude Code files, unrelated project code, secrets, or another repository during this loop. If a report row requires source-provider changes or product judgment, leave the generated Codex artifact with clear manual guidance instead of changing the source.\n\n## Commands\n\nChoose the migrator command.\n\n   ```bash\n   MIGRATE_TO_CODEX='python3 .codex\u002Fskills\u002Fmigrate-to-codex\u002Fscripts\u002Fmigrate-to-codex.py'\n   ```\n\nInspect the migration before writing.\n\n   ```bash\n   $MIGRATE_TO_CODEX --source ~\u002F.claude\u002F --scan-only\n   $MIGRATE_TO_CODEX --source ~\u002F.claude\u002F --target ~\u002F.codex\u002F --plan\n   $MIGRATE_TO_CODEX --source ~\u002F.claude\u002F --target ~\u002F.codex\u002F --doctor\n   ```\n\nDry-run, then run without `--dry-run`, for global and project.\n\n   ```bash\n   $MIGRATE_TO_CODEX --source ~\u002F.claude\u002F --target ~\u002F.codex\u002F --dry-run\n   $MIGRATE_TO_CODEX --source ~\u002F.claude\u002F --target ~\u002F.codex\u002F\n   $MIGRATE_TO_CODEX --source .\u002F.claude\u002F --target .\u002F.codex\u002F --dry-run\n   $MIGRATE_TO_CODEX --source .\u002F.claude\u002F --target .\u002F.codex\u002F\n   ```\n\nRun the post-migration validator against each target after edits.\n\n   ```bash\n   $MIGRATE_TO_CODEX --validate-target ~\u002F.codex\u002F\n   $MIGRATE_TO_CODEX --validate-target .\u002F.codex\u002F\n   ```\n\nRun `$MIGRATE_TO_CODEX --help` for flags (`--scan-only`, `--plan`, `--doctor`, `--validate-target`, defaults, and so on). Deep tables and more links are in `references\u002Fdifferences.md`.\n",{"name":5,"description":7},"main","459326d435e3b6ae17300b946bd4b7458ecd2bae","skill-library\u002Fmigration-release\u002Fmigrate-to-codex","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent","https:\u002F\u002Fgithub.com\u002FSnuc1925","2026-07-29 09:46:52",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Snuc1925\u002FSWE-AI-Agent --skill migrate-to-codex",{"tool":36,"command":37},"bunx","bunx skills add Snuc1925\u002FSWE-AI-Agent --skill migrate-to-codex",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Snuc1925\u002FSWE-AI-Agent --skill migrate-to-codex","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fmigration-release\u002Fmigrate-to-codex\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",11357,[50,58,66,74,82,90],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":54,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M79T5E59T5HMWZVTFJA9QXN1","linear","Manage issues, projects & team workflows in Linear. Use when the user wants to read, create or updates tickets in Linear.","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fworkflow-planning\u002Flinear\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fworkflow-planning\u002Flinear\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":62,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79T535TSDZ09RXZ2YPEE3TN","define-goal","Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome. Use this skill for goal creation and goal refinement only; it does not manage durable snapshots, decision logs, or long-running execution artifacts.","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fworkflow-planning\u002Fdefine-goal\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fworkflow-planning\u002Fdefine-goal\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79T4TE9NAVN5REZVETVXBCN","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79T4HSEDWY2NXVRDZ3RX7J4","test-master","Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation frameworks; analyzing coverage gaps; performance testing with k6 or Artillery; security testing with OWASP methods; debugging flaky tests; or working on QA, regression, test automation, quality gates, shift-left testing, or test maintenance.","MIT","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Ftest-master\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M79T43SW5P3Y37F6Y82T76EM","playwright","Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Fplaywright\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Fplaywright\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M79T3ZYPH547MMC5FFBY1APS","playwright-interactive","Persistent browser and Electron interaction through `js_repl` for fast iterative UI debugging.","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Fplaywright-interactive\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Fplaywright-interactive\u002FSKILL.md",[],[]]